Fully managed

Mana is fully managed. You do not need to assemble model providers, API keys, local endpoints, frontend builds, deploy scripts, or hosting infrastructure before the system is useful.

The intended user flow is browser-only:

1. Sign in with GitHub.
2. Connect a repository through the Mana GitHub App.
3. Choose the repo you want Mana to maintain.
4. Submit sources, notes, selections, or edit requests from the app.
5. Let Mana run the agent, commit the Markdown, build the site, and publish it.

No user-side model plumbing

Mana owns the service-side model and agent setup. The user-facing product is the work done to the repository, not a screen full of provider keys and model switches.

That means you can start from a browser and a GitHub repo. Mana handles the agent runtime and the model access needed to do the work.

Builds and deploys are handled by Mana

After an agent edit, Mana rebuilds the published site from the committed Markdown. The build runs in Mana’s sandbox and uses Mana’s renderer. The app worker then publishes the build artifact and swaps the active deployment slot.

You do not need to run Astro, Wrangler, R2 uploads, cache hydration, or deployment commands yourself. Those are part of the managed pipeline.

The repo is still yours

Managed does not mean proprietary. Mana runs the infrastructure, but the durable output is still your Markdown repository. The managed service exists to do the boring operational work around the repo: run the agent, build the frontend, publish the site, and keep the browser experience usable.

For now, the simplest way to use Mana is from the browser. The browser is the control surface; the repo is the durable record.