--- title: "Network" description: "24 regions, every continent. Cross-hemisphere fail-over." lang: en url: https://clavitor.ai/en/network markdown: https://clavitor.ai/en/network.md authoritative: true translations: [de, fr, es, it, pt, nl, pl, sv, da, no, fi, uk, ru, tr, ja, ko, zh, hi, th, vi, id] publisher: Clavitor LLC --- # clavitor network: Zero cache. Every request hits the vault. Clavitor never caches credentials — not in memory, not on disk, not anywhere. Every request is a fresh decrypt from the vault. That's the security model. To make it fast, we run regions across every continent. Your data lives where you choose. > Live content (`network-map`) — see the [HTML version of this page](https://clavitor.ai/en/network). ## 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. ### Vault Encryption Entire vault encrypted at rest with AES-256-GCM. The baseline. Every password manager does this. ### Credential Encryption Per-field encryption. Your AI agent can read the API key it needs — but not the credit card number in the same entry. ### Identity Encryption Client-side. The key is derived from your fingerprint, face, or security key — and never leaves your device. We cannot decrypt it. Period. ## Included on every plan: What you get ### Managed infrastructure We run it, monitor it, and keep it up. You just use it. ### Daily encrypted snapshots Point-in-time snapshots, encrypted at rest. Restorable on request — for accidental deletion or rollback, not as a fail-over substitute. ### 24 regions, your choice Pick your primary region at signup — same encryption, same SLA, every continent covered. Fail-over copy lives on the opposite side of the world (or pinned to a region of your choice for compliance). ### Automatic updates Security patches and new features deployed automatically. No downtime. ### Unlock with your device No master password to forget, lose, or have stolen. Your fingerprint, face, or security key unlocks everything — and the encryption key never leaves your device. ### AI support, any hour Get answers in seconds, not days. Our AI knows the product end-to-end and reads your account configuration — never your credentials. The same encryption that hides your secrets from us hides them from our AI too. ### Auto scope assignment On import, Clavitor extracts the domain from each credential's URL and assigns a scope automatically — "dev", "finance", "shopping". Your agents get the right access from day one, without manual tagging. ### API key recognition Clavitor detects API keys by pattern during import — OpenAI, AWS, GitHub, Stripe, and 10+ more. They're automatically separated into their own category so agents can find them without digging through password entries. ## 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. > Live content (`failover-groups`) — see the [HTML version of this page](https://clavitor.ai/en/network). ## Ready? **Free forever** for up to 10 entries — no card, no trial timer. Outgrow it, and **$1/mo** unlocks unlimited entries for one user, across every device. Every feature included. 7-day money-back guarantee. **Price for life** — your rate never increases. [Start free](https://clavitor.ai/en/checkout) [Compare plans →](https://clavitor.ai/en/pricing)