Skip to content
PortDock

Self-hosted application platform

Deploy and operate applications on infrastructure you control

PortDock builds and runs applications, databases and services from Git or Docker on your own Linux servers or Kubernetes clusters — with automatic HTTPS, versioned releases, monitoring, security scanning and single sign-on in one platform.

  • Open source under the Apache License 2.0
  • No plans, seats or usage limits
  • On-premises, in any cloud or air-gapped
Screenshot of PortDock: Dashboard — projects, deployments and servers at a glance
Git sources, including GitHub and Azure DevOps
6
database engines with backups
8
one-click services, plus 350+ Coolify templates
31
images in the Docker catalog
127
security scanners on every deploy
3
limits on servers, apps or users
0

Why PortDock

One platform for building, releasing and running software

The capabilities of a hosted PaaS — including those usually reserved for enterprise plans — on servers your organization already operates.

Everything in one place

Git deployments, Docker Compose stacks, managed databases, one-click services, domains with automatic HTTPS, scheduled jobs, metrics, alerts and backups — on Docker servers or Kubernetes, from a single binary.

Roll back in seconds

Every production deployment is kept as a version. Drag an older one onto Live and it is back — no rebuild. A canary release rolls itself back if it does worse.

Monorepos done right

A frontend and a backend in one docker-compose.yml deploy together, each service with its own domain and its own variables.

Built for teams

Project roles, protected environments, deployment approvals, SSO, LDAP / Active Directory, two-factor authentication, scoped API tokens, an audit log and a compliance report.

Secure by default

Image vulnerabilities, static analysis of the code and a dynamic scan of the running app on every deploy, with reports and policies that block — and releases signed with Sigstore.

An AI assistant built in

It reads your logs, containers and deployments with your permissions, finds the cause and proposes the fix as an action you confirm — with any model on OpenRouter or a local server.

Modules

One interface for the whole lifecycle

From the first commit to incident response. Every screen shown is the product itself, running with a demo organization.

Push to deploy, from any Git

Connect GitHub, Azure DevOps, GitLab, Gitea, Bitbucket or any Git URL. PortDock detects the build pack, builds, checks the health and moves traffic only when the new version is ready.

  • Dockerfile, Nixpacks, Node.js, Bun, Python, Go, static sites, Docker Compose
  • Pull request previews with their own domain
  • Zero-downtime rollouts, or canary releases with automatic rollback
  • Scheduled jobs (cron), persistent storage, Git over SSH
Screenshot of PortDock: Push to deploy, from any Git

How it works

From an empty server to production in three steps

No YAML to learn and no cluster to run. If it runs in Docker, it runs on PortDock.

  1. 01

    Install PortDock

    One command on a Linux server. The installer adds Docker if it is missing and starts the dashboard — or sets up Kubernetes with HTTPS and a registry.

    sudo bash install.sh
  2. 02

    Connect your code

    Link GitHub or Azure DevOps from the settings, or paste any Git URL. The build pack is detected automatically.

    git push origin main
  3. 03

    Operate in production

    Every push is built, scanned and rolled out without downtime — with HTTPS, metrics, alerts and backups already on.

    v42 live · https://shop.acme.example

Integrations

Works with the tools you already use

Standard Docker and Docker Compose underneath — nothing proprietary to migrate away from.

Git

  • GitHub
  • GitHub Enterprise
  • Azure DevOps
  • GitLab
  • Gitea
  • Forgejo
  • Bitbucket
  • Git over SSH
  • Any Git URL

Databases

  • PostgreSQL
  • MySQL
  • MariaDB
  • SQL Server
  • MongoDB
  • Redis
  • Valkey
  • ClickHouse

Identity

  • Microsoft Entra ID
  • Okta
  • Google
  • Keycloak
  • Authentik
  • Active Directory
  • OpenLDAP
  • FreeIPA

Observability

  • Slack
  • Microsoft Teams
  • Discord
  • Telegram
  • Email (SMTP)
  • Signed webhooks
  • Prometheus
  • Grafana Loki
  • Elasticsearch
  • Splunk
  • OpenTelemetry
  • Syslog / SIEM

Security

  • Trivy
  • Semgrep
  • OWASP ZAP
  • Let's Encrypt
  • Sigstore
  • HashiCorp Vault
  • Azure Key Vault
  • AES-256-GCM
  • SARIF

Infrastructure

  • Docker
  • Docker Compose
  • Kubernetes
  • k3s
  • cert-manager
  • Traefik
  • Nixpacks
  • Terraform
  • Nexus
  • Artifactory
  • Harbor
  • Amazon S3
  • Cloudflare R2
  • MinIO

Tour

Product tour

Screens from PortDock with a demo organization. Select an image to view it at full size.

Screenshot of PortDock: Dashboard — projects, deployments and servers at a glance
Dashboard — projects, deployments and servers at a glance
Screenshot of PortDock: Topology — domains, resources, servers and containers, live
Topology — domains, resources, servers and containers, live
Screenshot of PortDock: Deployment — build log and security reports
Deployment — build log and security reports
Screenshot of PortDock: Environment — encrypted variables, build-time and runtime
Environment — encrypted variables, build-time and runtime
Screenshot of PortDock: Uptime — monitors, response times and incidents
Uptime — monitors, response times and incidents
Screenshot of PortDock: New resource — Git, Docker image, Compose, database or service
New resource — Git, Docker image, Compose, database or service
Screenshot of PortDock: Project — environments and every resource in them
Project — environments and every resource in them
Screenshot of PortDock: Audit log — who did what, with export
Audit log — who did what, with export

AI assistant

An operations assistant built into the interface

Ask why a deployment failed or which containers have problems: the assistant reads the evidence with your own permissions, explains the cause in PortDock terms and proposes the fix as an action you confirm.

  • Reads logs, containers, deployments and metrics — with your permissions
  • Proposes deploys, rollbacks, restarts and backups that run after you confirm
  • Knows the PortDock documentation, offline too
  • Any model on OpenRouter, or Ollama, vLLM and LiteLLM in your network

PortDock assistant

anthropic/claude-sonnet

Why did the last deployment of storefront fail?

I read the build log of deployment #41: it stopped at npm ci, because package-lock.json doesn't match package.json (react-dom 19.3.0 was added without updating the lock file).

Run npm install locally, commit package-lock.json and push — PortDock will deploy it automatically. Your live version keeps running meanwhile.

Ask about deployments, DNS, Docker…

Comparison

PortDock vs. a hosted PaaS

The convenience of Heroku, Vercel or Render — with the control and the cost of your own infrastructure.

Hosted PaaSPortDock
Where your apps and data liveThe provider's cloudYour servers, any provider or on-premises
CostPer app, per seat, per GBFree — you pay only for your servers
LimitsPlan limits on apps, builds, bandwidthNone
DatabasesPaid add-onsIncluded, with backups to your own S3
SSO, LDAP, audit logUsually enterprise plansIncluded
Security scansExtra productsTrivy, SAST and DAST included
KubernetesA separate, paid productOptional: your cluster, or k3s installed in one command
Vendor lock-inProvider-specific configurationStandard Docker and Docker Compose

If you know Coolify, Dokploy or CapRover, PortDock will feel familiar — and it imports your applications from Coolify, Heroku and Dokku. On top: versions and drag-and-drop rollback, canary releases, Kubernetes clusters, deployment approvals, SSO / LDAP, security scans and an AI assistant included.

Enterprise

The controls regulated organizations require

Identity, access and audit controls that banks, public institutions and large companies ask for — built in, documented and available in every installation.

Single sign-on

OpenID Connect with PKCE: Entra ID, Okta, Google, Keycloak, Authentik.

LDAP / Active Directory

LDAPS or StartTLS, nested groups, required and admin groups.

Two-factor authentication

TOTP with recovery codes and an organization-wide policy.

Approvals

Protected environments and the four-eyes principle for production.

Audit and compliance

Every action logged and streamed to your SIEM, and a compliance report for auditors.

Security gates

Deployments blocked on critical findings; releases signed with Sigstore and verified before every update.

Air-gapped friendly

Corporate proxy, Nexus mirrors, scanner images from your own registry.

Data sovereignty

Everything stays on your servers, backups go to your own S3, secrets can stay in Vault.

FAQ

Frequently asked questions

Is PortDock really free?

Yes. PortDock is open source under the Apache-2.0 license, with no plans, no license keys and no limits on servers, applications or users. You pay only for the servers you run it on.

What do I need to run it?

A Linux server (Ubuntu or Debian recommended) with ports 80 and 443 free for the HTTPS proxy. The installer adds Docker if it is missing; remote servers are connected over SSH. For Kubernetes, a fresh server and a DNS record of your domain are enough: the installer sets up the rest.

Does it work in a corporate network without internet?

Yes. PortDock supports an HTTP(S) proxy with NO_PROXY, a Docker Hub mirror on Nexus, Artifactory or Harbor, npm / PyPI / Go / Maven mirrors, a mirror of the Trivy database and scanner images from your own registry.

How does a rollback work?

Every successful production deployment is kept as a numbered version. Drag an older version onto Live, or press Roll back: the image is started again with the current variables, and the running version stops only when the old one is healthy.

Can I deploy Docker Compose projects and monorepos?

Yes. A docker-compose.yml deploys as one application, with a domain and variables per service. Watch paths let each application of a monorepo deploy only when its own folder changes.

Which security scans are included?

Trivy scans images for known vulnerabilities, Semgrep analyses the source right after the checkout (SAST), and OWASP ZAP scans the running application (DAST). Every scan has HTML, CSV and JSON reports plus the tool's own report, and a deployment can be blocked by policy.

Does PortDock use Kubernetes?

Only if you want it. By default PortDock uses Docker and Docker Compose with the Traefik proxy, simple to run and debug. A namespace of any Kubernetes cluster can also be a server, and on a fresh server one command installs k3s, HTTPS, a private registry and PortDock with a test and a prod environment. Databases, one-click services and Compose stacks stay on Docker servers.

Where is my data stored and how is it protected?

On your servers. PortDock keeps its state in SQLite with secrets encrypted with AES-256-GCM, SSH keys encrypted and host keys pinned; secrets can also be read from HashiCorp Vault or Azure Key Vault. Database backups can be uploaded to your own S3 storage.

How are updates installed?

From the interface, with one click. PortDock checks the signature of the new image, backs up its database and key, recreates itself with the new version and rolls back automatically if it doesn't start. Your applications keep running throughout. In Kubernetes as well: a job of the current version moves PortDock to the new one and restores the previous one if it does not start.

What if the PortDock server itself is lost?

PortDock backs up its own database and encryption key, encrypted, on a schedule — on the server and optionally in S3. On a new server, the first-run page restores the backup with every account, project, setting and connection.

Can AI agents work with PortDock?

Yes. The MCP server lets Claude Code, VS Code, Cursor and other agents list, deploy, roll back and read logs with an API token whose scope and projects you choose. Protected environments still need an approval, and every action is in the audit log.

Evaluate PortDock on your own infrastructure

Installation takes a few minutes on any Linux server. No licence key or registration is required.

Shell
$ git clone https://github.com/gavrilencu/PortDock.git portdock$ cd portdock$ sudo bash install.sh