How Recued works
Recued is the local control plane between any AI, the people who reach you, and the accounts and data on machines you own. Agents and people ask, and Recued does jobs of its own. All of it passes one gate: grants are checked, personal data is shielded, and writes wait for your yes. Recued acts locally with your keys and records every run, and running work can be watched live, killed, or paused outright.
Reading the diagram
- Start in the middle — the control plane. The center is Recued, the local daemon you run, encrypted at rest. It holds your data (mail, calendar, files, contacts, tasks, notes, CRM, the things you own, memory and timeline) and does jobs of its own — a chat you reach in the app, by email, in Slack or Telegram, and recipes run by hand, on a schedule, or when something happens — beside the Contracts and Gateway boundary, Approvals, and the Logs audit trail. Everything is local: Recued's cloud gives your server a name and a certificate, and your data never passes through it.
- Your systems, outbound. Through Connections and packs, Recued reaches your own APIs, mail and calendar, CRM and accounting, payments, files, MCP servers, command-line tools, coding agents, notifications, and webhooks with scoped read and write. Keys stay on your server, or with a managed-OAuth broker you pick — never in Recued's cloud.
- People, inbound. People reach you through Reception and Messenger — booking and intake, file drop, quotes and sign-offs, approval links — and you reach Recued the same way, in Slack, in Telegram, or by email. Requests land in your Reception inbox and writes wait for review; public pages expose declared fields only, and your private data is never shown.
- External agents, inbound. Any MCP app — Claude Code, Claude Desktop, Codex, Cursor, Cline, OpenClaw, your own, or a peer Recued — and chat apps that speak the OpenAI API call in through a contract: one key, with nothing granted until you choose. Customers you sell access to come in the same way, in tiers through your own Stripe, and Recued takes no cut. Agents receive contracted tools, never your account keys.
- The LLM boundary, round-trip. Chat, AI steps, and background AI route through policy. Personal data is aliased before it leaves — Person1, m1@d1.invalid, addresses and links — the model reasons over the aliases, and Recued restores the real values locally. Facts on file go to the model first, and a plain lookup needs no model at all.
- Follow the gate. Every call — from agents, people, and Recued's own jobs — passes the Contracts and Gateway boundary once, in order: check the contract, ask if needed, record, run. Unknown callers fail closed, and one master pause halts everything. AI writes and outward calls wait for your approval, answered in the app, by email, Slack, or Telegram — one, a batch, or a whole session — and allowed, denied, blocked, and approved calls all land in Logs, recorded before they run. Account keys are decrypted only to run the call. Running work can be watched live, killed, or paused — controls on the work, never on the record.
The four flows
The arrows in the diagram carry the story.
Local read and write. Server to your systems and back — bidirectional, and the keys never leave the machine.
The inbound ask. Agents call in over MCP; people arrive through Reception and Messenger. Both terminate at the gate.
The gate. Contracts and approval. Every call passes here before anything runs.
The AI round-trip. Out to an LLM with personal data shielded, back with the answer to restore locally.
The surfaces
- Recued
- The local daemon you run — the control plane itself: your data, its own chat and recipes, the Contracts and Gateway boundary, approvals, and the Logs audit trail. It runs on a machine you own, encrypted at rest.
- Contracts
- The grants surface. A contract holds one key and grants nothing until you choose — the inbound twin of Connections.
- Connections
- Outbound endpoints to your own systems — API and OAuth, mail, calendar, CRM and accounting, payments, files, MCP servers, notifications, webhooks. Packs add command-line tools and coding agents.
- Chat and recipes
- What Recued does on its own — its chat in the app, by email, Slack, or Telegram, and recipes run by hand, on a schedule, or when something happens. The same tools are offered to agents over MCP.
- Logs
- The audit story — every allowed, denied, blocked, and approved run, recorded before execution.
- Reception
- One public-ingress surface — booking and intake, file drop, quotes and sign-offs, approval link — not the whole product.
Recued's chat
A quick lookup is answered from your saved records, with no AI. A question that needs AI gets the personal details swapped out and the relevant facts brought along first. Replay Maya's questions in the demo.
See a business at work
Step through an illustrated replay of Recued flows across intake, bookings, payments, delivery, and governed automation. It uses simulated screens and synthetic data, and never contacts a server.