A SurrealDB Cloud instance is a managed SurrealDB deployment you operate from the dashboard or Surrealist. This page summarises lifecycle actions and placement options.
Creating instances
When you create an instance, you choose a plan (Start or Scale), a region close to your applications, and an instance type (CPU, memory, and storage profile). Start provisions a single-node instance with dedicated storage. Scale provisions a multi-node cluster on SurrealDS — at least three compute units by default — for fault-tolerant, horizontally scalable workloads. Options such as network access mode depend on your organisation and plan.
Give each instance a clear name so teams can find it in the organisation view. See Cloud architecture for how plans map to topology.
Pausing and resuming
Pause an instance to stop compute charges while keeping storage and configuration. Resume when you need the database online again. Pausing is suited to non-production environments or predictable downtime; always confirm whether connections and automated jobs tolerate the outage.
Unused free instances will be paused automatically after 7 days.
Deleting instances
Delete removes the instance and its data from Cloud according to the product behaviour shown at confirmation time. Ensure you have backups (paid plans) or a logical export before deletion if you might need the data later.
Instance types and regions
Instance types balance vCPU, memory, and I/O for different workloads. Regions affect latency to clients and data residency; pick the same region as your app stack when possible.
First-time setup
If you have not created an organisation or connected a client yet, follow Getting started with SurrealDB Cloud for account setup, instance creation, and connection strings.