Beta 0.1.0 — invite only
Push-OPS is a desktop control center for deploying web apps to your own VPS, your laptop, or a managed cloud runtime. The workflow of a managed platform. The control of a machine with your name on it.
What it does
Push-OPS is the polished client for a real deployment engine. It shows you what is actually happening on your machines, and refuses to invent the parts it cannot see.
Every progress state streams from the actual build and runtime.
Push-OPS refuses to fabricate deployment success. Build output, container startup, health checks and failures stream straight from the control plane over a live channel. When a deploy fails you get the exact line that broke it, not a spinner that gives up.
CPU, memory, disk, uptime, ports and a live SSH terminal in one pane.
Register a VPS over SSH and Push-OPS inspects it, reports what is missing, and installs only what the chosen runtime needs — Docker, Git, OpenResty, Certbot, rsync. Public versus loopback ports are surfaced explicitly, and a real terminal session is one click away.
Detected build command and output directory, shown before you commit.
The prepare step reads your project and proposes a framework, build command, install command and output directory. You review a frozen summary before anything runs. Nothing is guessed silently and nothing changes your deployment target without an explicit action.
Every deploy is a versioned attempt you can return to.
Each deployment is an immutable build-and-release attempt with its own logs, commit, and artifact. Deployment history keeps the active release visible, so rolling back is selecting a known-good version rather than reconstructing one under pressure.
SSH keys and secrets never cross into the UI process.
The Electron main process holds SSH keys, passphrases and environment values behind a narrow preload bridge. Push-OPS never uploads private keys, environment variable values, source code, or arbitrary command output for licensing or telemetry.
The control plane can live on your laptop, not a vendor account.
For a solo operator, the control plane runs locally against embedded storage and reaches remote targets over SSH. Teams that need an always-on plane can point the same desktop client at a self-hosted PostgreSQL and Redis deployment.
Where it runs
Local, Server and Cloud are destinations inside one platform, not three products. A project moves between them without learning a new operational model — and a deployment always shows both what was deployed and where it runs.
Run the full pipeline against your own workstation. Ideal for validating a build, testing a Compose stack, or working offline.
A Linux box you rent or rack. Push-OPS connects over SSH, checks the machine, installs missing components, and manages Docker or bare workloads.
A managed execution target for when you want capacity without maintaining a host. Same projects, same deployment model, different destination.
Real output
Build output, container startup, health checks and routing all stream from the control plane. There is no client-side progress simulation anywhere in Push-OPS — when a step fails, the line that failed is the line you see.
Beta access
Keys carry an expiry, a status, and a device limit. Activation is validated by the control plane — not by the desktop client — so a revoked key stops working everywhere. Ask for an invitation and we will send one when a slot opens.
Windows · macOS · Linux — signed installers, in-app updates
FAQ
Still unclear on something? The full product brief and the source are public.
Push-OPS is a cross-platform Electron desktop application that deploys and operates web applications on infrastructure you own. It gives you the workflow of a managed deployment platform — connect a source, build, get a live URL, roll back — while the servers, data and control plane stay under your control.
Managed platforms run your app on their runtime and their account. Push-OPS deploys to your VPS, your laptop, or a cloud target you choose, and the control plane can run locally on your machine. You keep the smooth workflow without handing over the infrastructure.
Three: Local (this machine), Server (any Linux box you register over SSH), and Cloud (a managed runtime). They are targets inside one platform model, not three separate products, so a project moves between them without a new mental model.
No. Docker is one runtime option alongside bare process execution. Push-OPS inspects the target and installs Docker, Git, OpenResty, Certbot or rsync only when the runtime you picked actually requires them.
No. SSH private keys, passwords, passphrases, environment variable values, source code and project files never leave your machine for licensing or telemetry. Credentials are held by the Electron main process and are never exposed to the renderer.
Yes. Every deployment is an immutable build-and-release attempt with its own logs and artifact. Deployment history shows the active release, and rollback restores a previously known-good version.
The beta is invite-only. An administrator issues a revocable license key with an expiry and a device limit — typically two machines per key. Activation is validated server-side by the control plane, and keys can be extended, revoked, or have a device slot reset.
Windows, macOS and Linux. Signed installers are produced for each platform through electron-builder, and in-app updates are handled by electron-updater.
