Running Recued requires no account: the server, clients, marketplace browsing, and installing all work without one. An account adds the public bits — a free publisher handle for the marketplace and, optionally, the Pro conveniences — and the dashboard is where you manage them.
#What an account is for
- Publishing. A free account reserves your publisher handle — namespace ownership, not payment — and everything you publish appears under it.
- Recued Pro. The optional $5.99 USD/mo convenience bundle (a
<handle>.recued.netname plus an automatically renewed certificate) attaches to your account, where you manage the subscription.
#The dashboard
The dashboard at dashboard.recued.com is the one signed-in cloud surface.
It shows your publisher handle and published inventory — recipes,
ingredients, versions, submissions and their review state, install and rating
stats — plus your plan and server-binding status, and it is where you manage
billing.
It summarizes and routes; it does not author. Editing a recipe from the dashboard opens the Kitchen on your own setup — recipe content is never edited in the cloud.
#Binding your server
Pro conveniences apply to a server, so the account and the server link through a deliberate binding step: your webclient hands the server a narrow, single-purpose binding token, and the server presents it to attach itself to the account. The order doesn't matter — subscribe first or bind first — and binding can be revoked and redone when you move servers.
#What the account cannot do
The account holds no warehouse data, no credentials, and no control channel: it cannot read your server's data, run recipes, or reach into your machine. Publishing is the only thing that makes content public — and that is content you chose to publish.
#Related
- Reachability — what the Pro name and certificate actually do.
- Recipes and packs — how published content is browsed and installed.