Skip to content

Capabilities

What Notploy does today

Grouped by the job each capability does. For the authoritative status — including what is in development, planned or out of scope — the documentation feature matrix and limitations pages are the reference.

Feature matrixLimitationsPlatform overview

Capabilities by domain

Each domain is documented independently, so a limitation in one does not silently disappear behind a general claim.

Workloads

  • Applications built from GitHub, GitLab, Gitea or Bitbucket
  • Images pulled from public or private container registries
  • Docker Compose projects managed as one stack
  • PostgreSQL, MySQL, MariaDB, MongoDB and Redis
  • Scheduled jobs and one-off commands

Infrastructure

  • The local server Notploy is installed on
  • Remote Linux servers added over SSH
  • Docker Swarm clusters across nodes
  • Volumes and bind mounts
  • Build servers and registry credentials

Operations

  • Deployment history, logs and rollback
  • Container and deployment logs
  • CPU, memory and network metrics
  • Database and volume backups to S3-compatible storage
  • Health checks and maintenance commands

Networking

  • Custom domains per service
  • Traefik routing and internal networks
  • Automatic TLS certificates and renewal
  • DNS provider integrations

Access & governance

  • Organisations, projects and environments
  • Roles and permissions per resource
  • API keys and SSH keys
  • Single sign-on and SCIM provisioning where available
  • Audit logs and white labeling on the commercial offer

Automation & integrations

  • REST API, CLI and TypeScript SDK
  • Webhooks and CI/CD triggers
  • MCP server for agent-driven operations
  • Git provider, identity provider and DNS adapters

This page deliberately carries no status badges. Statuses change with every release, so they live in the documentation rather than in marketing copy that ages badly. Open the feature matrix

Capability questions

How to read this page without over-claiming.

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.