Platform/Open standards · Docker · Traefik

One control plane for every layer

Notploy Platform is the common set of capabilities shared by Notploy Self and Notploy Cloud: deploying applications, managing servers and clusters, routing traffic, protecting secrets and operating everything through one API. Easy by default, transparent by design.

Capabilities by operational domain

The platform covers the full lifecycle of an application, from the first commit to day-two operations. Each domain stands on its own, but they are designed to work together.

Deploy

From a Git repository or a container image to a running application, with build pipelines, environment variables and repeatable deployments.

  • Application deployment with Nixpacks, Buildpacks or a Dockerfile
  • Native Docker Compose projects
  • Databases: PostgreSQL, MySQL, MariaDB, MongoDB, Redis
  • One-click templates for popular tools

Part of the same control plane as every other domain — no separate console, no separate credential store.

How the platform fits together

Notploy is infrastructure-first: the platform manages the machinery — servers, containers, routing, certificates, storage — while you keep ownership of it.

Your side

Git, CI and your teams

Push code, open pull requests, trigger builds — Notploy picks it up from there.

Notploy

The operational layer

A control plane (web UI, REST API and background workers) you install in one command.

Your side

Servers, Docker and providers

Docker hosts or Swarm clusters, DNS providers, object storage and registries you already own.

How the platform is built

The decisions behind the product, visible in every screen and every endpoint.

One control plane

Applications, databases, servers, domains and users are managed from a single interface — no stitching together five separate tools.

Everything is scriptable

The dashboard and the API expose the same operations, so anything you can click, you can automate in CI or with your own tooling.

Built on open standards

Docker, Compose, Traefik and OIDC — Notploy builds on technologies your team already knows instead of inventing proprietary abstractions.

One platform, two ways to run it

The capabilities are the same. What changes is who operates the control plane — you, or Notploy.

Notploy Self

You operate the platform

The open-source edition. You install it on infrastructure you own and keep full control over updates, data and network boundaries.

  • Apache-2.0 and free to self-host
  • Run on any Linux server with Docker
  • Keep data, secrets and backups inside your boundary
  • Extend it, script it and audit it

Notploy Cloud

Notploy operates it for you

The managed service operated by Notploy. The control plane is run and upgraded for you, with support and availability commitments.

  • Control plane hosted and monitored for you
  • Always on a supported release
  • Support with response commitments
  • Same platform capabilities as Self

Platform FAQs

How the shared platform relates to the two editions.