Skip to content

European application infrastructure

Your services. Your infrastructure. Your control.

Notploy provides the tools to deploy, operate and control the services you depend on — from a personal server or homelab to a growing multi-node infrastructure. Run it yourself with Notploy Self, or choose Notploy Cloud for a managed experience.

Install Notploy SelfExplore Notploy Cloud
Read the documentationView the sourceNotploy for teams
curl -sSL https://notploy.com/install.sh | sh

Any Linux server, VPS or homelab host with Docker. Installation guide

Capabilities

Deploy, operate, observe, control

What the platform covers today, grouped by the job it does. Feature availability depends on the edition and the integrations you use.

Workloads

Applications from Git or Docker images, Docker Compose stacks, databases and scheduled jobs.

Infrastructure

One server or several, remote hosts over SSH, Docker Swarm clusters, volumes and registries.

Operations

Deployment history and rollback, logs, metrics, backups and restore workflows.

Networking

Domains, Traefik routing, TLS certificates and internal service networks.

Access

Organisations, roles, API keys, single sign-on and audit logs where available.

Automation

REST API, CLI, SDK, webhooks, MCP and CI integration for everything you do in the dashboard.

Explore the platformSee what is available today

How it fits together

From your infrastructure to running services

Notploy sits between the machines you control and the services you depend on. Nothing else in the stack is owned by us.

  1. 01

    Infrastructure

    A Linux server, a homelab machine, a VPS or a Docker Swarm cluster — the machines you already run.

  2. 02

    Platform

    Notploy installs on that infrastructure and becomes the control plane: deployments, routing, certificates, secrets, backups and monitoring.

  3. 03

    Services

    Applications from Git or Docker, Compose stacks, databases and scheduled jobs — running where you decided they should run.

Explore the platformSingle server today, more nodes when you need them.

Who it is for

One platform, three starting points

The same product, approached from a homelab, a development team or an organisation with governance requirements.

Ways to run it

Same platform, two operating models

Choose who operates the control plane. Your workloads stay on the servers you connect either way.

Notploy Self

You operate the platform

Install Notploy on the servers you control. You decide the upgrades, the network boundaries, the backups and who has access.

  • Free and open source (Apache-2.0)
  • Runs on any Linux server with Docker
  • Data, secrets and backups stay in your boundary
  • Start on one server, add nodes when you need them
Install Notploy

Notploy Cloud

Notploy operates the platform

The control plane is hosted, monitored and upgraded by Notploy. Your workloads stay on the servers you connect.

  • Nothing to install to get started
  • Upgrades and monitoring handled for you
  • Your applications and data stay yours
  • Same product as Self, different operating model
Explore Notploy Cloud

The choice is about who operates the platform, not which features you get. Compare Self and Cloud.

Architecture

One server to start. More when you need them.

The same control plane works on a single machine or across several nodes. What changes is how many hosts you connect and how you choose to distribute workloads.

Single nodeStart here

One Docker host

Notploy control plane
Traefik · TLS
Application
Database
  • Infrastructure, platform and services on one machine.
  • Remote servers can be added later over SSH.
Multi-nodeWhen you grow
Notploy control plane

Docker Swarm cluster

Node 1workloads
Node 2workloads
Node 3workloads
  • Remote servers joined to the same control plane.
  • Workloads scheduled across nodes by Swarm.

Multi-node distributes workloads across servers; it is not an automatic high-availability or disaster-recovery setup. Redundancy depends on how you design and operate the infrastructure around it.

Principles

What we commit to — and what we do not claim

Notploy is built around ownership and open technology. Where a statement depends on your setup or on the law, we say so instead of replacing it with a label.

Self-hosting first
The default is software you install and keep. Notploy Cloud is an option, not a requirement.
Open source
Apache-2.0. The source, the issues and the release notes are public.
Control stays with you
Data, backups, network boundaries and upgrade timing are your decisions.
Transparent dependencies
Docker, Compose, Traefik and Swarm — standard tools you can inspect, replace and take with you.
European development
Notploy is developed by a European team. We say what that means, and what it does not guarantee, instead of trading on the label.
Verifiable statements
Claimed capabilities are traced to the documentation or the product. What is still being built is labelled as such.
Read the project philosophy

Built in the open

You can verify what you are running

Notploy is developed publicly and licensed for self-hosting. Source, releases and support channels are outside this marketing site.

  • Apache-2.0

    The licence covers the platform source. Read it, audit it, modify it and redistribute it.

    View the repository

  • Public development

    Issues, pull requests and release notes are tracked in the open on GitHub.

    Release notes

  • Community

    Questions, setups and trade-offs are discussed in Discussions and on Discord.

    Join the discussions

  • Service status

    Availability of the hosted services is published independently of this site.

    Open the status page

Questions before the first install

The practical points that decide between Self and Cloud — and what Notploy does not do for you.

Start with the infrastructure you already have.

Install Notploy Self on a server you control, or let Notploy operate the control plane with Cloud. Both paths lead to the same platform.