Hosted in the EU today. More planned.
The VAID primitives and the guarantees they carry are identical wherever this runs. What changes is operational: who runs it, and where your identities, policy and audit records live. This page is written so a security or infrastructure reviewer can self-qualify.
Where this stands
Hosted by us, in the EU
We operate the control plane. This is what the demo and every provisioned agent run on today.
- Hosted authority, issuing and revoking VAIDs operated for you. "Hosted authority" is our name for the aggregate of the durable pieces below plus KMS-backed keys; it isn't a single component you can point at.
- Enforcement at call time, policy decisions applied on every governed request. Cross-process enforcement across a whole estate is not shipped; the federation router is in-process today.
- Audit-of-record, a durable, hash-chained history, retained and operated for you. The audit seam is already open source in vaid; the durable ledger behind it is what's commercial.
This is the one path you can actually be provisioned on today, after a conversation, not a checkout.
Your own Google Cloud
The control plane runs inside your own Google Cloud project. In development, built for a specific customer before it is offered generally.
- Your environment, the control plane runs inside your Google Cloud, not ours.
- For teams that need their own cloud boundary but are not yet asking for air-gapped or on-premises operation.
- Same open primitives, the same VAID standard underneath, with a commercial agreement for the operated components.
Not self-serve and not generally available while it is still being built for the first customer.
AWS, Azure, on-premises and air-gapped
After the Google Cloud path above: AWS, Azure (including Azure Government, for US public-sector requirements), on-premises Kubernetes, and fully air-gapped operation with no network path out. None of this work has started, and we will not invent a date for it.
What doesn't change
The VAID primitives and the guarantees they carry, a signed action anyone holding the signer's public key can verify, capability scoping, lineage, a tamper-evident record. The format and the signing contract are the same wherever this runs; that's the point of an open standard. Verifying a VAID issued by another deployment additionally needs that deployment's key, Planned.
What does change
Who operates the control plane, and where your identities, policy and audit records physically live. Today that's us, in the EU. Next is your own Google Cloud; everything after that is planned, not built.
SYNTHERA is the trust layer for multi-agent systems: every agent gets a verifiable identity, scoped authority and a tamper-evident record, so software from different teams, vendors and frameworks can act on each other’s behalf without custom glue between every pair.
Find the deployment that fits your constraints.
Tell us your residency, air-gap or operational requirements and we'll say what's possible today, what's being built, and what's only planned.