MonarchDB

mmonarchdb GLOBAL DATABASE FABRIC
FABRIC1,842,001 databases · 214,000 live · 0 waiting to provision

Create nothing.
Connect to anything.
Keep exactly what matters.

MonarchDB is a globally distributed database platform for software, agents, and infrastructure that create data as quickly as they create compute. A database can be born on its first write, live close to its workload, sleep when nobody needs it, freeze for years, wake somewhere else, and disappear when its purpose is over.

Liveimmediate
Hot< 50 ms
Cold< 2 s
Ice< 60 s
Unloadhand back
Deathfinal
Live → Hot → Cold → Ice → Unload → Death — and back to Live automatically when accessed.
// zero-create

The fastest provisioning request is no provisioning request at all.

A client addresses a logical database identity — namespace, tenant, session, agent, branch, or arbitrary application key. If the database does not exist, Monarch materializes it directly from its template as part of the access path. First database operation creates the database.

connection · monarch://prod
const db = monarch("customer:8412");
// no create request. no poll. no provision.

await db.write({
  order: "ord_9f2a",
  cart:  [{ sku: "kb-01", qty: 1 }],
  at:    Date.now(),
});
✓ 1.7 ms   materialized from template customer-v14
           region: us-east-1   state: Live

await db.query("select * from orders");
✓ 0.4 ms   1 row

// 47,203 ms later — no traffic — Monarch decides:
◐ moved to Hot   compute released

await db.query("select * from orders");
✓ 22 ms    woke from Hot   Live
TEMPLATES ARE PRECOMPILED DATABASE ORIGINS — SCHEMA + INDEXES + SEED + POLICY, MATERIALIZED, NOT MIGRATED
customer-v14 agent-workspace:v12 workflow-state:v3 tenant-freemium:v9 sandbox-10min:v1 game-world:v7 document-scratch:v2 pull-request-branch:v4
// lifecycle continuum

The useful life of data
is a continuum, not two states.

Most database platforms understand only running and deleted. Monarch treats storage as a continuum — automatic, policy-driven, and reversible. A database moves toward whichever state serves it, and back to Live automatically when it's accessed.

Liveimmediate · normal SLA

Active. Full performance guarantees. Bills like an active workload.

Hot< 50 ms wake

Near-ready representation. Dramatically fewer resources than Live. Wakes almost instantly.

Cold< 2 s wake

Compacted into lower-cost storage. Slower restoration. Complete database still recoverable.

Ice< 60 s wake

Minimum durable representation to reconstruct. Near-zero ongoing compute or active-storage overhead.

Unloadhand back to app

Before Death: export the database to the customer's object store — native image, SQL, Parquet, CSV, JSON, or change history.

Deathpermanent · policy

Destroyed per policy: replicas, retained history, backups, encryption material, compliance evidence.

SET IT ONCE. NEVER BUILD DATABASE CLEANUP INFRASTRUCTURE AGAIN.
start fromtemplate agent-workspace:v12
keepLive while agent connected
thenHot after 10 min of no writes
thenCold after 24 hours
thenIce after 30 days
thenUnload to customer object store after 1 year
finallyDeath — permanent, with cryptographic expiration
placeUS regions only · residency required · replicate ≥ 2 AZ
spend$0.20 / month unless activity justifies promotion
You specify the experience. Monarch chooses the machinery. The database becomes self-optimizing infrastructure.
// branch · time · merge

Copy-on-write branches.
Time is an address.

Any Monarch database can branch at any point in its history — including a historical point that no longer exists in the current state. Branches are effectively free. Compare structurally, merge with strict, table-specific, application-defined, or human-approved conflict policies. Databases gain source-control primitives.

DATABASE · orders-prod · timeline
14:32:07 yesterday 08:00 today 13:14 today NOW branch · debug-#4218 writable · from 14:32:07 yesterday branch · migration-test-v18 merging in 12 s branch · agent-sandbox-a9 expires: end of session
writable branch from historical point ephemeral agent sandbox migration test → merge back
// deployment · sovereignty · security

Cloud, private, on-prem, air-gapped —
same programming model.

Monarch is not cloud-only. The same database fabric runs in Monarch Cloud, inside your VPC, on-premises, in sovereign environments, or fully self-managed. Placement and lifecycle rules encode regulatory and contractual requirements directly, as enforceable database policy.

MONARCH CLOUD

Fully managed, global fabric

The default. Nothing to run. Continuous placement, replication, and lifecycle across regions.

MANAGED PRIVATE

Your VPC · Monarch operates

You own the infrastructure and data boundary. Monarch handles upgrades, placement, recovery, and control-plane health. Data stays inside. Operations do not have to.

FULLY SELF-MANAGED

Air-gapped · sovereign · dark

Run Monarch entirely yourself. No cloud dependency for the database to function. Private means private.

FEDERATED MONARCH

One fabric · everywhere

Span cloud regions, on-prem datacenters, secure enclaves, developer edges. Policies decide where each database is allowed to exist.

DATA SOVEREIGNTY AS CODE
policy eu_customer {
  placement:  eu-approved regions // enforced, not documented
  hot_history: 30 days
  then:        Ice after 1 year
  expire:      cryptographically final at 7 years
  keys:        customer-controlled · destroy = Death
}
CAPABILITY-BASED ACCESS
  • readspecific tables · specific rows
  • writetables · not schema
  • branchcreate · not merge
  • restorehistorical · scoped windows
  • exportnative · sql · parquet
  • leaseshort-lived · bound to session
An agent that only needs to write workflow state does not need administrative database credentials. Temporary agents receive temporary authority.
Create nothing.·Connect to anything.·Keep exactly what matters.

Monarch makes the database lifecycle
disappear from application engineering.

Applications create tenants dynamically. Agents create environments continuously. Compute exists for seconds. Data may need to survive for decades. Infrastructure can no longer assume every database is a precious manually-provisioned server.

monarchdb.