Quickstart in Console

Stable

The first working scenario in Console: login → tenant → database → connect → monitoring.

Updated: March 5, 2026

Below is a typical user path that covers most scenarios: create a workspace, start your first database, and connect an application right away.

1. Log in to Console

Open Console in a browser and enter:

  • email;
  • API token.

Important: the API token is access to the Control Plane, not a PostgreSQL password.

2. Create a tenant

Go to the Tenants section and create a separate tenant for your project or environment.

Right after creation, Console usually shows:

  • pg_user;
  • pg_password;
  • dsn_template.

This is a key moment: save them immediately into a secret store, .env, or your team’s internal secrets system.

3. Create a database

On the tenant page, create a database and specify:

  • name;
  • size.

In the trial scenario, Console usually leaves only L1 available. On broader plans, other size classes are available too.

After creation, the database will appear in the list. In the serverless model, this does not mean compute is already running permanently — the platform will start it when needed.

4. Open the database page and copy the DSN

On the page of a specific database, Console fills the tenant data into the template DSN and shows the ready-made connection string for the selected database.

Usually, you can also:

  • copy the DSN with one click;
  • view examples for psql, JDBC, SQLAlchemy, node-postgres;
  • download a .env file if your UI build supports it.

5. Connect your application

Connect to the database through the Gateway host from the DSN.

If the database is in stopped, the first client connection may take a little longer: Gateway initiates auto-start, the Control Plane starts compute, and then the connection proceeds as with a regular PostgreSQL instance.

6. Check Monitoring

After the first connection, open:

  • Metrics — to see CPU, memory, connections, and general activity;
  • Logs — to quickly verify errors and the fact that startup completed successfully;
  • and, if necessary, Active queries and Query statistics.

Practical result

A normal working scenario in Console looks like this:

login -> create tenant -> save credentials -> create db -> copy DSN -> connect app -> check monitoring

This is the main advantage of Console: a minimal number of manual steps and a clear path to a working PostgreSQL database.