Deploy anything to your own servers.

Nixploy turns any Docker host into a full deployment platform. Push from Git and get builds, TLS domains, databases with backups, and live monitoring — without the per-app cloud bill.

Install Nixploy

Runs anywhere Docker runs. Five databases, seven service types, 86 one-click templates.

Projects & environments

Staging and production, side by side.

Group services into projects, then split them across environments. Each environment carries its own variables, domains, and deployment history.

  • Per-environment variables and domains
  • Clone a service into another environment in one click
  • Tags, search, and per-org resource quotas

Deployments

Every deploy, recorded and reversible.

Builds stream their logs live. When something breaks, roll back to any previous deployment — the failed one never takes the running version down.

  • Live build and runtime logs over websockets
  • One-click rollback to any previous deploy
  • Preview deployments for every pull request

Monitoring

Metrics that match reality.

Container-level CPU, memory, network, and disk for every service. Remote servers report over SSH, so a multi-node Swarm shows up in one view.

  • 30-second samples, 48 hours of history
  • Remote nodes sampled over SSH
  • Threshold alerts through your notification channels

Templates

86 stacks you can deploy before lunch.

Supabase, Plausible, Ghost, Uptime Kuma, Ollama and 80 more. Deploy from the catalog and the compose file, env, and domains are yours from the start.

  • 86 templates across 15 categories
  • You own the compose file after deploy
  • No hidden images or locked configs

How a deploy goes out

git push is the whole workflow.

  1. 1

    Connect a repo

    GitHub, GitLab, Bitbucket, Gitea — or a plain Git URL. Pick the branch and the builder: Nixpacks, buildpacks, Dockerfile, static site, or a prebuilt image.

  2. 2

    Push

    The webhook fires and the build queues. Fork pull requests wait for your approval before anything runs on your host.

  3. 3

    Rollout

    Swarm updates the service with zero downtime and Traefik re-routes traffic. A failed deploy leaves the previous version untouched.

  4. 4

    Watch

    Logs and metrics stream into the panel immediately. Roll back from the same screen if you need to.

your terminal

$ git push origin main

→ webhook received · build #42 queued

→ nixpacks · detected node 22, pnpm workspace

→ image built in 38s · pushed to local registry

→ service web updated · 3/3 replicas healthy

→ https://app.example.com is live

Prefer a terminal for everything? @nixploy/cli covers the full API — and the MCP server lets your AI assistant deploy and inspect for you.

The rest of it

Everything a PaaS does, on hardware you already pay for.

  • Builds your way

    Nixpacks, buildpacks, Dockerfile, static sites, or a prebuilt image — chosen per app, not per platform.

  • Databases with real backups

    Postgres, MySQL, MariaDB, MongoDB, and Redis. Scheduled dumps to S3-compatible storage, restores from the panel — and a backup of Nixploy itself.

  • Compose, first-class

    Paste a compose file or point at a repo. Stack or plain compose mode, with isolated deployments for side-by-side copies of the same stack.

  • Domains & TLS

    Attach domains per service and Traefik issues Let's Encrypt certificates. Redirects and basic-auth rules live in the same tab.

  • Teams without drama

    Organizations with owner, admin, and member roles. Destructive actions check capabilities, land in the audit log, and can require 2FA org-wide.

  • Automate everything

    REST with OpenAPI on your own panel, @nixploy/cli for the terminal, and an MCP server so AI tools can deploy and inspect too.

Template catalog

86 one-click deploys, no lock-in after.

Supabase, Plausible, Ghost, Uptime Kuma, Ollama, Metabase and dozens more. Every template deploys as a plain compose service you can edit, version, and back up like anything else you run.

  • AI4
  • Analytics4
  • Apps7
  • CMS6
  • Communication2
  • Databases6
  • Finance3
  • Knowledge10
  • Media5
  • Monitoring7
  • Notifications4
  • Productivity10
  • Security6
  • Storage3
  • Tools9

Supabase · Plausible · Ghost · Uptime Kuma · Ollama · Metabase · n8n · MinIO · Vaultwarden · Umami

Browse the catalog

FAQ

Frequently asked questions

  • Yes. Apache-2.0, no hosted tier, no license key. The only thing you pay for is the server it runs on.

  • A Linux host with Docker and an active Swarm. One curl installs the panel, Traefik, and the config layout — you're deploying within minutes.

  • Yes. Add remote servers over SSH from Settings → Servers; they join the same Swarm and report metrics back to the same monitoring view.

  • Yes. Point DNS at your server, attach the domain to a service, and Traefik issues the Let's Encrypt certificate. Redirects and basic-auth rules are built in.

  • Connect GitHub, GitLab, Bitbucket, or Gitea — or paste any Git URL. Pick a branch and a builder (Nixpacks, buildpacks, Dockerfile), and every push triggers a deploy.

  • The whole panel is an API: REST with OpenAPI docs on your own instance, the @nixploy/cli for terminals, and an MCP server so AI assistants can operate it too.

Your next deploy could be on your own hardware.

Bring a Docker host. One curl later you have the panel, the Traefik edge, and a platform you actually own.

Install now