Hubfly spaceDocs
Console

Managed Databases

Managed Databases

Run PostgreSQL, MySQL or SQLite (libSQL) that Hubfly space provisions, secures and operates. Connect from anywhere over TLS, or bind it to a Cell app in one step.

A managed database is an instance in a Managed service project. Hubfly space creates the server, keeps its credentials encrypted, requires TLS on every connection, and gives each instance its own dashboard for connecting, querying, monitoring and configuration. You can manage it in the Dashboard, with hubfly db, with the SDKs or through the Databases API.

Choose a guide

Engines and versions

EngineVersionsHow clients connectGood to know
PostgreSQL18 (default), 17, 16PostgreSQL protocol over TLS (sslmode=require)Extensions from an allowlist, including pgvector, PostGIS and pg_stat_statements. Needs at least 512 MiB of memory.
MySQL8.4 LTS (default), 9.7 LTSMySQL protocol over TLS (ssl-mode=REQUIRED)Oracle's long-term-support releases. Needs at least 1 GiB of memory.
SQLite (libSQL)libSQL server 0.24HTTPS with a libsql:// URL and an access tokenSQLite you can reach over the network. Uses access tokens instead of database users.

You choose the version when you create the instance. When Hubfly space publishes an update for that version line, the instance shows that an update is available and you apply it from Settings or with hubfly db upgrade.

How it fits together

ResourceWhat it is
Managed service projectA project type for services Hubfly space operates. Hubfly space chooses where it runs; there is no region picker. One project can hold several databases and Realtime servers.
InstanceOne database server: engine and version, CPU and memory, a storage volume, and a hostname made of the instance name and a short suffix, such as app-db-k3x9.db.hubfly.app.
Databases and usersPostgreSQL and MySQL: the default database and admin user created with the instance, plus any databases and users you add.
Access tokenslibSQL: signed tokens with read-only or full access, shown once when created.
App bindingWrites the connection details into the environment variables of a Cell project you choose.

What Hubfly space runs for you

  • Provisioning and placement. Hubfly space creates the server and its storage volume, and runs it in a location it chooses.
  • Credentials. Passwords and signing keys are generated by Hubfly space and stored encrypted. You get a managed admin role (it can create databases and roles and read and write all data), never a superuser.
  • TLS everywhere. Unencrypted connections are refused. Each PostgreSQL and MySQL instance has its own certificate that you can download for full verification.
  • Operations. Start, stop, restart, resize, version updates, validated configuration changes with rollback, metrics, logs, sessions and query insights.
  • Your data. Manual export and import. Exports stay downloadable for 7 days.

Single node, no automatic backups yet

Each instance runs as a single server in one location. There are no replicas, no high availability and no point-in-time recovery. Automatic backups are coming soon: until then, export your data regularly and keep the files somewhere you control.

Team access

Managed Databases use three project permissions: Database read, Database query and Database admin. Organization owners, admins and operators have all three; viewer roles have Database read.

PermissionAllows
database:readSee instances, connection details without secrets, metrics, configuration, databases, users and tokens.
database:queryRun SQL, browse and edit table rows, read logs, sessions and query insights, open a database shell.
database:adminCreate and delete instances, lifecycle and resizing, configuration, users, tokens, network, credentials, app bindings, export and import.

Passwords and tokens are shown only to people with Database admin: once when they are created, or through an explicit reveal or rotation. Reveals and rotations are recorded in the instance's activity log.

From the terminal

The hubfly CLI covers the same workflow. This creates a PostgreSQL database in a new managed project, then writes its connection string into a Cell project named web:

bash
hubfly db create app-db --engine postgresql --size nano --project new
hubfly db bind app-db --to web
hubfly db url app-db --reveal

See the hubfly db reference for every command.

Something unclear or out of date? Emailsupport@hubfly.spaceBack to top