PUSH-OPS — FULL CONTENT ================================================================ Canonical URL: https://pushops.dev Generated: 2026-09-07T18:48:14.314Z Version: 0.1.0-beta.1 (invite-only beta) License: Content is free to quote with attribution and a link back to https://pushops.dev. Contact: hello@pushops.dev Repository: https://github.com/vishvajeet2012/ops ---------------------------------------------------------------- SUMMARY ---------------------------------------------------------------- Push-OPS is a desktop control center for deploying web apps to your own VPS, local machine, or cloud. Vercel-like simplicity, self-hosted control, real build logs, SSH server management, and rollbacks. Push-OPS is not a second deployment engine. The OPS platform is the engine and source of truth for API routes, deployment pipelines, runtimes, server provisioning, authentication, storage and background jobs. Push-OPS is the desktop client that makes those capabilities simple to operate. The product promise: Vercel-like deployment simplicity with self-hosted control, portability, and an operator-friendly desktop experience. ---------------------------------------------------------------- HERO ---------------------------------------------------------------- Ship to servers you actually own. 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. ---------------------------------------------------------------- AT A GLANCE ---------------------------------------------------------------- 3 — Deploy targets (Local, Server, Cloud) <60s — First deploy (Connect to live URL) 0 — Fake progress bars (Every state is real) 100% — Your infrastructure (No vendor runtime lock) Supported runtimes, sources and components: Docker, Next.js, Node.js, Python, Go, Rust, PostgreSQL, Redis, Ruby on Rails, Laravel, Django, Bun, GitHub, Nginx, Vite, Astro, Nuxt, Linux ---------------------------------------------------------------- FEATURES ---------------------------------------------------------------- 01. REAL LOGS, NEVER SIMULATED 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. 02. SERVER OPS WITHOUT THE TAB SPRAWL 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. 03. FRAMEWORK DETECTION THAT ADMITS UNCERTAINTY 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. 04. IMMUTABLE RELEASES AND ONE-CLICK ROLLBACK 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. 05. CREDENTIALS STAY OUT OF THE RENDERER 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. 06. LOCAL-FIRST CONTROL PLANE 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. ---------------------------------------------------------------- HOW IT WORKS — THE DEPLOYMENT PIPELINE ---------------------------------------------------------------- Step 01 — Connect a target This machine, your VPS, or a cloud runtime. Add a server with host, SSH port, user and auth method. Push-OPS tests the connection before it saves anything, so a bad credential fails at setup instead of mid-deploy. Step 02 — Pick a source A GitHub repository and branch, or a local folder. Connect GitHub once and select a repo and branch, or point at a directory on disk. The Electron main process inspects local projects so the renderer never touches your filesystem. Step 03 — Review the plan Detected framework, build command, output directory, target. Push-OPS freezes a deployment summary before execution: what gets built, how, and precisely where it lands. You approve it, then it runs. Step 04 — Watch it build Streaming logs from the real pipeline. Install, build and release output streams live. Health checks report readiness, OpenResty routes the domain, and Certbot issues HTTPS when the target needs it. Step 05 — Operate it Live URL, history, health, rollback, auto-deploy. The dashboard answers what is deployed, what is failing, where the next deploy runs, and what to do next. Redeploy, roll back, or turn on auto-deploy from the same screen. ---------------------------------------------------------------- DEPLOYMENT TARGETS ---------------------------------------------------------------- Every deployment shows both what was deployed and where it runs. The target selector has exactly three product-level choices. LOCAL — This machine Run the full pipeline against your own workstation. Ideal for validating a build, testing a Compose stack, or working offline. - Zero network setup - Docker or bare process - Same logs as production SERVER — Your own VPS A Linux box you rent or rack. Push-OPS connects over SSH, checks the machine, installs missing components, and manages Docker or bare workloads. - SSH key or password auth - Component install on demand - Live terminal and health CLOUD — Managed runtime A managed execution target for when you want capacity without maintaining a host. Same projects, same deployment model, different destination. - No host maintenance - Same rollback model - Portable project config ---------------------------------------------------------------- PRODUCT PRINCIPLES ---------------------------------------------------------------- 1. Simple on the surface, real underneath. Every progress state comes from the real API or runtime. The client never shows fake deployment success. 2. Desktop-first and local-first. For a solo user the control plane can stay on the user's machine and reach a remote target over SSH. 3. One platform model. Local, Server and Cloud are deployment targets, not three unrelated products. 4. Safe defaults. Test a server before saving it, validate target ownership, keep credentials out of the renderer, and fail with actionable messages. 5. High-signal UI. Restrained typography, clear status, real logs, progressive disclosure. ---------------------------------------------------------------- BETA ACCESS, LICENSING AND PRIVACY ---------------------------------------------------------------- The beta is invite-only. 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. - Revocable license key with explicit expiry - Two devices per key by default - Random installation ID, no hardware fingerprinting - Opt-in diagnostics, exportable and deletable A license key supports a validity window, a status (active, expired, revoked or suspended), a maximum device count, server-side device registrations, and administrator actions to revoke a device, reset a device slot, extend the expiry, or revoke the whole key. Device identity is a random installation identifier stored on the machine. It is not a covert hardware fingerprint. Push-OPS never uploads SSH private keys, SSH passwords or passphrases, environment-variable values, source code, project files, or arbitrary server command output. The renderer does not decide whether a key is valid — the API returns a signed license session and the desktop revalidates it periodically. ---------------------------------------------------------------- FREQUENTLY ASKED QUESTIONS ---------------------------------------------------------------- Q: What is Push-OPS? A: 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. Q: How is Push-OPS different from Vercel or Netlify? A: 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. Q: Which deployment targets are supported? A: 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. Q: Does Push-OPS need Docker? A: 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. Q: Are my SSH keys or environment variables uploaded anywhere? A: 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. Q: Can I roll a bad deployment back? A: 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. Q: Is Push-OPS free, and how do I get access? A: 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. Q: Which platforms does the desktop app run on? A: Windows, macOS and Linux. Signed installers are produced for each platform through electron-builder, and in-app updates are handled by electron-updater. ---------------------------------------------------------------- END OF CONTENT ----------------------------------------------------------------