Statio Deploy
All your local apps in one panel, for Mac
A Node project, a Python one, a Docker Compose stack that has to be up
before the others: each with its own command, its own port and its own
.env file. Statio Deploy puts them in a single list. Start and stop them
with one click, read their logs, open them in the browser and edit their variables,
without keeping ten terminals open.
Everything from the menu bar
The part you use most is not the window: it is the menu bar panel. One click on the icon at the top right and all your projects are there in a column, each with its status dot, a button to start or stop it and one to open it in the browser. No hunting for the window, switching Spaces or remembering which terminal runs what: start the backend, open the frontend, stop everything at the end of the day and get back to what you were doing.
When something is running, the icon gets a dot, so you know at a glance. A
project's name takes you to the main window, already open on it, when you need the log
or the .env.
A look inside
What it does
- Works out how to start a project
Pick the folder and Statio Deploy suggests the commands it finds: the scripts in
package.json(with npm, pnpm, yarn or bun, depending on the lockfile), Django, FastAPI, Streamlit and plain Python (with.venv, Poetry or uv), Makefiles, Docker Compose, shell scripts,Procfileand the code blocks in the README. Nothing is executed during detection. - Start and stop, with live logs
Each app runs in your login shell, with your
PATHand your tools, and in its own process group: when you stop it, every child process stops too. Quitting Statio Deploy stops the apps that are still running. - Open in the browser
The app's address can use the variables in its
.env, such ashttp://localhost:${PORT}. Pick a browser for each app, a default one, or "Open with" for a one-off. - .env file editor
Edit, add and delete variables, while the rest of the file is written back exactly
as it was: comments, quotes,
export, line endings. If the file changes on disk while you are editing it, the app tells you before saving. Every save keeps a copy of the previous version outside the project. - Port in use Before starting an app, Statio Deploy checks whether its port is already taken and offers to stop the other process, start anyway or cancel.
- Works with AI agents
Statio Deploy has a built-in MCP server: Claude Code, Claude Desktop, Cursor, Codex
and other MCP clients can list your apps and read their status, logs and
.envand, only if you allow it, start, stop and edit them. It is off until you turn it on, and secret values stay masked. - Dock and notifications The Dock shows how many apps are running, and a notification tells you when one exits on its own.
- No forgotten processes If Statio Deploy quits unexpectedly, on the next launch it finds the apps left running and asks whether to stop them or leave them alone.
- Launch at login It starts with your Mac, if you want it to.
Requirements
A Mac with Apple Silicon or Intel and macOS 26 Tahoe or later. The app's interface is in Italian.
Installation
Open the DMG and drag Statio Deploy to the Applications folder. The app is signed with my Developer ID certificate and notarized by Apple: macOS opens it without warnings.
Updates are not installed automatically: new versions are published on this page.
To check that the downloaded file is intact, shasum -a 256 followed by the file name in Terminal must print:
How to use it
The guide explains in a few minutes how to
add an app, start it, open it in the browser, edit its .env and what
happens when a port is in use.
Support and privacy
Frequently asked questions and contact details are on the support page. The full policy is on the privacy page. In short: Statio Deploy does not connect to the Internet and does not collect any data. Everything stays on your Mac.