Skip to main content

Databases and services

The platform runs shared database and message-broker servers for you. You create a service user with a password, create databases under it, and connect from any of your labs — nothing to install, back up or keep running yourself.

Open Services in the sidebar. The badge next to it counts your service users.

Services are in beta

The page says so itself. They are fine for learning, projects and prototypes; keep your own backups of anything you cannot lose.

What is available​

Which engines appear depends on your platform. The managed ones — with a Manage button — are:

ServiceKindInside a user you create
MySQLRelational databaseDatabases
MariaDBRelational databaseDatabases
PostgreSQLRelational databaseDatabases
MongoDBDocument databaseDatabases
RedisKey-value storeNothing — credentials only
RabbitMQMessage brokerVirtual hosts

Some cards are informational only, such as Adminer (a browser-based database tool) and Memcached. They show how to reach the service but have nothing to manage.

Limits​

LimitFree planPaid plan
Service users, across all engines215
Users per engine55
Databases (or virtual hosts) per user55

While acting as an organization, the organization's own limit applies. Your exact numbers are in Account Settings → Account Limits.

At a limit you see You have reached your services limit (N) or You have reached the maximum number of databases allowed. Delete a user or database you no longer need.

The service card​

The Services page with two or three service cards, one showing the hostname badge, the port rows and the Port Forwarding section, and its Manage button.

Each card shows:

  • the hostname to use from inside your labs (hover it: This hostname is reachable from within your lab);
  • the port or ports the service listens on;
  • Port Forwarding helpers (below);
  • Manage, which opens the service page.

The service page​

Click Manage. The service page has a Dashboard tab and, except for Redis, a second tab for what lives inside a user.

WhereWhat is there
Dashboard → Connection InformationService, IP Address, Hostname and Port — each with a copy button. These are the values to use from inside a lab.
Dashboard → UsersYour service users for this engine (Maximum 5 users), each with its credentials and a copy button. Add User creates one.
Database tabCreate and drop databases. On RabbitMQ it is Virtual Host; Redis has no second tab.
Deleting a user deletes its databases

Delete User removes the user and every database it owns. Export anything you need first.

Connecting from a lab​

Your labs reach services directly over the platform's internal network — no tunnel or port forwarding needed.

  1. Open the service page and copy the Hostname (or IP Address) and Port from Connection Information.
  2. Use them with a user and password from the Users panel.

Always copy these values from the page rather than typing ones you remember: they are the authoritative ones for your platform. The pages for each engine have example commands:

Reaching a service from your own computer​

The Port Forwarding helpers on each service card are for using a local tool — a database GUI, your own code — against a service:

HelperHow to use it
VS Code DesktopCopy the address and add it under Ports in VS Code connected to your lab over SSH. VS Code forwards it to your computer.
VS Code Web ($)Shown for services with a web interface. Copy the command, paste it into the terminal of VS Code in the browser, and the service is reachable locally.

VS Code may forward to a different local port than the original if that port is busy on your computer. Use the port it shows.

Public endpoints​

Where a service offers a public endpoint, it is shown on the service page as a Public endpoint row (and sometimes Public TLS) under Connection Information. The same user credentials work there. If there is no such row, the service is reachable only from inside your labs — or from your computer through the port forwarding helpers above.

Services in an organization​

While you are acting as an organization, the Services page says so. Users and databases created there belong to the organization and are shared with all of its members. See Organizations.

Do it with an AI assistant​

You can also do this by asking an AI assistant connected to your account — see Connect an AI assistant to set one up.

AskWhat the assistant does
“What database services do I have?”list_services
“Create a MySQL user called appsvc01”add_service_user, with a password you choose
“List the databases under appsvc01”list_databases
“Delete appsvc01 and its databases”remove_service_user
Choose the password carefully

The assistant does not generate one — you supply it. It is stored so that anyone who can open the service page can read it, including every member of an organization. There is no password reset: changing it means removing the user, which drops its databases.

In this section​

Last updated on