Hubfly space Managed DatabasesPostgreSQL, MySQL & SQLite

Managed Databases.PostgreSQL, MySQL and SQLite, run for you.

Create a PostgreSQL, MySQL or SQLite (libSQL) database on dedicated resources. Hubfly space provisions and operates it; you choose its size and who can connect, then bind it to your apps.

Three stacked matte graphite database discs with brushed steel rims and a small amber status light
PostgreSQL, MySQL & SQLiteHubfly space Managed Databases
  • PostgreSQL, MySQL & SQLite (libSQL)
  • TLS always on, optional IP allowlist
  • Bind to a Cell app in one step
  • Explore the API

Built for your workflow

A production database without running the server.

Pick an engine, a size and who can connect. Hubfly space provisions the instance, keeps it running and gives you the tools to work with your data from Dashboard, the CLI or the API.

Three engines, current versions

PostgreSQL 18, 17 or 16 with extensions such as pgvector and PostGIS, MySQL 8.4 or 9.7 LTS, or SQLite served over HTTPS by libSQL.

Encrypted connections, your rules

Every connection uses TLS. Limit public access with an IP allowlist or turn it off, verify the server with its own certificate, and rotate credentials whenever you need to.

Connect apps in one step

Bind a database to a Cell project and Hubfly space writes DATABASE_URL, or LIBSQL_URL and LIBSQL_AUTH_TOKEN, into its environment. Your app reads them on its next deploy.

Work with your data

A SQL editor that stays read-only until you allow writes, a table explorer, users and tokens, metrics, logs, sessions, query insights and a validated configuration editor.

How it works

From engine choice to a connected app.

Create an instance in Dashboard or with one CLI command. Hubfly space decides where it runs, provisions its storage and shows the price before anything is created.

  1. 1

    Choose the engine and size

    PostgreSQL, MySQL or SQLite (libSQL); a preset from Nano to X-Large or custom CPU and memory; 1 to 500 GiB of storage.

  2. 2

    Decide who can connect

    Public access over TLS is on by default. Add an IP allowlist, or turn public access off so only apps running on Hubfly space can connect.

  3. 3

    Connect and build

    Bind it to a Cell project, copy a connection string into your client, or open a SQL shell with hubfly db shell.

Example database instance

Instance
app-db
Engine
PostgreSQL 18
Size
Small · 0.5 vCPU / 1 GiB · 10 GiB storage
Host
app-db-k3m9.db.hubfly.app
Access
TLS required · IP allowlist
Bound to
web → DATABASE_URL

Illustrative instance. Dashboard and the CLI show the exact endpoint and price before you create it.

Use it from the CLI

Create, bind and query from your terminal.

The hubfly db commands cover the whole lifecycle: create and resize instances, manage databases and users, run SQL, export and import, and follow metrics and logs.

Command reference

hubfly-cli

$ hubfly db create app-db --engine postgresql --size small
# Shows the monthly quote, then waits until the database is ready
$ hubfly db bind app-db --to web
# Writes DATABASE_URL into the web project
$ hubfly db query app-db "select count(*) from users"
$ hubfly db export app-db --format sql --output app-db.sql

A few useful details

Before you start.

Go deeper in the docs

Works well with

  • Cell

    Deploy the app that uses your database, then bind the two together.

  • Realtime

    Add live updates to the same app with managed WebSockets.

  • Volumes and registry

    Run a self-managed database in a container with a persistent volume.

What does a managed database cost?

Pay as you go, billed hourly: compute at the dedicated container rates, storage at the standard volume rate, and a management fee of 30% of compute while the instance runs. A stopped instance pays for storage only. Nano with 10 GiB of storage comes to about $2.02 a month. The quote in Dashboard or the CLI is authoritative.

What does Hubfly space manage, and what is up to me?

Hubfly space provisions the instance, runs the engine with TLS, enforces your network rules, watches its health and applies minor version updates when you choose to upgrade. You own the schema, data, users and queries. Your admin user can create databases and roles and read and write all data, but it is not a superuser.

Are backups included?

Automatic backups are coming soon. Today you can export a database and import it again from Dashboard or the CLI; exports stay downloadable for 7 days, and each file can be up to 5 GB. Every instance runs on a single node without replicas, so keep your own copies of data you cannot afford to lose.

How are connections secured?

TLS is always required: PostgreSQL uses sslmode=require, MySQL requires secure transport and libSQL is served over HTTPS. For PostgreSQL and MySQL you can download the instance certificate to verify the server, for example with sslmode=verify-full. Public access is on by default; limit it to up to 64 allowed address ranges, or turn it off.

Where does my database run?

Hubfly space chooses the location and runs each instance there on a single node. There is no region picker, and instances are not replicated or spread across regions.

Can I still run a database in a container?

Yes. You can run any database yourself in a Cell container with a persistent volume, for example from a template. Choose Managed Databases when you want PostgreSQL, MySQL or SQLite operated for you.

Build with Managed Databases

Make Managed Databases part of your project.

Create a PostgreSQL, MySQL or SQLite (libSQL) database on dedicated resources. Hubfly space provisions and operates it; you choose its size and who can connect, then bind it to your apps.