Git push to deploy: every push goes live
Connect GitHub, GitLab or Bitbucket and every push to your branch builds and deploys. Live build logs, rollbacks and deploy notifications come with it, and builds are never charged by the minute. Hosted in the UK, on servers we own and run ourselves.
From push to live in four steps
You can watch every step in the dashboard.
Connect a repository
Authorise GitHub, GitLab or Bitbucket, then choose the repository and branch. We register the webhook for you.
Push
Push to your deploy branch. The deploy is queued, and the newest push wins if several arrive at once.
Build, with a live log
We install your dependencies and build your app with Node 18, 20 or 22, Bun, or your Dockerfile.
Go live
The new version replaces the old one, ScaleShield and SSL stay in front, and your deploy notifications fire.
Pull-request previews
Each pull request on GitHub gets a temporary copy of your app on its own address, so reviewers try the change before you merge. On Pro, Studio, Agency, Solo Plus, and Solo HA.
Previews sleep when idle
Idle previews pause so they do not use your plan. The next visit wakes them, and closing the pull request stops them.
Roll back by redeploying
Deploy any earlier commit from your history. Every deploy maps to a commit, so you always know what is live.
Live build logs
The build output streams into the dashboard as it runs, in full, so a failed build is quick to fix.
Deploy notifications
Send a message to Slack, Discord or your own web address when a deploy succeeds or fails.
Queued deploys
Deploys run one at a time per site, and the newest one wins, so an older build never overwrites a newer one.
Your framework, your build
14 presets cover the common cases: Next.js, Astro, Nuxt, SvelteKit, Remix, Vite apps, Bun, static sites, Strapi, Medusa and Payload. Anything else ships from a Dockerfile in your repository.
- Node 18, 20 or 22: chosen per app. Bun is available as its own runtime.
- Your own Dockerfile: for full control of the image, including one in a sub-folder.
- Environment variables: set per key in the dashboard. Auto-detected builds read them at build time and run time; Dockerfile apps take build-time values in the Build args field.
- Cron jobs: schedule recurring commands in your container from the dashboard.
Deployment FAQ
Which git providers can I connect?
GitHub, GitLab and Bitbucket. Authorise the repository in the dashboard, pick the branch, and we register the webhook (the message your provider sends us on each push). Every push to that branch then builds and deploys.
Can I deploy without pushing?
Yes. Deploy any commit from the dashboard at any time. Deploys queue one at a time per site, and the newest one wins, so two quick pushes never race each other.
How do I roll back?
Every deploy is tied to a git commit. To roll back, deploy an earlier commit from your deploy history. Your database is separate, so rolling back code does not touch your data.
What happens to pull-request previews I stop using?
Idle previews sleep so they do not use your plan, and the next visit wakes them. When the pull request closes, the preview stops.
Which plans include pull-request previews?
Pro, Studio, Agency, Solo Plus, and Solo HA, from £59 a month. Previews work with GitHub repositories. Git deploys on every push come with every paid plan, from Starter at £12 a month.
Ship on every push
A fixed monthly price and builds that are never metered. See performance and security for the rest of the platform, or the pricing page for every plan.