Free
$0
Forever, not a trial
- 1 app, with all its services
- Every feature
- Updates
Every local app. One home.
Start, stop and watch every dev server, worker and database on your Mac, grouped by the project they belong to.
Works withNodePythonRuby on RailsGoRustDocker ComposeProcfile
Nine terminal tabs. Three forgotten ports. One crashed worker you didn't notice.
Homeport puts every service of every project in one window, so you can see what's running, what's healthy and what just broke.
01 · Grouped by project
Every service, under the app it belongs to.
Web, API, workers and databases sit together under one name. Start the whole app with one click, in the right order.
Overview
App detail
Start in stages
02 · Logs, health and crashes
Know the moment something breaks.
Color logs for every service, health checks that mean "ready", and one quiet notification when a worker crashes.
- Color logs per service, searchable
- HTTP, TCP and command health checks
- Crash alerts, once per incident
03 · Local HTTPS domains
https://shop.test, not localhost:3000.
Give each app a real name with a trusted local certificate, instead of a port number to remember.
Domains
Certificate
04 · Menu bar
Always there, never in the way.
Homeport lives in your menu bar. Close the window and your services keep running; open the menu to check on them.
- Start, stop and check apps from the menu bar
- Launch at login, and start chosen apps with it
Also included
Port conflicts
Homeport warns before a start when another process already holds a declared port.
Environment health
Checks Node, Python and Ruby versions and missing .env keys before a start. Also from the terminal: homeport doctor.
Quiet notifications
One notification per incident, cleared when the service recovers.
Assistant
Ask why a service crashed or how to add a health check, with your own Anthropic key. You review what is sent.
Command line
homeport up, down, logs and list drive the same engine from the terminal.
Config review
New or changed commands wait for your approval before they run.
Config that lives in your repo.
A short homeport.yaml describes how your app runs. Commit it, and everyone on your team gets the same setup.
- Commit homeport.yaml and share the setup with your team
- Keep personal overrides in homeport.local.yaml
- Or set it up in the app, without writing YAML
version: 1
name: Demo Shop
description: Three tiny Python services for trying out Homeport.
services:
db:
command: python3 db.py
ports: [54329]
health: { tcp: 54329, interval: 2s, start_period: 10s }
api:
command: python3 api.py
depends_on: [db]
health:
http: http://127.0.0.1:8089/health
interval: 2s
start_period: 10s
worker:
command: python3 worker.py
depends_on: [api]
health: { shell: "curl -fsS localhost:8089/health", interval: 5s }
restart:
policy: on-failure
max_retries: 3
backoff: { initial: 1s, max: 8s }
stop: { signal: SIGINT, timeout: 5s }
x-notes: Send SIGUSR1 to the worker to see an interactive y/n prompt.Your Mac, your rules.
Runs only what you approved
Homeport runs a project's commands only after you review and approve its config, and asks again when the config changes.
How we knowNo account
There is nothing to sign up for. Pro is a license key you enter in Settings.
How we knowWhat Homeport sends online
Homeport connects to the internet to check for updates, to activate and check your license, to send an assistant request you approved, and when you ask it to check a project's dependencies, which runs that project's own package tools. Health checks go to the addresses in your own config, normally your own Mac.
How we knowThe assistant sends only what you review
Before every send you see exactly what goes to Anthropic, with your own key. Environment values in your config are always hidden, and likely secrets in logs are masked.
How we know
How Homeport compares
| Feature | Homeport | Terminal tabs | Overmind* | Docker Desktop |
|---|---|---|---|---|
| Services grouped by project | Yes | No | PartlyProcesses from one Procfile | PartlyCompose projects only |
| Health checks | Yes | No | No | PartlyContainers with a Docker health check |
| Crash alerts | Yes | No | PartlyCan restart crashed processes; no alerts | PartlyManual restart; no alerts |
| Local HTTPS domains | Yes | No | No | No |
| Port overview | Yes | No | No | PartlyPer container |
| Mac app with a window | Yes | No | No | Yes |
| Runs services outside Docker | Yes | Yes | Yes | No |
* Overmind runs each process in a tmux session.
Based on each tool's documentation, without plugins; — means the documentation doesn't describe it. Something out of date? Let us know.
Free for one app. Pro for all of them.
Every feature in both. Pay once, get updates forever.
Pro
$9.99 one-time
Up to 5 Macs
- Unlimited apps
- Every feature
- Lifetime updates
Secure checkout by Lemon Squeezy · Prices in USD, tax added at checkout
Frequently asked questions
The app
How is Homeport different from Overmind or tmux?
Overmind and tmux run your processes in a terminal. Homeport is a Mac app that groups every service under its project, checks that each one is healthy, tells you when one crashes, and gives your apps local HTTPS domains. It runs the same commands you would type.
Does it work with Docker?
Yes. A service's command can be anything you'd run in a terminal, including docker compose up. Homeport starts, stops and watches it like any other service.
Which Macs does it run on?
Homeport needs macOS 26 or later.
Will it slow my Mac down?
Homeport itself stays in the background and samples CPU and memory every 2 seconds, only while services are running. Your services use the same resources they would in a terminal.
How does it run commands safely?
Before Homeport runs anything, it shows you the commands in a project's config and asks you to approve them. If the config changes, it asks again before running the new version.
Where does the config live?
In a homeport.yaml file in your project, so you can commit it, with personal overrides in homeport.local.yaml. Or Homeport can keep the config for you, without any file in your repo.
What does the assistant send?
Your question and the context you tick in Review what will be sent: status, config, health results and recent logs (up to 200 lines per service). Environment values in your config are always hidden, Homeport doesn't send your .env files, and values from them are masked in logs. Masking has limits, listed on the privacy page. It uses your own Anthropic API key and sends nothing until you click Send. The privacy page lists exactly what's included.
Buying
What's free?
Everything, for one app. The free version has every feature; Pro removes the one-app limit.
How do I activate Pro?
After you buy, you get a license key by email. Paste it into Homeport ▸ Settings ▸ License.
How many Macs can I use it on?
One license works on up to 5 Macs. You can move it by deactivating an old Mac in Settings ▸ License.
Do I pay again for updates?
No. Pro is a one-time purchase and includes every future update.