Zero cache. Every request hits the vault.

Fresh every read

No sync. No cache. No stale credentials.

Most credential systems cache the vault locally and sync it in the background. That creates the problems they then have to solve: stale credentials when a teammate rotates a key, write conflicts between devices, secrets lingering on disk after a revoke, and the eternal "did the latest version sync to my laptop yet?" question.

Clavitor doesn't sync. Every credential read is a live, encrypted fetch from your vault — every time, every device, every agent. Rotate once, take effect everywhere on the next read. Revoke a key and there's no cached copy to worry about, because there isn't one.

The trade-off is latency. A read that takes 800ms turns a one-second task into a wait. So the network is built to dissolve that trade-off: 24 Points of Presence (POPs) across every continent put your vault within <60ms of where the people on your team actually work — your colleague in Tokyo, your VP in São Paulo, every co-worker on every timezone. Fresh reads + global reach is one product, not two. Every POP is dual-stack, native on both IPv4 and IPv6, so agents and people reach the vault over whatever the network gives them, with no gateway in between.

Three-tier encryption

Jurisdiction is irrelevant.

Math is not. Your vault is encrypted at rest. Your credentials are encrypted per-field. Your identity fields are encrypted client-side with a key that never leaves your device. No server — ours or anyone's — can read what it doesn't have the key to. That's the real protection. Zürich is the belt to that suspenders: a jurisdiction where nobody will even try to force open what mathematics already guarantees they can't.

Included on every plan

What you get

Continuity

Your credentials stay readable when your primary POP doesn't.

Your vault already lives in the city you chose at signup, close enough that a read feels instant. Continuity is the quieter promise: if that city has a bad day — a flood, a cut cable, a power grid that forgets itself — the same encrypted copy is waiting somewhere else, and the people and agents who depend on it keep working. The second copy is the same ciphertext you already own. The key never leaves your device, so the replica city can hold the bytes without ever reading them.

When you want that spare as far away as geography allows, we use two cities we actually trust at that distance: Dallas and Zürich. Both sit inland, on quiet ground, with power and law that do not share a single fate. Dallas gives you American contract law and a grid that is not Europe's. Zürich gives you Swiss privacy law and a country that has spent two centuries declining to take a side. We place your replica in whichever of those two is further from home, so Tokyo's spare is Dallas, Sydney's is Zürich, and a vault in London still has an ocean and a continent between it and the copy. The point is not drama. It is that a regional event should not be able to take both buildings down.

Some teams need the spare closer to home, because the law they live under is the point of the product. Same-continent replication keeps EU ciphertext inside the EU, American ciphertext inside the United States, and the UK and Switzerland together rather than folded into the Union. Africa stays with Africa, South America with South America, Japan and Korea with each other, Australia with Singapore, the Gulf with Istanbul and Mumbai. You still get a second building. You do not get a second set of courts. And if you would rather have one city and accept the silence, that is a choice too.

The pairings below are the ones we draw on the map.