Recued holds the boundary between AI and your accounts. It gives an AI useful context and actions without handing the AI your credentials or making the cloud the owner of your data.
Local first. Your server is the orchestrator, identity root, audit authority, and the only Recued component that connects directly to your accounts.
#Start here
- Set up Recued and pair your first client.
- Understand how the four Recued surfaces fit together.
- Review what stays local and what can leave.
- Learn why recipes are browsed individually while packs are installed as a unit.
#What the documentation covers
| Area | What you will find |
|---|---|
| Setup | Installation, pairing, reachability, updates, backup, and AI setup |
| Concepts | Security, privacy, identity, grants, approvals, audit, and local-first boundaries |
| Guides | Connections, recipes, packs, authoring, publishing, and selling access |
| Reference | Recipe, ingredient, and pack manifests, transforms, and the glossary |
#Engineering reference
This site explains supported product behavior. Architecture specifications, decision records, and contribution material are maintained alongside the source tree.