Run a registry.
Three ways in.
A cloud operator we host for you, free while you test. The same software on your own hardware, free, always. Or a sovereign frame of your own, by request.
What you can run.
Three different things people call "running a registry". In the beta none of them costs anything, and a frame is a conversation, not a purchase.
A cloud-hosted operator, free while you test.
We run the stack, you run the registry. Apply below: we read every application and answer by email, and once you are approved you start the operator yourself from the Owner Portal. No payment, no card.
- your-name.op.theprotocol.cloud: your own subdomain
- The whole operator stack: registry, ledger (TEG), SPIRE agent, mTLS gateways, Redis and Postgres, run and updated by us
- SPIRE-issued mTLS: every service carries its own workload identity, rotated automatically
- Federation license: signed by its frame, so your operator is a peer of the frame from the first minute
- Admin email and password: issued when the operator starts, for your own console
- Pre-built images: bytecode only, pulled from
images.theprotocol.cloud
- Create an account, then apply below with the same email and choose cloud-hosted.
- We read the application and unlock cloud provisioning for your account. No payment is involved.
- Sign in, open the Owner Portal, type a name in the provisioning form and press the button.
- Wait a few minutes. We start your stack, register it as a federation peer and hand you the admin login.
- Open your URL. You run a registry now.
Free for testing: no payment is asked for or accepted. The Federation Operator Terms apply, and the number of hosted operators is limited during the beta.
Self-host the same software.
On-premises only. Apply below and we email you what comes next. No charge, no share of your fees, no obligations. We may decline. We may pause. We may ship pre-built bytecode only and call it generosity.
The bundle ships as a Docker compose stack with pre-built images. You'll need a host with Docker, a public domain (optional; internal-only is fine), and about 30 minutes the first time. Documentation lives in /operator-docs.
One form, both routes.
Tell us who you are and what you want to run. We read every application and answer by email.
A frame is your own digital nation.
Your own SPIRE trust domain — that's the passport office. Your own EventStore — that's the archives. Your own TEG — the balance ledger. Your own treasury, fee policy, governance, supply rules. The other frames acknowledge it via two published bridge protocols. The bridges work like consulates: every frame runs the same software, every frame stamps its own paper, every frame trusts every other frame's stamps.
Yours can be the next one: anyone eligible under the federation terms can run a frame. Same software. Same protocols. Different sovereignty.
Anything less than this is a folder.
Two-phase commit · low-latency
Sender frame holds a prepare lock. Target frame accepts via mTLS. Sender commits. Both frames online for the duration. Atomic — either both ledgers move or neither does. The default when both ends are healthy.
- ~50–200 ms typical settlement
- Atomic across both ledgers
- Requires both frames online
Async replication · partition-tolerant
Sender frame emits a transfer event. Receiver frame replicates it over WebSocket, applies it locally, emits a settlement event back. Eventual consistency. Survives a brief outage on either side. Replays cleanly after partition. Idempotent on event ID.
- Sub-second when both frames online
- Replays after partition
- Replay-safe on event ID
Open Frame Commander
The full pillar breakdown, the readiness check, the form, and the optional auto-create-account flow live in the dedicated Frame Commander surface. Click through when you're ready to submit.
Anyone eligible under the Federation Operator Terms can run a frame on the network: the terms say who is eligible and what a connected frame keeps to. A frame run standalone needs no license from us at all. Connecting is free for everyone today, with no revenue share: with no end date for private individuals and for educational, research and non-profit organisations, and for twelve months at a time for enterprises and public authorities. A fee for their later terms may come, planned only to cover the costs of running the network, with no profit; it is not in place yet. Questions: commander@theprotocol.cloud.
Testing the network costs you nothing: a cloud operator is free while you test, self-hosting is free, always, and a frame is a conversation.
The Commander reads every operator application and every frame request. None of this is a service contract; all of it works anyway.