Local-first VPS launch assistant

Put your app on your VPS.

Choose the folder where your projects live. Pick a server already in your SSH config. OpsTrace checks what is running, follows the existing deployment style, and shows the URL only after it responds.

See the three steps Read the MVP status
  • Runs on your computer
  • Uses your existing VPS
  • No AI key required

How it works

Three decisions. The deployment detail stays out of the way.

  1. 01

    Choose your work folder

    OpsTrace finds the apps inside it. Source files remain on your computer until you approve a launch.

  2. 02

    Choose your VPS

    Named hosts come directly from ~/.ssh/config. With permission, OpsTrace shows running apps, ports, and deployment tools without saving the inventory.

  3. 03

    Launch or update

    OpsTrace uses a guarded Docker Compose path, verifies the public URL, and records success only when the app answers.

The local app

Made for the person who wants the URL, not a DevOps course.

The main screen shows projects. The launch screen asks for a VPS and permission to inspect it. Technical history stays behind advanced details.

OpsTrace launch screen showing a selected project and VPS selection
Actual server-rendered OpsTrace UI. No design mockup and no hosted account.

MVP boundary

One supported direction, stated plainly.

Project sourceLocal project folderFiltered upload; secrets and dependency folders excluded
TargetExisting VPS over SSHNamed hosts are read from local SSH config
DeploymentDocker ComposeNew launch or guarded update of a detected Compose project
ResultVerified public URLSaved only after the configured health URL responds
Not in this MVPCloud provisioning and managed infrastructureAWS, Azure, GCP, domains, databases, and Kubernetes are future work

Local by design

Your credentials do not become OpsTrace data.

SSH config stays local.Hosts and key paths are read when needed and are not copied into the primary workflow database.

Inspection needs permission.Read-only VPS checks run only after you approve them. Raw command output is not persisted.

No arbitrary command box.Launch and update steps use narrow, validated command patterns.

No AI setup.The deterministic MVP works without an AI provider and never asks the beginner for a model key.

Current status

This is an MVP, not a cloud platform.

The VPS workflow is implemented and tested locally. A real deployment against an external user-owned VPS remains the release proof gate.

Local app
Working
SSH config discovery
Working, non-persistent
VPS inventory
Permissioned, read-only
Compose launch and update
Implemented
External VPS smoke
Pending
macOS and Linux packages
Release work in progress
Repository
Private during MVP hardening