Keep the platform. Drop the bill.
Git push deploys and preview environments, on servers you own.
DeployOpen source · Free on your own servers
Your whole app on one canvas, running on a server you own.
From root prompt to https in one command.
root@server:~#
$ ployz login
$ ployz up --server root@203.0.113.12
Installing Ployz on 203.0.113.12
Building web
✓ https://web.acme.up.ployz.app
Invoices that chase themselves.
Send, remind and get paid, without the follow-up emails.
Sign in, point Ployz at your server, and it installs itself, builds your app and gives it an address.
Builds your app without a Dockerfile, or runs any Docker image.
Start on one server
It runs your whole app: web, workers and databases.
Add servers
One command each, all on one private network.
Leave any time
Open source. If Ployz Cloud went away, your apps would keep running.
No load balancer to rent. Every server is one.
Every server runs its own load balancer, and joins one private network when you add it.
Everything you'd pay a platform for.
feature/pricing → main
Invoices that chase themselves.
Send, remind and get paid, without the follow-up emails.
A preview environment for every pull request.
Its own https address on your servers. Save its settings, and they ship with the merge.
See every change before it deploys.
Edits in the dashboard wait in pink until you press Deploy, or discard them.
You build the app. Ployz runs the servers.
ployz up puts Ployz on your server, builds your app and gives it an https address.
- One command
- No Dockerfile needed
- https address
Every push builds and ships. Every pull request gets its own environment.
- Git push deploys
- Preview environments
- Logs and variables
Add a server with one command, and spread your app across both.
- Up to 50 replicas
- Private network
- No Kubernetes
- Database movesSoon
- Snapshots, backups and rollbacksSoon
Anything you can do, your agent can do too, with output it can read.
- A command for every action
- JSON output
- The canvas follows along
Free on your own servers. Custom domains are $9 a month.
DeployYour servers are billed by your provider. We make money on custom domains, never on usage.
Your servers are billed by your provider.
“I moved my apps to one big server and got about ten times the machine for a tenth of the cost. Then I missed the platform, so I built it.”
The platform, without the landlord.
| Ployz | Hosted platforms | Self-hosted tools | |
|---|---|---|---|
| Where your app runs | Your servers | Their servers | Your servers |
| What you pay for | Your servers, plus $9/mo for custom domains | Plans and usage, often per seat | Your servers |
| A preview environment per pull request | Yes | Yes | Some tools |
| Your whole app on one canvas | Yes | Some platforms | Some tools |
| Dashboard changes reviewed before they deploy | Yes | Some platforms | Rarely |
| Adding a second server | One command | They handle it | Varies by tool |
| If the company disappears | Your apps keep running | You move your app | Your apps keep running |
| Who patches the server's OS | You do | They do | You do |
Questions
How is this different from the platform I pay for now?
It runs on servers you control. You still get a preview environment for every pull request, your whole app on one canvas, and dashboard changes reviewed before they deploy. It's free on your own servers, and custom domains are $9 a month. The trade: the server is yours, so its OS updates are yours too.
How is it different from other self-hosted tools?
One canvas for your whole app, dashboard changes reviewed before they deploy, a preview environment for every pull request, and one command to add a server to your private network. No Kubernetes, and your apps keep running if Ployz Cloud goes away.
Do I need to know Linux?
You need a Linux server you can reach as root over SSH. ployz up does the rest. Ployz doesn't update the server's operating system; that stays with you.
What will this cost me?
Ployz is free on your own servers, and $9 a month only if you want custom domains. Your provider bills you for the servers.
What happens if Ployz goes away?
Your servers keep running your apps. The engine and the dashboard are open source, and you can host the dashboard yourself.
What happens if my server dies?
Services on that server stop. Replicas on your other servers keep running, but Ployz doesn't fail over for you, and a volume lives on the server it's on. Keep a copy of your data off the server; snapshots and backups are coming soon.
Are my databases backed up?
Not by Ployz yet: snapshots, backups and rollbacks are coming soon. Until then, keep regular dumps off the server, or keep your managed database and point your app at it with a variable.
Can I move to a bigger server later?
Moving a database to a bigger server without going down is coming soon. Today you can add servers and run replicas across them.
Will my app work? Do I need a Dockerfile?
Ployz works out how to build Node, Python, Ruby, PHP, Go, Rust, Java, Elixir and more, or builds from your Dockerfile if you choose it. Any Docker image runs too. Compose files aren't supported.
Do I get https and my own domain?
Every first deploy gets an https address. Custom domains are $9 a month.
Can my coding agent run it?
Yes. Everything the dashboard does, the ployz CLI does too, with JSON output. ployz setup agent teaches your agent how, and its changes show on your canvas within seconds.
Is it open source?
Yes. The engine is Apache-2.0 and the dashboard is AGPL-3.0.
Does it scale?
Add servers with one command, and run a service as up to 50 replicas across them, without Kubernetes. There's no autoscaling.
Where do I see logs? Can I get alerts?
Every service's logs are in the dashboard. Ployz doesn't send alerts, so use an uptime monitor.
Is it secure?
Your servers talk over one private network. Ployz doesn't harden or patch the operating system, so use SSH keys, a firewall and automatic updates.
Can my team use it?
Not yet. Ployz is built for one person today, and there are no team roles or permissions.
Which servers can I use?
Any Linux server with systemd that you can reach as root over SSH, on x86-64 or ARM, from any provider.
Your servers. The whole platform.
Deployroot@server:~# exit