Skip to content
Mezzanine

Mezzanine

The mezzanine floor between raw servers and your apps. Adopt any VPS or bare-metal box, then deploy from git, scale into pools, load-balance, and manage DNS · Docker · SSL — all from one panel.
Install (self-host) Try it free (hosted) GitHub

Start in two minutes

Two ways to run the exact same product — pick one:

  1. Point a fresh Ubuntu VPS at this repo:
    Terminal window
    git clone https://github.com/mezzanine-cloud/mezzanine.git /opt/mezzanine
    cd /opt/mezzanine/deploy/docker
  2. Configure + launch:
    Terminal window
    cp .env.example .env && $EDITOR .env   # set DOMAIN + ACME_EMAIL
    docker compose --env-file .env up -d --build
  3. Open your domain, create the first admin, and adopt your first server. Full walkthrough: Installation.

What you get

One panel reaching many providers over SSH

Bring your own infrastructure

Hostinger, Contabo, DigitalOcean, Hetzner, Cloudflare — or any box reachable over SSH, including your office rack. No lock-in.

git pull → build → reload → healthcheck pipeline

One workflow, every stack

Templates for static · php · wordpress · react · nextjs · nodejs · django · flask · fastapi · docker. Same shape, swapped commands.

nginx load balancer fanning to pool members

Horizontal scaling built in

Group servers into Pools, deploy one workflow to each, and route through a built-in nginx LB (round-robin / least-conn / ip-hash).

GitHub or Gitea push → Mezzanine → deploy to server

Git, end to end

Connect GitHub or Gitea — repos, deploy keys, webhooks, and SSH keys without leaving the panel. CI/CD that never goes out of house.

owner / admin / moderator / viewer roles behind a gate

Multi-user from day one

owner / admin / moderator / viewer roles, route-enforced and UI-gated, with scrypt + HTTP-only sessions.

Self-host or Mezzanine Cloud — the same image

Self-host or let us run it

Identical image either way. Free + unlimited on your own box, or managed with backups, hibernation, and billing on Mezzanine Cloud.

Where Mezzanine sits

Where Mezzanine sits in your stack

Not IaaS, not a closed PaaS — the mezzanine floor in between. You keep the servers; Mezzanine gives them a control plane.

See how it works

System architecture The panel, containers, and SQLite volume — and how it reaches your fleet over SSH.
Deploy pipeline From git push to live: triggers → runner → typed steps → health-check → notify, with live logs.
Pools + load balancer Anatomy of a pool and how the built-in nginx LB routes traffic across members.
Two-server production topology Each server in depth, then clubbed: the panel box and the hosted-SaaS box behind one domain.

Start here

Installation Fresh VPS → working panel in ~45 minutes.
Self-host vs Hosted Which path fits you, and how the hosted platform is built.
Workflow templates The 5-stage skeleton + a 'which template?' map.
API reference Drive everything the panel does over REST.