Skip to content

Git push deploys

Git push to deploy on your own servers.

Every push to your branch, yours or your coding agent's, deploys to servers you rent once your GitHub checks pass.

One push, from commit to the live site. If any step fails, the old version keeps serving.

Only what changed

Give each service a root directory and watch paths, and a push deploys only the services it touched.

Old version keeps serving

A new replica has to answer your health check before the old one stops.

No Dockerfile, no registry

Common languages build without a Dockerfile, and the image goes straight to your servers.

Hold the deploy for CI.

Turn on Wait for CI and a commit deploys once its GitHub checks pass. A newer push replaces one still waiting.

A service's Source settings in the Ployz dashboard: repository, Branch, Add root directory, and the Auto-deploy and Wait for CI switches

Edits wait for Deploy.

Dashboard changes, yours or your agent's, turn pink and stay staged until you deploy. Publish them and the next push takes them along.

The Details panel in the Ployz dashboard: a deploy message field, one change marked will be added, and the Discard all changes, Publish and Deploy changes buttons

Compared with the platforms.

What you needHeroku, Render, RailwayPloyz on your server
Deploy on pushYes, on their serversYes, on your servers
Wait for CIRailway reads GitHub Actions onlyChecks from any GitHub app
MonorepoRender, Railway: root directory plus pathsRoot directory plus up to 50 watch paths
Dashboard editsHeroku restarts on a config changeStaged until you press Deploy
Overlapping deploysRender: queue or cancel, per workspaceOne per environment, the newest waits

Good to know.

  • Migrations stay applied if the deploy then fails.
  • A service with a volume, like Postgres, stops briefly while it swaps.
  • GitHub only, and Wait for CI reads checks, not commit statuses.
  • Builds on your server share its CPU and need 2 GB of RAM.

Questions

What is git push deploy?

Pushing a commit to a Git branch and having that push build and release your app, with no other step. Heroku made it popular. Most platforms now do it through a GitHub integration.

How do I deploy on push to my own server?

Install Ployz on the server, connect the GitHub repository to a service and deploy once. From then on every push to the service's branch builds on your server and deploys.

Can it wait for GitHub Actions to pass?

Yes. Turn on Wait for CI under Settings → Source. The deploy waits for the commit's GitHub checks, from Actions or any other app. A failed check stops that commit.

What happens if a deploy fails?

A failed build changes nothing. A replica that fails its health check is stopped and the old one keeps serving. The deployment page says why it failed.

How is this different from Dokku or a git hook?

Dokku and a post-receive hook deploy when you push to a remote on the server. Ployz hears pushes to GitHub, so it can wait for checks and skip services by watch path. The git push deploy article compares five setups.

Can my coding agent deploy this way?

Yes. An agent that pushes to the branch deploys like you do. Dashboard and CLI edits it makes stay staged until a deploy, and every deploy, restart or delete your agent asks for waits for you to approve.

What does it cost?

Nothing, on any number of servers, with unlimited projects and preview environments. Custom domains with https, monitoring, searchable logs and databases with a restore point are included. You pay your provider for the servers.

Your servers. The whole platform. Free on your own servers.

Deploy your app

Facts checked 2026-10-18.