Trust & principles

What we stand for. And what we do not claim.

Notploy is built around ownership, open technology and European development. This page states those commitments precisely, including their limits.

Commitments

Each statement describes what Notploy does, not what a deployment automatically guarantees.

European development: Notploy is developed by a European team. That describes where the work happens and who is accountable for it. It does not mean that every dependency, provider or deployment you configure stays in Europe — that depends on the infrastructure and services you choose.
Self-hosting first: The default way to run Notploy is on infrastructure you control. Notploy Self does not require a Notploy-hosted service to operate, and the platform can run without outbound access to a vendor cloud.
Open source: The platform source is published under Apache-2.0. You can read it, audit it, modify it and redistribute it. Issues and release notes are public.
Transparent dependencies: Notploy builds on Docker, Docker Compose, Docker Swarm and Traefik. Those are technologies you can inspect, replace or migrate away from, rather than a proprietary runtime only we understand.
Your data stays yours: With Self, code, databases, secrets and backups remain on infrastructure you own. With Cloud, your workloads run on the servers you connect; what the managed service operates is the control plane, and the documentation describes the split.
Verifiable statements: Capability claims are traced to the documentation or the product. Where something is in development or depends on your setup, we say so instead of turning it into a badge.

Labels are easy to print and hard to defend. These are deliberately absent from our copy.

We do not claim to be "fully sovereign": sovereignty depends on your hosting, providers and legal arrangements, not on a product label.
We do not claim blanket "GDPR compliance". Notploy Self gives you the deployment model and controls; your obligations remain yours.
We do not claim "100% European infrastructure". The platform runs wherever you install it, and Cloud relies on infrastructure that the documentation describes.
We do not claim automatic high availability. Multi-node distributes workloads; redundancy is an architectural decision.
We do not claim that every workload, runtime or enterprise requirement is supported. The limitations page lists what is not.

Where a claim depends on your infrastructure or your legal obligations, the documentation is the place to check it. See the capability domains.

The points that come up before a purchase or a security review.

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