Windows · macOS · Linux

Self-hosted stacks, installed in seconds.

Tick what you need, point it at a folder, and ops sets up every stack in its own directory: your domain, fresh secrets, safe updates and backups. No copying files between machines.

  • Python standard library only
  • Window listens on 127.0.0.1 only
  • Never overwrites your edits
75+Ready-made stacks
17Categories
3Operating systems
1Command to start
Features

Everything between "git clone" and "it's running"

A window or a terminal menu, whichever you prefer, with the boring parts handled.

Terminal or window

Use it your way

The same tool runs as a keyboard-friendly menu in any terminal, or as a local window with a mouse.

  • Menu over SSH. Tick stacks with the keyboard on a remote server.
  • Window on your PC. ops ui opens a dashboard, library, editor and docs.
  • Scriptable. ops add and ops update run without any menu.
~/stacks
How it works

Three steps, no copying


Install ops

Paste one command. It installs Python if needed and adds the ops command.

Unlock and pick

Run ops ui, enter your password, choose a folder and tick the stacks you want.

Run it

Each stack lands in its own folder. Start it from the window or with docker compose up -d.

Why ops

Less typing, fewer surprises


By hand

  • Copy folders between machines and hope nothing is missing
  • Edit every .env and invent passwords yourself
  • Find out about a port clash when a container fails
  • Lose your edits, or never update, because merging is scary

With ops

  • Tick stacks and each lands in its own folder
  • Your domain and random secrets are filled in for you
  • Every published port in one table, conflicts flagged early
  • Diff and merge, with a backup before every change
Keyboard first

Mouse optional


CtrlKQuick find/SearchSpaceTick a stackASelect allFFull-screen docsTLight / dark?All shortcutsEscClose
Security

Private by design

This page is public. The stack library is not.

  • Password-protected library. Stacks are only served after the password check.
  • Read-only access. The server reads one private repository with a read-only token that never reaches your machine.
  • Secrets stay local. Passwords are generated on your machine and written only to your .env files.
  • The window is local-only. It listens on 127.0.0.1 with a per-session token.
your machine this site private repository ops ──password──────────▶ function ──read-only──▶ stacks/ ops ◀──stack files─────── checks password token stays here install.sh / install.ps1 ◀── static files (no secrets)
FAQ

Good questions


What do I need on my machine?

Nothing up front. The installer sets up Python 3.8+ if it is missing. To run stacks you need Docker with Compose v2; the Doctor page checks this for you.

Which systems are supported?

Windows 10/11, macOS and any mainstream Linux. Many stacks assume a Linux host, so use a Linux server to run them and any system to manage them.

Does it overwrite my changes?

Never. If you edited a file that also changed upstream, yours is kept and the new version is saved beside it. The Changes tab shows a diff and lets you choose.

Can I undo an update?

Yes. A configuration backup is made before every update and restore, and you can restore any backup from the stack's Backups tab.

Can I manage projects that already run on a server?

Yes. Adopt existing projects finds Docker projects on the machine and manages them in place. Nothing is moved, copied or deleted.

Can I run it on a remote server?

Yes. Use ops ui --no-browser on the server and forward the port over SSH, or use the terminal menu directly.

How do I remove it?

Delete the .ops folder in your home directory and the ops launcher. Folders it created for your stacks are yours and stay untouched.

Ready when you are.

One command, then pick your stacks.

Install ops