HeliosDB Cloud is the managed service for HeliosDB Nano at cloud.heliosdb.com. Each database runs SQL with vector search, branching and time-travel queries, and is reached through a REST API and a remote MCP server on every plan; direct PostgreSQL connections are not available yet. During its Experimental Period every plan, Free, Starter and Pro, costs $0/mo for every customer; accounts are for business email addresses, with no trial.
Last updated
Console accounts at cloud.heliosdb.com are for business email addresses. Personal mailbox domains such as gmail.com, yahoo.com and outlook.com are not accepted for them. After you verify your email address, the account is on the Free plan; a product feedback session with the HeliosDB team raises the Free quotas to their highest level. Agents and scripts that need a database without the console use the BaaS API: the account starts at the Instant level and may use any email address; with a personal mailbox address (such as gmail.com or outlook.com) the account is API-only: no console sign-in and no email verification, and it stays at the Instant level. The service is offered to organisations only, under the Cloud Terms of Service, the Data Processing Agreement and the Transaction Durability Commitment.
Nothing during the current Experimental Period: every plan, Free, Starter and Pro, costs $0/mo for every customer, the limits are indicative and not metered for billing, and no charge starts when the period ends unless you accept new paid terms. There is no trial of any kind, and no Enterprise plan or add-on is offered during the period. The numbers match the pricing page.
| Feature | Free $0/mo | Starter $0/mo | Pro $0/mo |
|---|---|---|---|
| Databases | 3 / 4 | 5 | 20 |
| Storage | 500 MB / 1 GB | 1 GB | 10 GB |
| Connections | 5 / 10 | 20 | 100 |
| Vector Storage | 50K / 100K | 100K | 1M |
| API Requests/mo | 50K / 100K | 100K | 1M |
| Time-Travel Retention | 7 / 14 days | 30 days | 90 days |
| Encryption | AES-256-GCM encryption at rest + zero-knowledge encryption | AES-256-GCM encryption at rest, all encryption modes | AES-256-GCM encryption at rest, all encryption modes |
| Uptime commitment | None on any plan; no service credits | ||
| Durability | Transaction Durability Commitment on every plan | ||
| Support | Best effort under the Support Policy; community channels for questions | ||
Free column: after email verification / after a product feedback session. All limits are indicative during the Experimental Period. Reference prices for after it, which apply only under new terms you accept expressly: Starter $9 and Pro $49 a month.
HeliosDB Cloud gives no availability or uptime commitment. It gives the Transaction Durability Commitment instead: a transaction the service has acknowledged as committed is not lost because of the version of the HeliosDB engine HeliosDB runs, including upgrades. HeliosDB Cloud does not route connections through HeliosProxy today; if it does, the commitment covers that too. It does not cover deletes made with your credentials, or hardware or site failures that destroy the data and all its copies, where a restore from the daily backup can lose up to about 24 hours of changes. One known limitation of the engine is excluded where its workaround is not used: statements outside an explicit transaction that read and change the same row from several sessions at once (such as UPDATE ... SET n = n + 1) can lose updates, so run them in an explicit transaction and retry when it reports a serialization failure. Terms: Cloud Terms of Service, Data Processing Agreement, Support Policy.
Every plan, Free included, has branching, time-travel queries, managed backups, encryption at rest, zero-knowledge encryption, vector and full-text search, and the REST and MCP interfaces. Plans differ in indicative quotas, retention and connection options.
Create a branch from the current state, from a timestamp or from a transaction ID, switch to it and merge it back. Branches are available in SQL, over REST and as MCP tools.
Read a database as it was at a past timestamp, within the plan's retention window, with AS OF TIMESTAMP in SQL or the query-at endpoint.
Backups are part of the managed service; there is no backup job to set up on your side.
Data is stored with AES-256-GCM encryption at rest. Zero-knowledge encryption derives keys and encrypts data on the client, so the server never sees plaintext keys. Starter and up include all encryption modes.
A REST API described by an OpenAPI 3.1 spec and a remote MCP server at /api/v1/mcp, both authenticated with per-database API keys that carry read or write scopes.
VECTOR(n) columns with HNSW indexes and BM25-ranked full-text search, in the same SQL as the rest of your data.
The connection options depend on the plan. GET /api/v1/connection-info returns the details for your account’s plan, and API keys are created per database in the console or over REST.
REST and MCP over HTTPS with a per-database API key.
REST and MCP over HTTPS, as on Free. Pro gives each organization a dedicated database file. Direct PostgreSQL connections for psql and standard drivers are not available yet.
curl -X POST "https://cloud.heliosdb.com/api/v1/organizations/$ORG_ID/databases/$DB_ID/execute" \
-H "X-API-Key: $HDB_API_KEY" \
-H "Content-Type: application/json" \
-d '{"sql": "SELECT id, title FROM documents WHERE id = $1", "params": [42]}'curl -X POST "https://cloud.heliosdb.com/api/v1/organizations/$ORG_ID/databases/$DB_ID/branches" \
-H "X-API-Key: $HDB_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "before-import", "as_of": "timestamp:2026-10-01T06:00:00"}'claude mcp add --transport http heliosdb https://cloud.heliosdb.com/api/v1/mcp \
--header "Authorization: Bearer $HDB_API_KEY"Use "as_of": "transaction:<id>" to branch from a transaction instead of a timestamp. The full endpoint list and the MCP tool catalogue are on the BaaS page and in the agent integration guide.
HeliosDB Cloud is the managed service for HeliosDB Nano at cloud.heliosdb.com. You create databases in the console or through the API and use them over a REST API and a remote MCP server; direct PostgreSQL connections are not available yet. HeliosDB operates the service, including encryption at rest and backups.
Console accounts, and every account at the Verified level or above, are for business email addresses; personal mailbox domains such as gmail.com, yahoo.com and outlook.com are not accepted for them. Agents and scripts that need a database without the console create one through the BaaS API with POST /api/v1/quick-start, described on the BaaS page: that account starts at the Instant level and may use any email address; with a personal mailbox address (such as gmail.com or outlook.com) the account is API-only: no console sign-in and no email verification, and it stays at the Instant level.
After you verify your email address, the Free plan gives 3 databases, 500 MB of storage, 5 connections, 50K vectors, 50K API requests a month and 7 days of time-travel retention. Completing a product feedback session raises it to 4 databases, 1 GB, 10 connections, 100K vectors, 100K API requests and 14 days. Free databases are reached over REST and MCP, with AES-256-GCM encryption at rest and zero-knowledge encryption.
No. HeliosDB Cloud has no trial of any kind, and no plan turns into a paid plan. During the Experimental Period every plan, Starter and Pro included, is free for every customer; HeliosDB gives at least 30 days’ notice before the period ends, and paid plans then start only under new terms you accept expressly (Cloud Terms).
Every Cloud plan is free of charge for every customer, plan limits are indicative and not metered for billing, and features may change; no availability commitment is given, while the Transaction Durability Commitment applies throughout. HeliosDB gives at least 30 days’ notice by email and in the console before the period ends (Cloud Terms, section 4).
Every plan has the REST API and the MCP server at /api/v1/mcp, authenticated with a per-database API key. Direct PostgreSQL connections for psql and standard drivers are not available yet.
Yes, on every plan. Create a branch from the current state, a timestamp or a transaction ID, switch to it and merge it back, and run time-travel queries at any point inside the plan's retention window: 7 days on Free (14 after the feedback session), 30 days on Starter and 90 days on Pro.
No. HeliosDB Cloud gives no availability or uptime commitment and no service credits on any plan. It gives the Transaction Durability Commitment instead: a transaction the service has acknowledged as committed is not lost because of the version of the HeliosDB engine HeliosDB runs, including upgrades. HeliosDB Cloud does not route connections through HeliosProxy today; if it does, the commitment covers that too. Support is best effort under the Support Policy.
HeliosDB Cloud runs HeliosDB Nano databases. A managed service for Lite and Full is planned; both editions are licensed for self-hosting through sales, as described on the pricing page.
Sign up with a business email address. Every plan is free during the Experimental Period, under the Cloud Terms of Service.