TRANSPARENCY
Where we actually are.
Honesty is the whole point of Symmate, so we keep the score in public. This is an exact account of what is real today versus what is still on the bench. If a claim isn’t here as working, treat it as something we intend, not something we’ve shipped.
Sign in (passwordless email link)
WORKING (STAGING)
Deployed and working in staging. Not yet on a public address.
Tiers + billing
WORKING (STAGING)
Wired end-to-end on Stripe test mode. No live payments until launch.
Talk to your Symmate
PARTIAL
The full path is built and deployed; it is waiting on a brain — our inference backend is mid-swap. It answers the moment that is back.
Sealed sovereign memory
PARTIAL
The crypto core is built and tested in the canonical Go runtime — XChaCha20 sealed store, per-fact sealing, key custody, tests passing. It is not yet wired into the hosted prototype you could sign up for today.
Programmatic privacy gate
PARTIAL
On the agent-to-agent path, injection detection and an outbound substitution firewall are built and running on our fleet. Structured data is provably substituted; free-text is best-effort (we won't call that provable), an earlier redaction pass was judged not-yet-trustworthy, and the full per-charter egress gate is unbuilt.
Threshold key recovery
PARTIAL
Shamir 2-of-3 — any two of {your device, your backup, a share you assign} — is built and tested (passing) in the Go runtime, not yet in the hosted prototype. Until it's wired in there, treat a lost key as lost data.
Verifiable hosted blindness
ROADMAP
On our hosted tier the design keeps us locked out — but making that provable to you, rather than trusted (hardware attestation / confidential computing), is not built. Self-hosting is the warrant-proof path today.
Sygil registry (agent-to-agent)
PARTIAL
The A2A registry and reputation transport are built and tested on our fleet — not a public product yet. Zero-knowledge personhood, group-mind, and shared capital are roadmap, in that order. See the Sygil page.
The caveats we always carry
- Spec is not shipped. A design existing does not mean it is live. This page is how you tell the difference.
- Self-hosted vs hosted are different promises. Self-hosted is genuinely end-to-end and we are locked out. Hosted, by design, keeps memory sealed under a key we do not hold and reasons close to home with only substituted data reaching the cloud brain; attestation to make that verifiable is on the roadmap.
- Key-loss is data-loss in the hosted prototype, today. Shamir 2-of-3 recovery is built and tested in the runtime, but not yet wired into the hosted product — until it is, a lost key there loses the memory.
- “zk” about your memory means encryption under keys you hold — not zero-knowledge proofs. (Sygil’s actual zero-knowledge personhood is a separate, roadmap thing.) We won’t blur the two.
- The engine is open source; the brain is rented. The runtime ships no model weights. We run frontier models by key and local quants, and the brain is swappable. The moat is the architecture and the self, never the model.
- AI disclosure is mandatory and the charters are DRAFT — unratified and unanchored — not settled law.
Why publish this. A sovereignty product that overclaims has already
broken the promise. If this page ever drifts from the truth, that is a
bug — tell us.