Provision a database

Helicarrier Cloud runs managed databases for you in a part of the platform called the Hangar. You pick an engine, and Helicarrier provisions it, keeps it running, and handles backups and connection details — no server setup.

Supported engines

• PostgreSQL — the default relational database. Optionally enable pgvector at creation for embeddings and vector search.
• MySQL and MariaDB — widely compatible relational databases.
• Redis — in-memory key/value store for caching, queues, and sessions.
• MongoDB — document database.
• ClickHouse — columnar warehouse for analytics.
• Qdrant — vector database for AI/embedding workloads.

Create one

1. On the Deck, click + New and choose the database engine you want.
2. Optionally set a name and (for engines that support it) a password. Leave the password blank to have one generated.
3. For PostgreSQL, tick pgvector if you need vector search.
4. Create it. Helicarrier provisions the database as a service node on your canvas.

pgvector for embeddings

If you are building AI features, enable pgvector when you create a PostgreSQL database. Helicarrier installs the extension so you can store and query embeddings directly in Postgres — no separate vector store needed (though Qdrant is available if you prefer a dedicated one).

Passwords

For PostgreSQL, MySQL, MariaDB, MongoDB, and Redis you can rotate the password later from the database’s settings — the change applies live. ClickHouse and Qdrant set their password at boot and are not rotatable after creation.

What you get

Once provisioned, the database exposes everything you need on its drawer:

• Connection details — internal and external URLs and split credentials (see Connect to your database).
• Backups — on-demand and automatic daily backups (see Backups & restore).
• Data tools — browse tables, collections, and keys right in the dashboard.

What Redis includes

Managed Redis runs Redis 8, so JSON, search, time series and probabilistic structures are part of the server — nothing to install:

JSON.SET user:1 $ '{"name":"Ada","tags":["admin"]}'
JSON.GET user:1 $.name
FT.CREATE idx ON JSON PREFIX 1 user: SCHEMA $.name AS name TEXT
TS.CREATE temperature

Databases created on Redis 7 or earlier do not have these commands — they return ERR unknown command. Existing databases can be moved forward from the Connect tab: upgrading keeps your data and restarts the database. It is one-way, since the newer version rewrites its data files in a format the older one cannot read.

Next

Wire it up: Connect to your database.