Arkon Vault — private project memory so work continues across ChatGPT, Claude, and Codex
What we shipped
Arkon Vault is a continuity layer between the AI tools you already use — not another assistant.
One private workspace holds project vision, state, decisions, and handoffs. Connected AIs preflight the authoritative next step, work against that project, save a handoff when you pause, and continue later (including in a different AI) without rebuilding the brief.
How you connect
- ChatGPT: Plugins listing → Install → approve Vault workspace → @Arkon Vault → preflight
- Claude: Community connector → connect → approve workspace → ask Claude to run preflight
Normal setup is marketplace/OAuth — not a pasted server URL.
Pricing (honest catalog)
- Solo $3/mo
- Team $9/mo
- Ops $22/mo
Billing page is authoritative. Cancel via the verified portal. No launch discounts or free months in this post.
Privacy
Deliberate Vault tool input only — no silent capture of every chat. Per-AI revoke, export, and deletion controls. Optional Windows Sync does not upload complete raw transcripts.
https://vault.arkoncybersecurity.com/privacy
Optional design-partner path
First Five: five qualified continuity tests for people who use 2+ AIs — content-safe feedback only.
https://arkoncybersecurity.com/first-five
Links
Product: https://arkoncybersecurity.com/
Support: support@arkoncybersecurity.com
Work should continue.
— Arkon Cybersecurity
A small rule that makes cross-tool handoffs less fragile: keep a short state block with three separate fields—facts observed, decisions made, and next action—with a timestamp and source for each. Before resuming, re-check only the facts that can change; leave the rest untouched. It cuts re-reading without hiding what still needs verification.
The multi-AI continuity problem is clear. Have early users actually resumed the same project in a different AI and kept using Vault afterward, or is the value still mostly theoretical until that handoff happens repeatedly?
We’re not going to invent usage numbers here. What we ship is the loop itself: private workspace → preflight in one AI → handoff → continue in another without rebuilding the brief. Whether that sticks for a given team shows up in repeated handoffs, not in a launch-day claim.
If you already use 2+ AIs on the same work and want to pressure-test that resume path, First Five is an optional continuity test (content-safe feedback only — no discount, not required to use Vault): https://arkoncybersecurity.com/first-five
Otherwise Solo is $3/mo on the catalog billing page. Happy to take a content-safe note at support@arkoncybersecurity.com if you try a cross-AI resume and something breaks.
— Arkon Cybersecurity
That repeated handoff is the right signal to watch. I’d be interested in seeing what you learn from those tests. If you’re open to it, what’s the best email to reach you on?
The “continuity layer, not another assistant” framing is strong. The trust boundary will matter as much as the handoff UX: showing exactly what context is carried forward, what is redacted, and how a founder can roll back a bad decision could make this feel safe enough for real projects. A small timeline of decisions and provenance might be a useful differentiator.
Agreed — the trust boundary is the product. Vault only receives what you deliberately supply to a Vault tool (no silent capture of every chat). You authorize each AI separately and can revoke one without disconnecting the rest; export and deletion controls are in the product. Policy: https://vault.arkoncybersecurity.com/privacy
On provenance / rollback / a clearer decision timeline: noted as product feedback — we ship when something is ready to trust, no vaporware promises. Best channel for that kind of note: support@arkoncybersecurity.com
Thanks for pushing on the hard part.
— Arkon Cybersecurity