Same app, two bills
The table has one typical app at three sizes. Set your own dyno types and plans to see both bills for yours.
- RAM the stack needs
- 3.0 GB
- Heroku Postgres disk limit
- 10 GB
- Heroku$26/mo
List prices, running all month. Basic allows one dyno per process type, so more than one is priced as Standard-1X.
- Your own server + Ployz$7/mo
Smallest Hetzner CX23/CX33/CX43/CX53 with that RAM (1 GB added for the OS), $0.60 IPv4 each. Shared vCPUs, not dedicated. Ployz is free on any number of servers.
Server prices are Hetzner's in Europe. In the US, a DigitalOcean Droplet or Netcup's Manassas datacenter is the cheap option; see Hetzner vs DigitalOcean.
What comes with it
Two more things come with the server, besides the logs in the table:
- Monitoring for every service and server, in the same dashboard as your deploys.
- An agent in the dashboard that answers questions about your app and can restart services, with an approval for anything destructive.
Your coding agent runs it. Risky actions wait for you.
Ployz is built for coding agents on your own servers. Each step your agent would otherwise do by hand over SSH, like installing Docker, setting up certificates or wiring a database to the app, is one Ployz call.
- Less to read.
ployz mcpgives the agent 55 tools, and every CLI command takes--json. - Changes stage first. The agent's edits wait on the canvas until one Deploy ships them.
- Risky actions wait for you. Every deploy, restart or delete your agent asks for waits for you to approve in your organization. No setting turns it off, and an agent connected through
ployz mcpcan't answer the approval.
Moving is a short checklist
Put Ployz on a server, recreate your process types as services, copy the database, then switch DNS. The full migration steps cover maintenance mode, the final database copy and env vars.
$ curl -fsSL https://ployz.sh | sh
Installs the ployz CLI on macOS or Linux.
$ ployz login
Signs in to Ployz Cloud in your browser.
$ ployz up --server root@your-server
Installs Ployz on the server, builds this directory and gives it an HTTPS address.
Or paste Read ployz.dev/agents.md and deploy this repo to my server. into your coding agent. Then add Postgres and Redis, copy your config vars across, and restore your Heroku Postgres dump into the new database before you switch DNS. The quick start shows the same first deploy from the dashboard.