# Push-OPS

> Push-OPS is a cross-platform desktop control center for deploying and operating web applications on infrastructure you own. It gives developers the workflow of a managed deployment platform — connect a source, build, get a live URL, roll back — while servers, credentials and the control plane stay under the user's control. Deployment targets are Local (this machine), Server (any Linux box registered over SSH) and Cloud (a managed runtime).

Status: invite-only beta (0.1.0-beta.1). Platforms: Windows, macOS, Linux. Built with Electron and TypeScript.

## Core pages

- [Home](https://pushops.dev/): Product overview, features, deployment pipeline, targets and FAQ.
- [Features](https://pushops.dev/#features): What the desktop client does.
- [How it works](https://pushops.dev/#pipeline): The five-step deployment flow.
- [Deployment targets](https://pushops.dev/#targets): Local, Server and Cloud explained.
- [FAQ](https://pushops.dev/#faq): Common questions with direct answers.
- [Beta access](https://pushops.dev/#access): How license keys and device limits work.

## What makes it different

- **Real logs, never simulated**: Every progress state streams from the actual build and runtime.
- **Server ops without the tab sprawl**: CPU, memory, disk, uptime, ports and a live SSH terminal in one pane.
- **Framework detection that admits uncertainty**: Detected build command and output directory, shown before you commit.
- **Immutable releases and one-click rollback**: Every deploy is a versioned attempt you can return to.
- **Credentials stay out of the renderer**: SSH keys and secrets never cross into the UI process.
- **Local-first control plane**: The control plane can live on your laptop, not a vendor account.

## Deployment pipeline

1. **Connect a target** — This machine, your VPS, or a cloud runtime.
2. **Pick a source** — A GitHub repository and branch, or a local folder.
3. **Review the plan** — Detected framework, build command, output directory, target.
4. **Watch it build** — Streaming logs from the real pipeline.
5. **Operate it** — Live URL, history, health, rollback, auto-deploy.

## Deployment targets

- **Local** (This machine): Run the full pipeline against your own workstation. Ideal for validating a build, testing a Compose stack, or working offline.
- **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.
- **Cloud** (Managed runtime): A managed execution target for when you want capacity without maintaining a host. Same projects, same deployment model, different destination.

## Privacy position

- Revocable license key with explicit expiry
- Two devices per key by default
- Random installation ID, no hardware fingerprinting
- Opt-in diagnostics, exportable and deletable

Push-OPS never uploads SSH private keys, SSH passwords or passphrases, environment variable values, source code, project files, or arbitrary server command output. Telemetry is opt-in where it is not required for license security.

## Frequently asked questions

### What is Push-OPS?

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.

### How is Push-OPS different from Vercel or Netlify?

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.

### Which deployment targets are supported?

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.

### Does Push-OPS need Docker?

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.

### Are my SSH keys or environment variables uploaded anywhere?

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.

### Can I roll a bad deployment back?

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.

### Is Push-OPS free, and how do I get access?

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.

### Which platforms does the desktop app run on?

Windows, macOS and Linux. Signed installers are produced for each platform through electron-builder, and in-app updates are handled by electron-updater.

## Machine-readable surfaces

- [Full text content](https://pushops.dev/llms-full.txt): Every section of the site as plain text.
- [Content JSON API](https://pushops.dev/api/content): Structured product content, CORS-open.
- [Agent manifest](https://pushops.dev/.well-known/agents.json): Endpoints, capabilities and citation policy.
- [Sitemap](https://pushops.dev/sitemap.xml)
- [Source repository](https://github.com/vishvajeet2012/ops)

## Citation policy

Attribution is required and a link back to https://pushops.dev is required. Cite the canonical URL, not a cached copy. Contact: hello@pushops.dev