Ployz

Ployz is built by Nick Potts and turns Linux servers you rent into a deployment platform with Git push deploys, per-pull-request preview environments, one-click databases and automatic https. It is offered through the Ployz Cloud dashboard and a CLI, and the site labels it Beta. The engine is Apache-2.0 and the dashboard is AGPL-3.0.

What It Is

Ployz is a self-hosted PaaS for people who want a hosted-platform workflow on servers from providers such as Hetzner, OVH or Netcup. You push to GitHub and the server builds the app, using Railpack so no Dockerfile is needed for common languages, or your own Dockerfile or any registry image. Services, databases, variables and domains sit on one dashboard canvas, and edits stay staged until a single Deploy ships them.

How Servers and Environments Work

Each server joins with one command and runs a small Ployz daemon next to Docker. Servers share an encrypted WireGuard private network, serve https themselves through Caddy, and a service can run up to 50 replicas across them. Every pull request can get its own https environment, optionally with a copied database, and staging environments can save changes back to production. Postgres, MySQL, Redis and MongoDB are available with restore points, plus logs, metrics and uptime checks.

Working With Coding Agents

The CLI prints JSON with --json, and the project exposes 55 tools through an MCP server so agents such as Claude Code, Codex or Cursor can add servers, deploy and configure services. Changes that would delete a service, volume or domain require approval from a person, and agents cannot approve them.

Current Status

The README says Ployz is young and changes quickly. Documented gaps include no OS update management, no offsite backups yet, no automatic failover, no Docker Compose file support, and email-only alerts. Apps keep running on your servers if Ployz Cloud is unavailable.