From sign-in to a live site, then an ordinary week
There is no onboarding call and nothing to install. The first site takes a few minutes; after that the agents do the work and you make the decisions.
Four steps to a live site
Sign in
Enter your email and open the link, or use a passkey. Name your workspace. ManagEm creates your account on its private code host behind the scenes; you never see it.
Create a project
Pick a name, a slug and a starter: marketing site, blog, documentation or landing page. ManagEm generates the repository, creates the database, media storage and cache, and runs the first deploy.
Open the admin
Your site is live at slug.sites.managem.ai. The EmDash admin opens with your ManagEm account. Edit the starter content or ask the Editor to.
Add your domain
Point a CNAME at the managed host. The certificate is issued for you and the site answers on your domain. The admin stays on the managed host.
What the agents do while you are not looking
Sentinel checks
Pages answer, forms post, certificates are valid, content renders. A miss becomes an issue with a diagnosis.
Backup Warden backs up
Content, media and settings. Ninety days kept. The weekly rehearsal restores into a scratch copy and verifies it.
Maintainer opens a pull request
The update, the changelog in plain words, the preview built, the checks run. It waits for you.
Intake, Builder, Editor
"Add a careers page." Intake writes the issue, the Builder opens the pull request with a preview, the Editor fills the copy you asked for.
Responder proposes a fix
A diagnosis and a proposed change, or a rollback to the last good deploy, ready for your approval.
You approve
From the console, from an email link, from your phone. Each approval shows exactly what will happen, then does it and records it.
"Add a pricing page with three tiers"
Twenty minutes from the message to the approval, with nothing visible to your visitors until you click.
09:12 Intake: Issue #38 opened · priority P2 · assigned Builder.
09:14 Builder: Branch issue-38-pricing · page type, three cards, nav item.
09:27 Builder: Pull request #39 · preview acme--pr-39.sites.managem.ai · 12 checks passed.
09:28 Editor: Draft copy for the three tiers saved to the preview.
09:31 you: Approve and merge.
09:32 Deployed to acme.com · backup taken before deploy · issue #38 done.