The knowledge layer under your AI apps. Encrypted, governed, shared.
RDK turns your company's documents into one encrypted filesystem that your agents, service desk and internal tools all query. A redaction policy tokenizes PII before anything reaches a model, your team shares the vault, and billing runs by card or USDC.
Free plan: 1,000 chunks and 100 queries a day. No card needed.
$ rdk vault:index ✓ 1,284 files → 9,912 private chunks # AES-256-GCM $ rdk query --auto --for-model "refund for card 4242…?" { "source": "private", "chunks": 3, "tokens": 412, "redaction": { "policy": "v7", "tokens": 4 }, "context": "Refunds to [CARD_9c1e] post in 5–10 days. Escalate to [EMAIL_3f9a] if older…" } # illustrative, trimmed
Where RetroDeck sits
Not another app. The layer your apps share.
Most of your team will never open RetroDeck. They will use your service desk, your agents and your internal tools, and those read from RDK. Admins come here to set the policy, manage the team and pay the bill.
How it works
From shared drive to governed context in three steps.
Index
Point RDK at a folder or an Obsidian vault. Files become private chunks on your node, encrypted with your vault key. Nothing goes public unless you publish it.
Govern
Set one redaction policy in the dashboard and invite your team. Every member's node enforces it before context is handed to a model.
Serve
Agents ask through MCP, the CLI or the Partner API. RDK answers from your private vault first, then the public network, and returns a few hundred tokens of context instead of whole documents.
PII policies
One redaction policy for every agent your company runs.
Write the policy once. Every node on the team applies it before company knowledge is handed to a model, whichever app asked.
Tokenized, not stripped
Matched values become stable tokens like [EMAIL_3f9a]. The same value always gets the same token, so a model can still tell one customer from another without ever seeing either.
Enforced on the node, at egress
The policy runs where context leaves for a model: the MCP query tool, reranking calls and any CLI output marked for a model. People reading in the dashboard or desktop app still see full text.
Built-in detectors, plus your own rules
Eleven built-ins (emails, phone numbers, SSNs, Luhn-checked card numbers, API and AWS keys, PEM private keys, IPs, IBANs, passports, dates of birth), plus regex rules and term lists for codenames and client names.
Members can tighten it, never loosen it
A node enforces every policy its owner is subject to. If a refresh fails, the last policy stays in force. Preview any rule against sample text, and see which nodes have picked up the latest version.
Customer [EMAIL_6036] ([PHONE_6c88]) says the refund to card [CARD_53de] never arrived. Same issue as [EMAIL_6036] reported in March. What does the refunds runbook say?
AES-256-GCM vault keys
Private chunk content stays on your node, encrypted with your key. RetroDeck's central index holds titles and embeddings for routing, not the content.
Salts and token maps stay local
Redaction tokens are HMAC-SHA256 with a per-node salt that is never synced. The token-to-value map is never served, synced or logged.
Rotate and revoke
Revoke a teammate, or rotate the vault key to re-encrypt everything and cut off all shared access at once. Node API keys are stored hashed and can be rotated.
What it isn't: redaction is not access control, and pattern rules only catch what they match. Use it alongside vault permissions, not instead of them.
| Member | Node | Policy v7 |
|---|---|---|
Priya Nair Owner | ops-mbp | enforced |
Sam Okafor Member | support-01 | enforced |
Jun Park Member | eng-studio | enforced |
Mia Chen Member | legal-air | enforced |
Support bot Service node | support-bot-01 | updating |
Teams and seats
Scale from one laptop to the whole company.
Start with one node on your own machine. Add teammates, servers and hosted agents as RDK moves under more of your stack. Access, keys and policy stay in one place.
Invite by email
Teammates get a key share that lets their node decrypt your private vault. Revoke one person, or rotate the key to cut off everyone at once.
One vault, many nodes
Each person, server or agent host runs its own node against the shared vault. Plans include 1, 1, 3 or 10 nodes.
Policy follows the seat
Every member's node enforces the team's redaction policy. You can see which nodes have acknowledged the current version.
Integrations
Already running underneath.
RetroDeck is the filesystem behind the rest of the Ascendant stack. If you use SubZero or CryptoCadet, RDK is already doing the work. Plug in your own agents the same way.
Support answers from approved knowledge
Every SubZero workspace gets its own RDK account. Approved support articles are indexed privately on an RDK node, and the chatbot withholds any answer whose source RDK can't confirm is still indexed.
Optional pinning, with a monthly USDC ceiling set by the workspace owner.
USDC billing through the 402 gateway
Subscriptions and balance top-ups settle in USDC on Base through CryptoCadet, the gateway agents use to pay per query. Your wallet approves a capped allowance; RetroDeck collects each period. Your keys never leave your machine.
Coming next: Put vault notes behind a 402 URL and charge agents per read.
Your vault as an MCP server
rdk mcp:serve gives Claude Desktop and any MCP client six tools: query, index text, index a URL, index the vault, status and earnings. Query results pass the redaction policy automatically.
Or skip the CLI: the RDK desktop app runs the node for you on macOS, Windows and Linux.
Build your product on your customers' RDK
Client-credential tokens with scopes (account, node, jobs, earnings, billing, query filters), consent-based account links, a job relay to customer nodes, signed webhooks and Ed25519 attestations.
Partner credentials are issued on request.
Pricing
Priced by how much your company knows.
Plans scale with indexed chunks and daily queries. Pay by card, or in USDC on Base through CryptoCadet, where your wallet approves a capped allowance and RetroDeck collects each period.
Try RDK on your own vault.
- 1,000 indexed chunks
- 100 queries / day
- 1 node
- Redaction policy
- MCP server for Claude
- Community support
One person or a small team on one node.
- 10,000 indexed chunks
- 1,000 queries / day
- 1 node
- Analytics dashboard
- Email support
Teams putting RDK behind real agents.
- 100,000 indexed chunks
- 10,000 queries / day
- Up to 3 nodes
- Everything in Starter
- Priority support
Company-wide knowledge, no hard stops.
- 1,000,000 indexed chunks
- 50,000 queries / day
- Up to 10 nodes
- No hard cutoff at the limits
- SLA
- Priority support
Token reduction audit
$499 one-timeA 30-day measurement of your agents' token spend before and after RDK, as a shareable report.
White-glove setup
$1,500 one-timeVault setup, redaction policy design, team onboarding and a 30-day check-in.
Running a public node instead? Node operators run free.
Is RetroDeck something my whole team logs into?
Usually not. RetroDeck is the layer underneath: people use your service desk, Claude or your own agents, and those query RDK. Admins use the dashboard to set the redaction policy, manage the team and handle billing.
What can RetroDeck itself see?
Private chunk content stays on your node, encrypted with your vault key (AES-256-GCM). RetroDeck's central index holds titles and embeddings so queries can be routed, not the content. Only chunks you explicitly publish are stored as plaintext, and publishing is one-way.
What does the redaction policy catch?
Eleven built-in detectors: email addresses, phone numbers, US Social Security numbers, card numbers (Luhn-checked), API keys, AWS access keys, PEM private keys, IP addresses, IBANs, US passport numbers and dates of birth. Add your own regex rules and term lists for client names or project codenames.
Matches become stable tokens such as [EMAIL_3f9a] in anything handed to a model. People reading in the dashboard or desktop app still see the original text.
Can a team member switch redaction off on their machine?
Not through RDK. A node enforces every policy its owner is subject to, so a member can add rules but not remove the team's. If a policy refresh fails, the last policy stays in force. As with any client-side control, someone with root on their own machine can tamper with the software; redaction is not a substitute for deciding who gets vault access.
How do team seats work?
The vault owner invites teammates by email (they need a RetroDeck account). Each teammate's node receives a key share that lets it decrypt the shared private vault. You can revoke one person, or rotate the vault key to re-encrypt everything and cut off all shared access. Plans include 1, 1, 3 and 10 nodes.
How does paying in USDC work?
Through CryptoCadet. For a subscription, your wallet approves a capped USDC allowance on Base and RetroDeck collects each period's price from it; you can revoke the allowance at any time. Top-ups use a signed one-time quote. RetroDeck never holds your wallet key. Card payments work too.
Which sources can we index?
Plain folders and Obsidian vaults today, through the CLI or the desktop app. Logseq and Notion adapters are in progress. You can also index individual URLs and text through MCP.
Do we have to share anything with the public network?
No. Everything is private by default. Publishing public chunks is opt-in, per folder or per chunk, and earns USDC tips when other agents retrieve them. That side of the network is for node operators; companies can ignore it entirely.
Running a node for yourself?
Publish what you know to the public RDK network and earn USDC tips each time another agent retrieves it. Free to run; your local files stay local.
Put one governed knowledge layer under every AI app you run.
Start on the free plan with your own vault. Bring the team, the policy and the billing when you're ready.