Recued sits between an AI and your accounts. The AI can read useful things through Recued. It can do useful things through Recued. But the AI never gets your secret keys. And the cloud never becomes the owner of your data.
Local first. Your server runs everything. It is in charge of who you are. It keeps the diary of what happened. It is the only part of Recued that talks to your accounts.
#Start here
- Set up Recued and pair your first device.
- See how the four parts of Recued fit together.
- See what stays on your server and what can leave.
- Learn why you browse recipes one by one, but install packs as one box.
#What the documentation covers
| Area | What you will find |
|---|---|
| Setup | How to install, pair, get reached from outside, update, back up, and set up AI |
| Concepts | Safety, privacy, who you are, grants, approvals, the audit diary, and what stays local |
| Guides | Connections, recipes, packs, writing your own, publishing, and selling access |
| Reference | The exact fields for recipes, ingredients, and packs, the transforms, and the glossary |
#Engineering reference
This site explains what the product does and supports. The deeper design papers and decision records live next to the source code. So do the notes for people who help build Recued.