Agents with narrow keys. People with the only one that matters.
ManagEm is built so that an agent can never do more than its job, a mistake can always be undone, and every action can be read afterwards.
Each site in its own compartment
Every site runs as its own Worker with its own database, media bucket and cache on Cloudflare's network. Sites cannot reach each other's data.
One gateway for every agent
Agents never hold a site's credentials. They call ManagEm's gateway, which holds a per-site, per-role credential behind Cloudflare Access and enforces what that role may do.
Production changes are human actions
Publishing, merging, deploying, restoring and changing domains or credentials require a person in your workspace. An approval link is single-use and shows exactly what will happen.
Daily, ninety days, rehearsed weekly
Database and media are backed up every day and kept for ninety days. A restore is rehearsed every week into a scratch copy and verified, and a real restore to any point is one approval away.
Every action, readable
The gateway logs each agent call with the role, the site, the tool and the outcome. Code changes are a git history you can read in the console. Approvals record who clicked and when.
No passwords to lose
Email links and passkeys for ManagEm; the EmDash admin signs you in with the same account. Sessions can be reviewed and ended from your profile.
Encrypted at rest, scoped in use
Credentials are sealed with per-workspace keys. Agents receive secrets only through the runtime's vault, limited to the hosts they are for, never in prompts or logs.
Cloudflare, end to end
TLS everywhere, certificates issued and renewed automatically for your domains, DDoS protection and the edge network included with every site.
Yours to take
Every project is a plain EmDash repository. Download an archive from the console at any time; nothing in it depends on ManagEm to run.
What people ask before they trust us
Can an agent publish or deploy on its own?
No. Agents can draft, build and propose. Publishing content, merging code, deploying to production, restoring backups and changing domains or credentials all require an approval from a person in your workspace.
What can an agent see?
Only what its role needs, through the gateway: the Editor sees content, the Builder sees code, the Sentinel sees responses. None of them sees your ManagEm credentials, your sessions or other workspaces.
Where is my data?
On Cloudflare's network, in resources that belong to your site alone: a D1 database, an R2 bucket for media, a KV cache. Backups are stored separately and kept for ninety days.
Can I leave?
Yes. Download the repository archive and the latest backup from the console. The site is a standard EmDash project and runs anywhere EmDash runs.
Which model powers the agents?
Claude, through Anthropic's managed agent runtime, with each agent's tools and credentials scoped to its role. ManagEm never trains anything on your content.