Introduction

Myrtille is an open source control tower for small technical teams (2 to 15 people). It plugs into what you already run, without touching your code, and draws one picture of your company:

• The town. Every environment is a district, every project a building, every service, automation, coding agent or MCP server a citizen. A citizen’s posture reflects its real state: idle, running, waiting, error, done, offline or unknown.
• The mail. Everything that waits for a human decision becomes a mail item: a Claude Code permission, a failed deployment, a preview ready, an unreachable server. Items are sorted by urgency and decided in one click, from a phone too.
• Actions. Redeploy, restart, cancel a deployment, approve or deny a permission, give a coding agent a mission. Every action is real, checked against your role, confirmed when destructive, and written to an append-only audit log.

What Myrtille never does

• It never writes a file into your repositories and ships no SDK to import: integration is configuration only.
• It never shows a secret, not even to an administrator, and never sends one to the browser or to a coding agent.
• It never acts on its own: actions are disabled everywhere until an administrator enables them, district by district, and a webhook never triggers an action.
• It never lies: when the town hall loses contact with a source, citizens turn grey with the time of the last news.
• It is never the only barrier for coding agents: Claude Code’s own permission rules and sandbox stay active.

Integration levels

Level	Principle	Sources
0	Configuration only	Coolify webhooks and API, Claude Code hooks at user level, Git webhooks, Docker agent
1	One environment variable	OpenTelemetry zero-code instrumentation
2	Opt-in, no SDK	One structured log line, for example {"myrtille":"progress","done":42,"total":120}

Level 0 alone produces a living town.

Try the demo

The demo town Quillmoor runs without connecting anything, on a scripted scenario of three minutes: a deployment, a failure, a permission and a mission. With the command line and the town hall installed (npm install -g @myrtillehq/cli @myrtillehq/engine), myrtille dev --mock runs it on your machine and prints the demo account. Its sign-in page also lets you visit it without a password, to look around (Public view and visitors). The hosted demo, demo.myrtille.eu, is deployed during sprint 6. This site describes a pre-release.

The documentation

• Install: Self-hosting, Install with Coolify, Install with Docker Compose.
• Use: First steps, the setup, the mail and the actions per district.
• Connect: Coolify (tokens, webhook, polling), Dokploy (two keys without scope, webhook, polling) and Claude Code (the local agent, hooks, missions).
• Configure: the town plan and its reference.
• Trust: Security and Telemetry.
• Run what the cloud runs: Cloud features, self-hosted.
• Understand: Architecture and the event schema.
• Take part: Contributing and the FAQ.

Myrtille is pronounced “meer-TEE”: it is French for blueberry.