Existing VPS, one guided path

Choose a project. Connect a server. Get the URL.

OpsTrace finds the apps in your work folder, uploads the one you choose to your VPS, starts it safely, and shows the URL only after it responds.

See how it works Read the current status
OpsTrace showing projects found in a local work folder
OpsTrace runs on your computer. Your source and credentials stay local until you approve a launch.
1Choose your work folder
2Connect your VPS
3Launch and verify

How it works

The deployment machinery stays behind three plain decisions.

No cloud console tour. No command editor. No local Docker requirement.

  1. 01

    Point OpsTrace at your projects

    Choose the folder where you keep your work. OpsTrace identifies deployable apps without uploading your code.

  2. 02

    Connect the server you already own

    Enter the VPS address, SSH user, and optional key path. The private key is never copied into the OpsTrace database.

  3. 03

    Launch, then wait for proof

    OpsTrace uploads a filtered source bundle, runs fixed Docker Compose steps on the VPS, checks the public URL, and saves the endpoint only when it responds.

What you need

Your computer stays simple. The server does the deployment work.

On your computer

  • The portable OpsTrace Windows beta
  • Your projects in a normal folder
  • An SSH key or SSH agent access

Python, Docker, and Git are not required for the guided local-folder path.

On your VPS

  • SSH access
  • Docker and Docker Compose
  • tar and an open application port

OpsTrace checks the server before the launch button appears.

The product

One journey, shown as it actually appears.

These are captured from the server-rendered local application, not design mockups.

OpsTrace work folder and detected projects screen
Find your appsChoose one work folder.
OpsTrace project selection and VPS connection flow
Connect your VPSOnly the details needed to reach your server.
OpsTrace existing VPS launch path
Check before launchServer readiness gates the real action.
OpsTrace project page refusing to present synthetic demonstration data as a live endpoint
Keep the result honestSynthetic demo records never appear as a live app.

Current beta status

Useful, narrow, and honest about the missing proof.

The portable Windows application and guarded VPS launch path are implemented and covered by automated tests. A deployment against a real user-owned VPS has not yet been completed in this environment.

Windows package
Built and locally smoke-tested
Folder to VPS path
Implemented
Real VPS smoke
Pending
Cloud providers
Future work, not presented as deployable
Repository
Private

Safety by constraint

OpsTrace does less on purpose.

No arbitrary remote commands.The VPS checks and deployment steps are fixed and validated.

Credentials stay local.Private key contents and secret values are not stored in SQLite.

Controlled remote paths.Uploads stay under the OpsTrace application directory.

No fake success.A live endpoint is saved only after the configured HTTP URL answers.

Private Windows beta

Unzip it, run OpsTrace.exe, and choose your work folder.

The self-contained portable ZIP is ready for invited testers. There is no public download or hosted OpsTrace account yet.

No Python setup No local Docker setup Runs on 127.0.0.1