The platform you run yourself

Notploy Self is the free, Apache-2.0 licensed edition of Notploy. Install it on infrastructure you control — your servers, your VPS, your hosting provider — and deploy applications and databases without handing ownership of your stack to anyone.

your-server/dashboard
Notploy dashboard listing applications and their deployments

The full control plane, running on a machine you own.

Runs on infrastructure you choose

Notploy does not require a specific provider or data center. If it runs Linux and Docker, it can run Notploy.

Your own servers and VPS

Any Linux machine — from a small VPS to a rack of bare metal — can run Notploy. Docker is the only prerequisite.

Homelabs

Notploy runs comfortably on modest hardware, making it a natural fit for homelab and personal infrastructure.

Any hosting provider

No preferred cloud: use AWS, Hetzner, OVH, Scaleway or your regional provider. Nothing ties Notploy to one vendor.

Air-gapped environments

Deploy inside private networks, regulated environments or systems with no outbound access to a vendor cloud.

Control and sovereignty by default

Self-hosting is not only about where binaries run. It is about keeping decisions — data location, upgrade cadence, security boundaries — where they belong: with you.

Read the architecture docs
  • Sovereignty over your data

    Code, databases, logs and secrets never leave your infrastructure. You decide where data lives and who can reach it.

  • You choose when to upgrade

    Updates are applied on your schedule, not on a vendor's release cadence. Pin a version, test it, then roll forward.

  • Security under your control

    Firewall rules, SSH access, certificate authorities and backup destinations are all yours to configure and audit.

  • Backups you own

    Database and volume backups go to storage you choose — local disks, S3 buckets or your own backup system.

  • Open source, no lock-in

    Apache-2.0 licensed. Read the code, fork it, extend it, or migrate your workloads away — the exit door is always open.

  • Full API and CLI access

    Everything the dashboard does is available through the API, CLI and SDK, so your automation never hits a paywalled endpoint.

From a blank server to your first deployment

Notploy is designed to be operational in minutes, not in a sprint.

  1. Host

    Provision a server

    Any Linux VPS or machine you already own. Modest specs are enough.

  2. One command

    Run the installer

    One command sets up Docker and the Notploy stack on the host.

  3. Account

    Open the dashboard

    Create your admin account in the web UI and connect a server.

  4. Ship

    Deploy

    Connect a Git repository, add a domain, and ship your first application.

Notploy Self FAQs

The practical questions that come up before the first install.