monopole.cloud
Docs Launch console
v3.2 — magnetic charge consensus is now generally available

Distributed compute,
powered by monopoles.

monopole.cloud routes workloads across a lattice of magnetic-monopole nodes — each carrying an isolated unit of magnetic charge — to deliver deterministic latency, charge-conserving consensus, and infrastructure that behaves more like a field than a fleet.

Provision a region Read the white paper
SLA 99.999%
Edge nodes 14,208
p50 routing 3.1 ms
Charge balance ±0
Lattice status — all regions nominal
monopole://us-east-1/lattice/4f2a-9c01
// 01 — platform

A cloud that conserves magnetic charge.

Every primitive in monopole.cloud is built around a single physical invariant: across the lattice, the sum of north and south magnetic charges always cancels. We turned that constraint into the strongest consistency guarantee in distributed systems.

Charge-conserving consensus

Replace Paxos and Raft with our Dirac protocol. Writes propagate as charge displacements; commits are field rebalances. Linearizable across continents with no leader, no split brain.

commit ⇄ Σq = 0

Monopole compute

Schedule workloads onto isolated north or south charge nodes. Pair them and you get a dipole worker — a stateless function with built-in symmetry checks and zero-trust attestation.

mc run --polarity=north worker.wasm

Field-aware storage

Objects are stored as flux loops across the lattice. Erasure coding becomes flux conservation: lose any node and the field naturally reroutes — no rebuild jobs, no degraded reads.

PUT /flux/v1/object

Deterministic edge routing

Requests follow the gradient of the local magnetic field — the path of least resistance. No DNS round trips, no anycast guessing. The network itself is the load balancer.

∇·B → nearest dipole

Zero-trust by topology

Identity is bound to magnetic charge. A token cannot be replayed on a node of opposing polarity — the field rejects it. Attestation runs at the speed of physics.

iam.attest(charge=±1)

Observability as flux

Metrics, logs, and traces emerge as perturbations of the field. Subscribe to a region and watch the lattice breathe. No agents to install, no scrape configs to manage.

tail --region eu-north-2
// 02 — architecture

Three layers, one field.

The monopole stack is intentionally thin. Each layer publishes a charge profile to the layer below; the field handles the rest. There is no message bus, no service mesh, no sidecar. Just polarity, gradient, and conservation.

L3

Application Field

Where your code lives. Functions, services, and pipelines are expressed as charge sources and sinks; the runtime resolves them into running workloads on the nearest compatible nodes.

  • monopole functions (Wasm, JVM, Python)
  • flux pipelines & cron dipoles
  • charge-scoped secrets
L2

Lattice Plane

The control plane expressed as a field. Every node continuously broadcasts its charge; the plane integrates them into a global potential that decides scheduling, replication, and routing.

  • Dirac consensus protocol
  • flux-loop object store
  • polarity-aware IAM
L1

Monopole Substrate

Custom silicon hosting isolated magnetic monopoles in shielded cryogenic cells. This is where the physics lives — and where every guarantee above ultimately resolves to a measurable charge.

  • cryo-cell node — 4 mK operating temp
  • spin-ice fabric interconnect
  • charge attestation TPM
// 03 — regions

A lattice that spans the planet.

Every region is a self-balancing pair of north and south charge clusters. Provision capacity in any region and the lattice will mirror it on the opposite polarity automatically — your data is always charge-neutral, always whole.

Region Polarity pair Edge p50 Charge balance Status
us-east-1 · Ashburn N₁ ⇄ S₁ 2.8 ms +0.0001 nominal
us-west-2 · Hillsboro N₂ ⇄ S₂ 3.4 ms −0.0002 nominal
eu-north-2 · Stockholm N₃ ⇄ S₃ 3.1 ms +0.0000 nominal
ap-south-1 · Mumbai N₄ ⇄ S₄ 4.0 ms +0.0003 balancing
ap-northeast-3 · Osaka N₅ ⇄ S₅ 3.6 ms −0.0001 nominal
sa-east-1 · São Paulo N₆ ⇄ S₆ 4.7 ms +0.0002 nominal
// 04 — console

Provision in a single field equation.

The monopole CLI is declarative all the way down. Describe the charge profile you want; the lattice converges to it. No imperative apply, no drift detection — the field is always the source of truth.

terminal manifest.toml field.log 
$ mc init --region eu-north-2 --polarity dipole
// resolving lattice ............ ok
// attesting charge cells ....... ok (Σq = 0)
// binding identity ............. monopole://you

$ mc deploy ./service.toml
// 4 dipole workers requested
// field gradient stable
// commit 7c0f4a — ready

$ mc tail --field
∇·B region=eu-north-2 mag=0.0007 stable=true
∇·B region=eu-north-2 mag=0.0006 stable=true
∇·B region=eu-north-2 mag=0.0006 stable=true

Ready when the field is.

Spin up your first dipole workload in under 90 seconds. No credit card. No quotas on charge.

Open the console Read the docs