Your keys, your memory, your call
stored is built around ownership, not opacity. Bring your own OpenAI key, hold per-org API keys, and inspect or self-host the open-source engine. Every memory is visible, editable, and deletable — with provenance, never a black box.
Your keys
Your OpenAI key is encrypted at rest per org; per-org API keys are stored hashed and shown once.
Your memory
Every memory is visible, editable, and deletable, with provenance on who wrote it and when.
Your engine
Built on the open-source agentwiki engine — inspect exactly how it works, or self-host it.
Built around ownership, not opacity
Five protections you can verify, each grounded in how the product actually works. Expand any one for the detail.
Straight answers
What we claim — and what we don't
We'd rather be precise than impressive. The protections on this page — BYO OpenAI key encrypted at rest, per-org API keys stored hashed, role-based access, and fully visible, editable, provenance- tracked memory — are real and grounded in how the product works. The best proof isn't a logo on this page; it's that the engine is open source, so you can read precisely how memory is stored and retrieved.
If you have specific requirements — custom contracts, bespoke quotas, or a deeper security review — that's an Enterprise conversation, and we're happy to have it.
Memory you can see — and stand behind
Start free with your own OpenAI key, hold your own API keys, and inspect the engine whenever you like.
No credit card required · Bring your own OpenAI key · Open-source engine