An environment for every pull request. Each preview runs the pull request's code at its own
https address. Copy the database service and the preview gets its own empty database, seeded by
your setup command. A database you leave shared gives the preview production data. On merge,
production gets the code and the preview's setting changes. The Ployz · ready to merge check
lists those changes on the pull request first.
Review before you deploy. Edits from the dashboard, the CLI or an agent wait as a draft. You
read the diff, then deploy it.
Deploy apps, databases and previews to your own servers. Run Ployz Cloud from your agent.
2026-11-08
ดาว
—
เครื่องมือ
—
อัปไทม์
—
The CLI does what the dashboard does. Commands print JSON with --json. A change that would
delete a service, a volume or a domain stops until a person approves it. An agent can't approve
it.
One private network across your servers. Add a server with ployz server add. Your servers
share a WireGuard network, and a service runs up to 50 replicas across them. A service with a
volume runs on the server that holds its data, one replica by default.
Apps that outlive Ployz Cloud. Your apps keep running on your servers if Ployz Cloud is down
or goes away. The engine and the dashboard are open source.
Use it with your agent
Paste this into your coding agent.
Set me up for Ployz: https://ployz.dev/agents.md
It installs the CLI and the Ployz skill, signs you in and registers the Ployz MCP tools. From
then on it runs the same commands you would.
> Copy production with its own worker, deploy it there, then stage it back.
$ ployz env branch try-worker --copy worker # Made Branch shop/try-worker of production.
$ ployz deploy --env try-worker # 2 deployed · across 1 server
$ ployz env sync --env try-worker --to # Synced try-worker → shop/production.
The change waits in production for you to review and deploy.
Quick start
You need a Linux server with systemd that you can reach as root over SSH. See the
server requirements.
Install the CLI.
curl -fsSL https://ployz.sh | sh
Sign in to Ployz Cloud.
ployz login
From your app's directory, point Ployz at your server.
ployz up --server root@your-server
Ployz installs itself on the server, builds your app and prints its https address.
Deploy on every push, and give each pull request a preview with its own seeded database.
ployz github connect # install the Ployz GitHub App
ployz set shop.repository=you/shop # build from GitHub instead of uploads
ployz deploy
ployz env pr you/shop --on --from production --copy postgres --setup 'shop=pnpm db:seed'
ployz up names the service after your app's directory, here shop. The preview copies a
postgres service you've added.
How it works
Each server runs a small Ployz daemon next to Docker. Your servers share a WireGuard network and
keep each other up to date. Every server serves https itself through Caddy, so there's no load
balancer to rent. The dashboard and the CLI tell your servers what to run. Once deployed, your
apps depend on neither. Generated ployz.app addresses use Ployz's DNS. A custom domain with an
A record pointing at your servers doesn't.
Status
Can I move a production app? Yes, if the gaps below are fine for you. If you need managed
backups and automatic failover today, wait. Ployz is young and changes quickly. Work through the
production checklist first.
You look after the OS. Ployz doesn't install OS updates.
No offsite backups yet. Volume mirrors keep a copy on another server. Dump your databases
on a schedule and keep the dumps off your servers, or keep your hosted database.
No automatic failover. If a server dies, what ran only there stops. Replicas on other
servers keep running.
No Docker Compose files. Add each container as its own service.
Alerts are email only. Ployz Cloud emails you when a service goes down or crashes.
Soon: offsite backups, automatic rollbacks, and moving a database to a bigger server without
downtime.
Pricing
Ployz is free on your own servers, custom domains included. Paid Ployz Cloud
plans are coming soon. Your hosting provider bills you for the servers.
Agents write most of Ployz. I design the loop they run in, and I answer for what comes out of it.
Every change ships as a small PR. The agent has to prove it by running Ployz the way you would,
on real servers. If it can't show me that, it doesn't merge. Low-risk PRs merge once the checks
pass. The orchestrator, networking and anything touching your data get a human review first.
When an agent gets something wrong, we turn the mistake into a lint rule or a test. Every mistake
makes the system stricter, and that's the part I trust.
Contributing
Bug reports and feature requests go in GitHub Issues.
The repository holds two projects. core/ is the engine, CLI and daemon, in Rust.
dashboard/ is Ployz Cloud, in TypeScript. Each README explains how to build it.
License
The engine in core/ is Apache-2.0. The dashboard in dashboard/ is AGPL-3.0.
