/dev/push: a self-hosted Vercel alternative you run on your own server
Like Vercel, but open source and for all languages.
At a glance
- What is it?
- devpush deploys Docker Compose apps from a connected GitHub repository onto your own servers. The install is a single npx devpush@latest init wizard, and a small Linux agent then manages HTTPS, logs, monitoring and backups on each server.
- Who is it for?
- Adopt devpush if you already run your own servers, want GitHub push-to-deploy with HTTPS handled by an agent on each server, and can maintain those servers yourself. Do not adopt it if you want a managed platform or need guaranteed zero-downtime updates, since the README says updates happen in place and do not guarantee zero downtime.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 13 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 14, 2026, and from our analysis. They are not legal advice.
Star history
- hunvreus/devpush4,832 ★ · +81
| Repository | 2026-09-23 | 2026-11-14 |
|---|---|---|
| hunvreus/devpush | 4.8k | 4.8k |
81 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The problem /dev/push solves, and who feels it
Vercel, Render and Netlify give you push-to-deploy on hosted infrastructure. devpush takes the same workflow and moves it onto servers you own. The repository describes it as "Like Vercel, but open source and for all languages," and the README as an open-source deployment platform for your own servers: connect a GitHub repository, configure your Docker Compose app and push to deploy. Teams, environments, encrypted variables, a REST API and MCP are included. The target reader is a small team or a solo developer who already runs servers. The build contract is Docker Compose: Compose is required, and Dockerfiles can be used within it, so any stack that runs in containers can be deployed. The trade-off is that you inherit the operational work the hosted platforms absorb, and the README is explicit about two limits: updates happen in place and do not guarantee zero downtime, and you should only deploy trusted code because Docker workloads can access their host.
How deployment works: GitHub App, Docker runners, per-deployment domains
The current repository splits devpush into a dashboard and an agent. The dashboard lives under app/ and runs on Cloudflare Workers or Node. A small Linux agent, under agent/ and tested with go test against ./agent/internal/agent, manages applications on your servers, including HTTPS, deployment logs, monitoring and backups. Deployments start from a connected GitHub repository, and the root test script includes app/scripts/github-app.test.mjs, so GitHub App handling sits in the dashboard. The agent's Docker smoke tests are named for running a real Docker Compose deployment and routing through a real Traefik. An example Compose app ships in examples/compose-web/, and configuration and operations are documented under docs/, starting at docs/index.md.
Installing /dev/push on a fresh Ubuntu server
The README points to docs/self-hosting.md for installing devpush on Cloudflare or with Docker Compose, and to docs/getting-started.md for deploying a first app once the dashboard is running. The install itself is one command:
npx devpush@latest initThe wizard creates a standalone project using the devpush npm package, configures your target and offers to deploy. For an existing project, the README points to docs/package-installation.md. To run from source instead, the development path requires Node.js 22.12+ and pnpm 10.17+:
pnpm install
pnpm configure
pnpm devChoose local development and open http://localhost:7429. docs/local-setup.md covers tests and the deployment VM, and docs/development.md covers code boundaries and plugins.
Where /dev/push is the wrong tool
The first real limit is operational: you run the servers, and the Linux agent manages applications on them. If your team has no one who can administer a server, a hosted platform is the cheaper answer regardless of licence. The second is the deployment contract: Compose is required, so an app has to be described as a Docker Compose app, with Dockerfiles used inside it. The third is availability during updates: the README says updates happen in place and do not guarantee zero downtime. The fourth is trust: only deploy trusted code, because Docker workloads can access their host. Deployments start from a GitHub repository, and the README names no other Git host.
How it differs from Dokploy and from Vercel itself
The README does not compare devpush with Dokploy or any other self-hosted panel, so that comparison has to come from your own evaluation. What this repository does show is its own shape: a dashboard that runs on Cloudflare Workers or Node, a separate Linux agent on your servers, Docker Compose as the required app format, and a REST API and MCP alongside teams, environments and encrypted variables. Against Vercel, the difference is ownership. devpush runs your apps on your own servers, with HTTPS, deployment logs, monitoring and backups handled by the agent, and you get the bill for the machines. The README does not claim feature parity with any of these platforms, and it is explicit that updates do not guarantee zero downtime.
Maintenance, updates and the MIT licence
The last push to the repository was on 2026-10-30, and the most recent releases are v1.0.2 and v1.0.3 on 2026-10-30 and v1.1.0 on 2026-11-02, so the project is shipping actively. The repository is not archived. The README says updates happen in place and do not guarantee zero downtime, and points to CHANGELOG.md for changes and TODO.md for planned work. Backups are among the things the agent manages on your servers. The licence is MIT, which permits commercial and private use and modification. This is a description of the licence text, not legal advice; check the LICENSE.md file in the repository for the exact terms before you rely on them.
Editorial conclusion
Adopt devpush if you already run your own servers, want GitHub push-to-deploy with HTTPS handled by an agent on each server, and can maintain those servers yourself. Do not adopt it if you want a managed platform or need guaranteed zero-downtime updates, since the README says updates happen in place and do not guarantee zero downtime. Before you commit, read docs/self-hosting.md, decide whether the dashboard will run on Cloudflare Workers or Node, and only deploy trusted code, because Docker workloads can access their host.
Frequently asked questions
What is /dev/push?
devpush is an open-source deployment platform for your own servers, described in the repository as 'Like Vercel, but open source and for all languages'. You connect a GitHub repository, configure your Docker Compose app and push to deploy. It is MIT licensed.
What are the prerequisites for installing /dev/push?
The README points to docs/self-hosting.md for installing on Cloudflare or with Docker Compose, and the npx devpush@latest init wizard configures your target. Apps must be Docker Compose apps, and running from source requires Node.js 22.12+ and pnpm 10.17+.
Does /dev/push support zero-downtime deployments and rollback?
No. The README says updates happen in place and do not guarantee zero downtime, and it does not describe a rollback feature.
How do I update a /dev/push installation?
The README says updates happen in place and do not guarantee zero downtime; for configuration and operations it points to the documentation starting at docs/index.md.
What licence does /dev/push use?
The repository is MIT licensed, which allows commercial and private use and modification. The exact terms are in LICENSE.md.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/hunvreus-devpush)Star history chart for your README
[](https://hysenlabs.com/projects/hunvreus-devpush)Was this useful?