Your data.
Your hardware.
Your rules.
Every Writ site is its own system. It has its own identity. It has its own security approval. It runs on your hardware, in your network. When you need sites to cooperate — across bases, allies, or mission areas — they can do that too, without sharing a single control point.
What 'sovereign' actually means.
Sovereign means the system belongs to you. It doesn't need a central hub owned by a cloud company. It doesn't need permission from a vendor to run. It doesn't send your data to someone else's computers to work.
When a site goes offline, every other site stays up. When a site needs its own rules — for a classified environment, for an allied partner, for a tactical deployment — those rules stay at that site.
No mandatory internet
Writ works disconnected from the public internet. Updates ship as files you can carry on a drive into a secure facility.
No single vendor's hardware
Runs on standard Intel, AMD, ARM, and Apple Silicon. No appliance contract to renew. No hardware lock-in.
No shared master system
Each site has its own identity, its own keys, its own records. Nothing forces them to talk to a central authority.
Your approval, your scope
Each site is approved for security on its own terms. A new site can inherit the existing approval with a short update, not a year of paperwork.
Cooperation without a central hub.
Real missions often span places — a site back home, a site overseas, a tactical edge site, an allied partner. Writ lets those sites work together when the mission calls for it, while keeping each site sovereign.
Cooperation between sites is opt-in. Every cross-site request is checked against the rules of both sides. A partner site can ask a question; the home site can decide whether to answer — and how.
The data never has to leave home. When sites share learning — for example, improving a model together — the math can happen without anyone seeing anyone else's underlying information.
The full cross-site architecture — hierarchical trust roots, the four layers of cooperation, the mechanisms that keep sensitive sites separate — is documented in the Federation Architecture white paper.