---
title: "Instances"
description: "What a SurrealDB Cloud instance is. How the Start and Scale plans and serverless SurrealDB Earth differ, and where each operational task is documented."
canonical_url: "https://surrealdb.com/docs/operate/instances"
section: "Instances"
surrealdb_version: "4.x"
last_modified: "2026-11-18T02:09:16Z"
---

> Full SurrealDB documentation index: https://surrealdb.com/docs/llms.txt

# Instances

What a SurrealDB Cloud instance is. How the Start and Scale plans and serverless SurrealDB Earth differ, and where each operational task is documented.

An instance is a SurrealDB deployment that SurrealDB runs for you.

That covers provisioning, high availability, patching, backups, and version upgrades. You choose a plan, a size, and a region, then connect your application.

Every instance belongs to an [organisation](/docs/operate/organisations.md), which also holds members, usage, and billing. You operate instances from [SurrealDB Studio](https://studio.surrealdb.com), or from a terminal with [`surreal cloud`](/docs/reference/cli/guides/cloud/instances.md). To run and operate the server yourself, see [Self-hosted](/docs/operate/self-hosted.md).

[Open SurrealDB Studio](https://studio.surrealdb.com)

## Plans

A dedicated instance runs on one of two plans, and the plan you choose at deploy time fixes the topology of the instance. [SurrealDB Earth](/docs/operate/instances/earth.md) is the serverless alternative: it runs on the Cloudflare network, has no instance type or node count to choose, and scales to zero when idle. The deploy page selects Earth by default.

| Plan | Topology | How it grows | Storage | Suited to |
| --- | --- | --- | --- | --- |
| **Start** | A single node | Vertically, by moving to a larger instance type | A dedicated disk per instance | Development, staging, and workloads that fit on one node |
| **Scale** | A cluster of three nodes or more | Vertically and horizontally, by using larger nodes or more nodes | Distributed storage shared across the cluster | Production that must survive the loss of a node |

The deploy page sets the plan by the node count: one node is Start, and three or more is Scale. Start offers two workloads of instance type. **Burstable** is for prototypes, testing and low-traffic workloads, and **General Purpose** is for steady production traffic. Scale uses General Purpose nodes.

The plan also gates some options. Configurable [backup frequency](/docs/operate/instances/backups.md) is available on Scale instances only.

Current capacity ceilings and prices are on the [pricing page](https://surrealdb.com/pricing). The deploy page shows what applies to your organisation. For the topology behind each plan, see [Architecture](/docs/operate/instances/architecture.md).

## Where instances live

The **Instances** section of SurrealDB Studio lists every instance in the organisation you are viewing. Each card shows the SurrealDB version and the region. Use the search box and the **Version** and **Type** filters to narrow a long list.

![The Instances page of SurrealDB Studio for the Acme Corp organisation, listing three instance cards: api-production on SurrealDB 3.2.4, and api-staging and analytics-eu on SurrealDB 3.2.1. All three are in AWS Europe (Ireland). The page also has a search box, Version and Type filters, and a Deploy new instance button.](~/assets/img/surrealdb/manage/instances-list.webp)

Selecting an instance opens its own workspace. That workspace holds a [dashboard](/docs/operate/instances/monitoring.md) of resource use, the schema and query views, and **Settings**. Settings is where [configuration](/docs/operate/instances/configure.md), [capabilities](/docs/operate/instances/configure.md#capabilities), [versions](/docs/operate/instances/versions-and-upgrades.md), compute, and [backups](/docs/operate/instances/backups.md) live.

`surreal cloud instance list` prints the same list in a terminal, and `--json` makes it scriptable. See [surreal cloud instances](/docs/reference/cli/guides/cloud/instances.md).

## Lifecycle

You control the lifecycle of an instance with four actions.

| Action | Effect | Where |
| --- | --- | --- |
| **Deploy** | Provisions the instance on the chosen plan, type, and region | [Create an instance](/docs/operate/instances/create.md) |
| **Resize** | Changes the instance type or the storage capacity in place | [Scaling](/docs/operate/instances/scaling.md) |
| **Pause** | Stops compute and usage billing. Data and configuration are kept, and the instance is unreachable until you resume it | [Configure an instance](/docs/operate/instances/configure.md#pause-an-instance) |
| **Delete** | Destroys the instance and everything stored in it, with no way to recover it | [Configure an instance](/docs/operate/instances/configure.md#delete-an-instance) |

The diagram below shows the states an instance passes through for each action.

<img src="~/assets/img/diagrams/light/ops-instance-lifecycle-light.webp" darkSrc="~/assets/img/diagrams/ops-instance-lifecycle.webp" alt="The states of a Cloud instance. Deploy creates it in the creating state, which becomes ready. Resize moves a ready instance to updating and back to ready. Pause, accepted only from ready, moves it through pausing to paused, where no compute is billed and the data and settings are kept. Resume, accepted only from paused, moves it through resuming back to ready. Delete moves a ready or paused instance through deleting to deleted, which cannot be recovered. Ready, paused and deleted are the states that surreal cloud instance watch --until waits for." />

You cannot change an instance name after deployment. Pick a name a colleague will still recognise in six months, such as `api-production` rather than `db1`.

## Topics

- **[Create an instance](/docs/operate/instances/create.md):** plan, instance type, region, version, name, and starting data.
- **[Configure an instance](/docs/operate/instances/configure.md):** capabilities, compute, storage, pausing, and deletion.
- **[Connect to an instance](/docs/operate/instances/connect.md):** SurrealDB Studio, the CLI, SDKs, and HTTP.
- **[SurrealDB Earth](/docs/operate/instances/earth.md):** serverless SurrealDB on the Cloudflare network, and its current limits.
- **[Architecture](/docs/operate/instances/architecture.md):** single-node and multi-node topologies.
- **[Scaling](/docs/operate/instances/scaling.md):** matching compute and storage to the workload.
- **[High availability](/docs/operate/instances/high-availability.md):** what survives a node failure on each plan.
- **[Backups and recovery](/docs/operate/instances/backups.md):** automated snapshots, retention, and restore.
- **[Import and export](/docs/operate/instances/import-and-export.md):** moving data with `surreal db export` and `surreal db import`.
- **[Versions and upgrades](/docs/operate/instances/versions-and-upgrades.md):** changing the SurrealDB version.
- **[Monitoring](/docs/operate/instances/monitoring.md):** the instance dashboard, metrics, and logs.
- **[Network access](/docs/operate/instances/network-access.md):** which outbound destinations queries may reach.
- **[Private connectivity](/docs/operate/instances/private-connectivity.md):** AWS PrivateLink and instance access modes.

## Related sections

- **[Organisations](/docs/operate/organisations.md):** accounts, members, roles, usage, billing, and support.
- **[surreal cloud](/docs/reference/cli/guides/cloud.md):** the management-plane command-line tool.
- **[Observability](/docs/operate/observability.md):** the full metric, audit-log, and slow-query reference.
- **[Self-hosted](/docs/operate/self-hosted.md):** running SurrealDB on your own infrastructure instead.
