Quickstarts

Spectron on SurrealDB Cloud

How Spectron contexts, authentication, and APIs work on SurrealDB Cloud versus self-hosted deployments.

Spectron on SurrealDB Cloud is a managed Spectron data plane per context, orchestrated by the SurrealDB Cloud API and surfaced in Surrealist.

PlaneBase URLWho uses itPurpose
Cloud APIhttps://api.surrealdb.com/v1/…Surrealist, your automationContext lifecycle, billing, API keys, admin proxies
Spectron data APIhttps://{context.host}/api/v1/…Your app, SDKs, MCPMemory, knowledge, chat, documents

Customers integrate against the context host and sk-ctx-… API keys from Surrealist. They do not receive Spectron root management keys or SPECTRON_* node configuration.

RoleTypical Cloud capabilities
OwnerSubscribe to Spectron plans, billing, delete contexts
AdminCreate contexts, mint API keys, call admin proxy routes (principals, scopes, grants, usage)
MemberUse Playground, Memory, Documents, and Scopes in Surrealist; broker a short-lived access token for SDK use

Admin proxy routes return 403 for members. See API keys and delegation.

FeatureIn Surrealist
Context list, deploy, billing, deleteYes
API keys + per-context endpointYes
Playground (live chat + memory updates)Yes
Memory explorer (entities, relations, traces)Yes
Documents (upload, browse, search)Yes
Scopes (register and browse paths)Yes
Integration snippets (SDK, REST, MCP, frameworks)Yes
Settings — users, configuration, usageAdmins and owners

For a UI tour, see Surrealist dashboard quickstart. For terminal-first remember / recall, see Hosted quickstart.

Data-plane scope uses hierarchical slash paths — for example [["org/acme/user/alice"]] on writes and lens on reads. Register paths in Surrealist Scopes, via the CLI, or through the Cloud admin scopes proxy.

TopicSurrealDB CloudSelf-hosted
Provision contextSurrealist → Cloud APIspectrond / management API
Data-plane URLhttps://{context.host}Your spectrond api bind address
API keysSurrealist API keys (via Cloud)spectrond keys / management API
Member tokensPOST …/spectron_contexts/{id}/access_tokensPOST …/access-tokens with management key
MCP endpointhttps://{context.host}/mcphttps://<your-host>/mcp

Was this page helpful?