DocsConcepts

Local, Hosted Sync, and BYODB

Understand the three operating modes, when SurrealDB matters, and why the hidden local engine is not the same thing as BYODB.

surrealdbbyodbhostedlocal

Coppermind has three operating modes:

  • Local: the default local-first runtime
  • Hosted sync: the optional managed cloud layer
  • BYODB attach: the advanced paid mode that routes to your own infrastructure

The important distinction

The hidden local SurrealDB companion used by the default runtime is not BYODB.

It is a Coppermind-managed local implementation detail.

BYODB starts only when you explicitly attach your own infrastructure through the cloud control plane.

Local mode

In local mode:

  • no account is required
  • no API key is required
  • Coppermind manages the local backend for you
  • local memory is authoritative

This is the normal starting point for most users.

Hosted sync

Hosted sync is the optional cloud convenience layer.

That is where Coppermind handles:

  • account identity
  • billing
  • dashboard visibility
  • cross-device or cross-client managed features

BYODB attach

BYODB attach is the advanced paid path for teams that want their own infrastructure behind Coppermind's routing and controls.

Choose it only when you already know you want external infrastructure in the loop.

When SurrealDB matters

For most new users, SurrealDB should not be a setup decision.

It becomes relevant when:

  • you are trying to understand the local backend architecture more deeply
  • you are using or evaluating BYODB attach
  • you are operating the advanced cloud-connected path

Which mode should I choose?

Use local if you want the fastest, simplest, and most private setup.

Use hosted sync if you want cloud convenience and dashboard features.

Use BYODB attach only if you want your own infrastructure and already expect a more advanced paid setup.