Get started with Recued

Run your own Recued server, pair a client, and install a foundation pack. Your data and your accounts' credentials stay on machines you control; every action an AI takes is granted in advance, audited, and reversible.

Why Recued

Your data stays local

AI reads and acts on your world through Recued. Your accounts' credentials and your data live on your own server — the cloud never decrypts them.

One audited boundary

Every action passes through a single enforcement point: granted in advance, logged, and reversible. Nothing runs that you didn't allow.

Any AI, over MCP

Connect Claude, GPT, or a local model over MCP. Recued is the layer between you and whichever AI you choose.

Free and self-hosted

The whole engine runs on your server at no cost. AI resolves through free-pool keys or your own BYOK — Recued bears no inference bill. Pro ($5.99 USD/month) only adds public reachability — a recued.net address and an auto-renewing certificate — and both have a free do-it-yourself path.

Built to reach anything

Recued is a substrate, not a fixed feature list — it reaches whatever you wire into it, and every connection runs through the same audited boundary.

Connect to any API or service

Reach any HTTP API, plus your mail, calendar, files, and CRM through the connection layer. Credentials are entered once on your server and never leave it.

Wrap any command-line tool

Turn a CLI — ffmpeg, pandoc, OCR, PDF tools — into a server-side step your recipes and AI can call. The tool runs on your machine, never in the cloud.

Your world as one warehouse

Mail, calendar, files, contacts, CRM, and a memory graph in one local store the AI reads through Recued — with provenance and a timeline behind every fact.

Reversible PII aliases

AI works over aliased stand-ins; the real emails, names, and URLs are restored locally on the way back, so the model never sees them.

Public reception, review-first

Accept inbound requests — webhooks, a public endpoint — into a review-then-approve inbox. Nothing acts until you approve it, with the arguments in front of you.

Scheduled and reactive

Run recipes on a schedule, on a trigger — a new email, a CRM change — or as idle-time housekeeping. All on your server, no cloud cron.

Install your server

One command. It fetches the signed binary for your platform, verifies it, and leaves you with a running Recued server.

Linux and macOS

curl -fsSL https://recued.com/install.sh | sh

Windows

Open PowerShell first: press Start, type PowerShell, and open it. Then paste:

irm https://recued.com/install.ps1 | iex

Then start it with recued. The script fetches the binary for your platform, verifies its signature against the release key, puts it on your PATH, and sets it to start when you log in.

Options

Set any of these before the command — RECUED_AUTOSTART=0 curl -fsSL https://recued.com/install.sh | sh. In PowerShell, run $env:RECUED_AUTOSTART=0 on its own line first.

RECUED_AUTOSTART=0 — don't start at login. It is on by default: without it the server stops when you close the terminal that started it, and an update cannot restart it for you.
RECUED_PREFIX / RECUED_BINDIR — where the payload and the recued command are placed. Default to /usr/local/lib/recued and /usr/local/bin; set both to install without sudo.
RECUED_CHANNEL=edge — follow the edge channel instead of stable.
RECUED_FORCE=1 — reinstall even when you are already on the released version.

Starting at login gives you a supervised server, not necessarily an unattended one: if you seal your keyfile with a passphrase it starts locked and waits for recued unlock. Sealed to the machine instead, it starts ready.

macOS, Windows and a Linux desktop all arm this per-user, no root needed. Headless Linux needs root — run the installer with sudo for a boot unit. Without a desktop keyring the only way to seal the keyfile to the machine reads a host key only root can read, so a non-root headless install arms nothing rather than writing a unit that would fail on every boot.

Linux and Windows on x64 or arm64. macOS on Apple Silicon and Intel — both signed and notarized with a Developer ID.

Then pair a client

Open the webclient at app.recued.com and pair it to your new server with the code it shows on first boot. The webclient is display and input only — your server runs the work.

Start with a foundation pack

Foundation packs bootstrap your warehouse with useful recipes from day one. Install one, then browse the rest.

Browse all packs

Read the docs Browse recipes See pricing