• Start
Sign In

FAQs

Common questions about managed instances: getting started, limits, security, pricing, legal terms, and troubleshooting.

Short answers to the questions asked most often about managed instances, with links to the page that covers each one in full.

A SurrealDB deployment that SurrealDB operates. SurrealDB handles provisioning, high availability, patching, backups, and version upgrades. See Instances for what that covers, and Self-hosted if you would rather run the server yourself.

Create an account at app.surrealdb.com, create an organisation, and deploy an instance. The free instance type needs no payment details.

AWS, in the regions listed in Create an instance. Support for further cloud providers is planned.

Any language with a SurrealDB SDK:

Any other language can use the HTTP API.

Yes. Export from your current deployment, then import into the instance. See Import and export, and Migrating to SurrealDB for a move from another database.

A dedicated migration tool for existing self-hosted deployments is in development. Until it ships, use surreal export and surreal import.

The instance most likely has no user or access method defined yet. Studio authenticates with your own session, so it works before any credentials exist. An SDK needs credentials. See Connect via SDK.

Yes. Automated snapshots run on a schedule, with tiered daily, weekly, and monthly retention. The snapshot frequency and the retention of each tier depend on the instance type, and Scale instances allow a configurable frequency. See Backups and recovery.

Once every six hours. Storage can increase but never decrease. See Configure an instance.

No. Deploy an instance in the target organisation, then move the data with surreal export and surreal import.

Not at present. Delete the instances inside it, and it stops accruing charges. See Organisations.

  • Server flags and environment variables cannot be set directly. Instance capabilities control runtime behaviour instead, in Studio or with surrealctl instance capabilities.

  • GraphQL is not yet enabled on managed instances.

  • Free instances become read-only above the 1 GB storage allowance. Existing data stays available, and new writes are refused until you move to a paid instance type.

  • Request sizes are capped per endpoint. See request size limits.

Instances run with encryption at rest and in transit, network isolation, access controls, and monitoring, as set out in the Security Addendum. Multi-factor authentication is available through the identity provider you sign in with.

SurrealDB holds ISO 27001, SOC 2 (Type 2), and Cyber Essentials Plus certifications. Further industry-specific programmes, such as HIPAA and PCI DSS, are planned. The Trust Centre holds the current detail.

Instances also inherit the security features of SurrealDB itself, and the security practices the database is developed under. To assess the service for a workload with specific requirements, use the contact form.

Email security@surrealdb.com. For a vulnerability in SurrealDB itself, submit a report through GitHub Security Advisories rather than opening a public issue.

SurrealDB asks you to:

  • Disclose the details privately to SurrealDB first.

  • Include enough information to reproduce the issue.

  • Keep the details from the public and from third parties until SurrealDB has addressed them.

  • Limit any exploitation of the vulnerability to what verifies that it exists.

  • Get permission before you run automated security tools against SurrealDB infrastructure.

In return, SurrealDB:

  • Acknowledges your report within three business days.

  • Verifies the issue, and reports progress to you.

  • Treats your report and any data you share as confidential.

  • Takes no legal action against you for a report made under this policy.

  • Credits you in any resulting advisory, unless you prefer otherwise.

Connect to the instance, then define users or access methods at root, namespace, or database level. Those credentials work across every interface: the HTTP API, the CLI, the SDKs, and SurrealDB Studio. See Connect via SDK.

Not at present. SurrealDB manages the keys that encrypt data at rest. The architecture supports customer-managed encryption keys, so they may be offered in future. Use the contact form if you need them.

Instances are reachable over the public internet by default, protected by the authentication and authorisation defined inside them.

Two additional controls exist:

  • AWS PrivateLink gives an instance a private network path from your AWS VPC. In private mode the instance gets no public hostname at all. It is available in a subset of regions, and the SurrealDB team onboards you to it.

  • Instance capabilities restrict what the engine does: which RPC methods and HTTP endpoints it serves, whether guest access is permitted, and which outbound destinations a query can reach.

You pay for the compute you consume and the storage you provision. Current rates are on the pricing page. Usage shows what an organisation has accrued so far this month.

Yes. The free instance type carries no charge, and provides limited resources for development and evaluation. It has a 1 GB storage allowance, cannot expand its storage, and pauses automatically after seven days without use.

Studio prompts you to add billing information to the organisation first.

Monthly, for the usage of the previous month. The cycle runs from the first day of a month to the last, and the invoice arrives by email. See Billing.

Yes. Enter your VAT or tax identification number in the billing details of the organisation, and it appears on every invoice.

No. All costs are on the pricing page. Prices quoted on the website exclude VAT and sales tax, and applicable taxes appear on the invoice.

Email support@surrealdb.com from the address associated with your account, and describe the query.

The Master Services Agreement governs your use of the managed service. It is on the legal page, together with the compliance and privacy documentation.

SurrealDB Inc. complies with U.S. regulations on embargoed countries and regions. It currently prohibits use of its products and services in Cuba, Iran, North Korea, and Syria. The prohibition also covers the Russian-controlled regions of Crimea, the Luhansk People's Republic (LNR), and the Donetsk People's Republic (DNR).

SurrealDB uses geoblocking to prevent logins from restricted regions. A regional block can restrict an entire country, which is beyond the direct control of SurrealDB.

SurrealDB Ltd is also subject to Article 5n(2b) of Council Regulation 833/2014. That article prohibits the supply of software for the management of enterprises, or for design and manufacture. The prohibition covers the Government of Russia and entities established in Russia.

SurrealDB reviews these obligations and updates them as regulations change.

Work through these checks in order:

  1. Confirm the instance is running and not paused. A paused instance is unreachable, and a free instance pauses itself after seven days.

  2. Check the endpoint, namespace, and database against the Connect menu of the instance in Studio.

  3. Check your credentials, and confirm the user or access method has permission on that namespace and database.

  4. On PrivateLink, confirm you connect from inside the VPC. A private hostname does not resolve outside it.

  5. Check whether the failing operation depends on a denied capability, such as an outbound HTTP call.

  6. Check metrics and logs for connection saturation or errors around the time the failures started.

If the connection still fails, raise a support ticket with the instance id.

Raise a support ticket, or ask in the Discord community. Include steps to reproduce the problem, the instance id, what you expected, and what happened instead.

Was this page helpful?