Ployz docs
Ployz turns your Linux servers into a deployment platform: Git push deploys, preview environments, databases and https, on servers you own. These docs cover the dashboard at ployz.dev.
Start here
Section titled “Start here”New to Ployz? Follow these steps from a first deploy to real users.
- Deploy an example app: Quick start
- Deploy your own app: Deploy from GitHub
- Configure it: Variables and Databases
- Test changes: Preview environments
- Get ready for production: Production checklist
Getting started
Section titled “Getting started”- Introduction: whether Ployz fits, what you need, what it costs
- Quick start: an example app on your server at an https address
- The basics: how your app is organized and how a change ships
Deploy
Section titled “Deploy”- Deploy from GitHub: connect GitHub, deploy on push, wait for CI, monorepos
- Deploy a Docker image: public and private registries
- Deployments: staged changes, Deploy, following a deployment, confirming data loss
- History and rollback: saved versions, undo, roll back, redeploy or cancel
- Deploy without downtime: health checks, update order, servers cut off mid-deploy
Services
Section titled “Services”- Services: add, rename, restart or delete a service
- Service settings: what each field does
- Variables: variables, secrets, references between services
- Databases: PostgreSQL, MySQL, Redis and MongoDB, connecting, backups
- Volumes: files that survive deploys
- Configs: shared text files mounted read-only into services
- Mirror a volume: keep a read-only copy of a volume on a second server
- Move a volume: move a volume and its service to another server
- Restore a volume: bring a volume back to an earlier point, or restore it in place
- Domains: generated addresses, custom domains, https
- Cloudflare Tunnel: serve your apps through a tunnel instead of open ports
- Private networking: how services reach each other
- Scaling and multiple servers: replicas, more servers, when a server goes down
Environments
Section titled “Environments”- Environments and branches: production, staging and branches of them
- Preview environments: a copy of your app for every pull request
Builds
Section titled “Builds”- How builds work: what triggers a build, when one is reused, build logs
- Railpack and Dockerfiles: building without a Dockerfile, build commands
- Where builds run: your servers or GitHub Actions, and in what order
- Build resources and cache: limit what builds use, clear the cache
Servers
Section titled “Servers”- Add a server: requirements, the install command, the ports to open
- Add many servers: one Fleet Token for several servers, reviewed before they join
- Manage servers: status, upgrades, removing a server
- Upgrade to Ployz 0.4: upgrade, then turn device enforcement on once, and what that can't undo
- Recovery code: get the code that opens your sealed values after you lose every server, and recover with it
Observe
Section titled “Observe”- Logs: service logs and deployment logs
- Metrics: CPU, memory, network and disk per service and server
- Uptime: whether visitors can reach each service, checks after each deploy and on demand. Part of Production
- Analytics: visitors, pages, sources and goals per Environment, without cookies. Part of Production
Account
Section titled “Account”- Your account: your profile, where you're signed in, signing a browser out
- Organizations and billing: your organization, deleting it, billing
- Permissions: roles, tokens, Protected environments and approvals in one place
- Try Ployz without an account: let an agent start in a sandbox, then claim it
- Notifications: choose which emails you get, and unsubscribe from one
- Production checklist: before you move real users
- The Ployz agent: ask the dashboard's agent to look around or deploy, and approve each deploy
- Connect an agent to Ployz Cloud: add Ployz to Claude, Codex or another MCP app with a link
- CLI and coding agents: install the CLI, set up your coding agent, MCP tools, tokens for CI
- Self-host Ployz Cloud: run the dashboard on your own infrastructure
Troubleshooting
Section titled “Troubleshooting”- Builds: detection failures, out of memory, stuck builds
- Deployments: failed health checks, crashing services, queued deployments
- My app isn't reachable: error pages, wrong ports, domains and certificates
- Trace a request: which server answered, its deploy and replicas, Cloudflare
- Servers: install failures, servers that don't join or go offline, full disks
- Volumes: moves that stop partway, busy volumes, a server lost mid-move