# Ployz

> Turn Claude Code, Codex or Cursor into the platform engineer for the servers you rent: deploys, databases, previews and monitoring. You approve the deletes.

Every page below is Markdown. The homepage, /contact and every docs or blog URL also return Markdown when the request sends `Accept: text/markdown`.

## When to use Ployz

- Good fit: self-hosting apps, databases and preview environments on rented VPSes.
- Good fit: leaving Heroku, Railway or Coolify to pay less.
- Poor fit: serverless or edge functions, managed Kubernetes, or Windows servers.
- Call Ployz through the `ployz` CLI first. Use the MCP server when you have no shell.

## Pricing

Ployz Cloud, the hosted dashboard and control plane at ployz.dev, has a Free plan for one server you rent: unlimited projects, deploys and members, with git push deploys, preview environments, one-click databases, custom domains with https, monitoring, searchable logs, uptime checks, email alerts, a restore point for every database and an agent in the dashboard included. Your hosting provider bills you for the server.

Pro is coming at $19 a month with 3 servers included and $5 for each extra server. It adds backups kept off your servers and test-restored every week, protected environments, longer history and email support. Scale, from $999 a month billed yearly, adds SSO, an audit log, a commercial license, onboarding and a named engineer.

Compared with Coolify Cloud, which costs $5 a month for 2 servers plus $3 for each extra server, Ployz Cloud's Free plan costs nothing for one server. Self-hosted Coolify is free too, but you run and update its dashboard yourself, on a server with at least 2 CPU cores and 2 GB of RAM.

## For agents

- [Set up Ployz and deploy](https://ployz.dev/agents.md): install the `ployz` CLI and the Ployz skill, sign the user in, add a server and deploy their app
- [The Ployz skill](https://ployz.dev/.well-known/agent-skills/ployz/SKILL.md): how a coding agent uses the `ployz` CLI
- [Ployz MCP server](https://ployz.dev/docs/account/connect-an-agent.md): the Ployz tools at `https://ployz.dev/mcp`, for an agent app with no shell. It signs in with OAuth.

## Docs

- [Ployz docs](https://ployz.dev/docs.md): How to deploy apps to your own Linux servers with Ployz: Git push deploys, preview environments, databases and https.
- [Your account](https://ployz.dev/docs/account/account.md): Your profile, where you're signed in, and which emails you get.
- [The Ployz agent](https://ployz.dev/docs/account/agent-sidebar.md): Ask the agent in the dashboard about your app, have it deploy for you, and approve each deploy.
- [Connect an agent to Ployz Cloud](https://ployz.dev/docs/account/connect-an-agent.md): Give Claude, Codex or another MCP app the Ployz tools with a link, no CLI or token to install.
- [Notifications](https://ployz.dev/docs/account/notifications.md): Choose which emails Ployz Cloud sends you, and turn one off from the email itself.
- [Organizations and billing](https://ployz.dev/docs/account/organizations.md): Your organization, its settings, deleting it, and what Pro costs.
- [Permissions](https://ployz.dev/docs/account/permissions.md): Who can do what in Ployz. Roles, tokens, Protected environments and approvals in one place.
- [Try Ployz without an account](https://ployz.dev/docs/account/try-without-an-account.md): An agent gets its own organization with one call, deploys to your server, and hands you a link to keep it.
- [Build resources and cache](https://ployz.dev/docs/builds/build-resources-and-cache.md): Limit the CPU, memory and disk builds use on a server, give builds more time, and free up disk space.
- [How builds work](https://ployz.dev/docs/builds/overview.md): When Ployz builds your app, what triggers a rebuild, and how to read a build log.
- [Railpack and Dockerfiles](https://ployz.dev/docs/builds/railpack-and-dockerfiles.md): Build your app without a Dockerfile, or with yours, and set commands, build-time variables and CPU types.
- [Where builds run](https://ployz.dev/docs/builds/where-builds-run.md): Build on your own servers or on GitHub Actions, and choose which one goes first.
- [CLI and coding agents](https://ployz.dev/docs/cli/overview.md): Install the ployz CLI, set up your coding agent, deploy a directory and use tokens in CI.
- [Deployments](https://ployz.dev/docs/deploy/deployments.md): Stage changes, deploy them, follow each deployment, and know what happens when one fails.
- [Deploy a Docker image](https://ployz.dev/docs/deploy/docker-image.md): Run any image from Docker Hub, GitHub Container Registry or another registry, public or private.
- [Deploy from GitHub](https://ployz.dev/docs/deploy/github.md): Connect a repository, deploy on every push, wait for CI, and deploy only what changed.
- [Environments and branches](https://ployz.dev/docs/environments/environments.md): Run staging next to production with its own data, and sync what works back to production.
- [Preview environments](https://ployz.dev/docs/environments/preview-environments.md): Give every pull request a temporary copy of your app at its own https address.
- [Introduction](https://ployz.dev/docs/getting-started/introduction.md): What Ployz gives you, who it's for, what you need, what it costs and what you own.
- [Quick start](https://ployz.dev/docs/getting-started/quick-start.md): Deploy an example app to your own server and open it at an https address.
- [The basics](https://ployz.dev/docs/getting-started/the-basics.md): How your app is organized in Ployz, and how a change reaches your servers.
- [Analytics](https://ployz.dev/docs/observe/analytics.md): Count visitors, pages, sources and goals, and read each route's speed and failures, for each Environment, without cookies or a script.
- [Logs](https://ployz.dev/docs/observe/logs.md): Read what your services print, live, and the build and deploy logs of each deployment.
- [Metrics](https://ployz.dev/docs/observe/metrics.md): See how much CPU, memory, network and disk each service and server uses.
- [Uptime](https://ployz.dev/docs/observe/uptime.md): See whether visitors can reach each service, check it after a deploy, and read its incidents.
- [Production checklist](https://ployz.dev/docs/production-checklist.md): What to set up before you move real users to your app, and what Ployz doesn't do for you yet.
- [Self-host Ployz Cloud](https://ployz.dev/docs/self-hosting.md): Run the Ployz dashboard on your own infrastructure with Docker Compose.
- [Add a server](https://ployz.dev/docs/servers/add-a-server.md): What a server needs, the command to paste on it, and the ports to open.
- [Add many servers](https://ployz.dev/docs/servers/add-many-servers.md): Install once per host, review the waiting servers, then enroll them together.
- [Manage servers](https://ployz.dev/docs/servers/manage-servers.md): Server status, what runs where, roles, upgrades, and removing a server.
- [Configs](https://ployz.dev/docs/services/configs.md): Create shared text files, mount them into services, and review changes before deploying.
- [Databases](https://ployz.dev/docs/services/databases.md): Run PostgreSQL, MySQL, Redis or MongoDB next to your app, connect to it, and back it up.
- [Domains](https://ployz.dev/docs/services/domains.md): Give a service an https address, use your own domain, and choose the port it reaches.
- [Move a volume](https://ployz.dev/docs/services/move-a-volume.md): Copy a volume to another server, and move it and its service there.
- [Private networking](https://ployz.dev/docs/services/private-networking.md): How services reach each other by name, and how you reach them from your laptop.
- [Restore a volume](https://ployz.dev/docs/services/restore-a-volume.md): Bring a volume back to an earlier point, as a new volume, from its mirror or an old copy.
- [Scaling and multiple servers](https://ployz.dev/docs/services/scaling.md): Run more copies of a service, spread them over your servers, and know what to do when a server goes down.
- [Services](https://ployz.dev/docs/services/services.md): Add a service from a repository, an image or a database, find your way around it, and rename or delete it.
- [Service settings](https://ployz.dev/docs/services/settings.md): Every field in a service's Settings: what it does, its default, and when to change it.
- [Variables](https://ployz.dev/docs/services/variables.md): Configure your services with environment variables, secrets and references to other services.
- [Volumes](https://ployz.dev/docs/services/volumes.md): Keep files across deploys and restarts.
- [My app isn't reachable](https://ployz.dev/docs/troubleshooting/app-not-reachable.md): Fix "This app didn't respond", "Nothing is deployed here", wrong ports, custom domains, certificates and services that can't reach each other.
- [Troubleshooting builds](https://ployz.dev/docs/troubleshooting/builds.md): Fix builds that fail, wait, run out of memory or disk, or can't run on GitHub Actions.
- [Troubleshooting deployments](https://ployz.dev/docs/troubleshooting/deployments.md): Fix failed builds, missing images, failed health checks, failed pre-deploy commands, crashing services and pushes that don't deploy.
- [Troubleshooting servers](https://ployz.dev/docs/troubleshooting/servers.md): Fix install failures, servers that don't join or go offline, and full disks.
- [Trace a request](https://ployz.dev/docs/troubleshooting/trace.md): See which server answered a request to your domain, and what it knows about the service there.