Skip to main content
Mangrove turns one Linux box into a small platform for your apps. Point it at a Git repository, a Dockerfile, a compose file or a pre-built image, and it builds it, runs it, checks it’s healthy, and puts it behind a reverse proxy. Push to GitHub and it redeploys itself. These docs are task-first: each page says what something does, how to use it, and what to do when it breaks.

​
Get started

What is Mangrove

What you get, what it isn’t, and how it fits together.

Install

One command on Debian or Ubuntu, or build it yourself.

First deploy

A GitHub repo, deployed and redeploying on every push.

Concepts

Workspaces, projects, deployments, services and runs.

​
Deploy and run

From GitHub

Auto-deploy, commit statuses and webhooks.

Builds

Dockerfile, nixpacks, compose, image or static.

Domains and HTTPS

Custom domains, automatic certificates, DDNS.

Environments

Variables, staging, promote and PR previews.

Templates

WordPress, Supabase, Gitea and more in one click.

Rollbacks

Go back to any successful run.

​
Operate

Going to production

The checklist for a box people rely on.

Configuration

Every environment variable.

Troubleshooting

Start with the symptom.

​
Other ways in

CLI and TUI

mangrovectl and the full-screen mangrove-tui.

HTTP API

Everything the dashboard does, as JSON.

MCP for agents

Let Claude operate your deployments.

​
Internals

The Internals group holds the longer, design-level documents: why each subsystem works the way it does. For where everything lives in the code, see REPO_MAP.md on GitHub, and for the dashboard’s visual language, DESIGN.md.