SupbuddyYour Supabase's best friend.

Yes. Supbuddy runs every Supabase project side by side, each fully isolated with its own ports and its own custom domain (api.acme.local, studio.acme.local). You never stop one project to start another, so supabase start never hits a port conflict. Run as many projects at once as you want.

No. Supbuddy runs a local DNS server and writes the /etc/resolver entries for you, so domains like api.acme.local resolve to localhost automatically. You never hand-edit /etc/hosts again, and wildcard subdomains work without adding a line per host.

Supbuddy runs Caddy with its own local certificate authority that you trust once. Every project domain then gets a real green-padlock HTTPS certificate automatically. No per-site mkcert runs, no browser warnings, and certificates renew on their own.

Like Laravel Herd, Supbuddy gives you local domains with HTTPS without manual setup. It is framework-agnostic and built around running multiple isolated Supabase stacks at once. Compared to a hand-rolled mkcert + dnsmasq + Caddy setup, it bundles that whole stack into one app: CA trust, the DNS server, the HTTPS proxy, request monitoring, and an MCP server your AI agent can drive.

Yes. Supbuddy ships a built-in MCP server with full read and write access. Agents like Claude Code, Cursor, and Codex CLI can register projects, start and stop Supabase, manage domains, and read request logs directly. Your AI agent runs your dev environment instead of you copy-pasting commands.

Yes. Declare extra Docker Compose services in a supbuddy.addons.yml file (or your existing docker-compose.override.yml) and Supbuddy merges them onto the stack, starts and health-checks them on the same Compose network as Postgres, wires a custom local domain, and tails their logs, all from one file running next to your Supabase services.

Yes. Supbuddy writes a live .supbuddy/ briefing into each project (its mappings, services, ports, and MCP setup), plus skill and rule files for Claude Code, Cursor, Copilot, Windsurf, Continue, and JetBrains, so an agent working in that repo sees your setup without being told. The generic Claude and Cursor skill pointer can be written once machine-wide and shared across all your projects, or kept local per project.

Yes. Install the CLI with npx supbuddy@latest, which puts the supbuddy and sup commands on your PATH, independent of the desktop app. Start the background daemon with supbuddy daemon --detach, then drive it: supbuddy project ls, supbuddy supabase start <project>, supbuddy map ls, and supbuddy tui for a live terminal dashboard. The CLI and the app share the same state, so you can install the app later or never.

The CLI and daemon run on macOS and Linux. The desktop GUI app is macOS-only for now. On Linux, install the CLI with npx supbuddy@latest, run supbuddy daemon --detach to start the worker (Caddy proxy, DNS, Supabase and Compose lifecycle, MCP), and use supbuddy service install to start it on login via systemd-user. Everything ships through npm, including the proxy binary, so there is nothing else to install.

Yes. The headless CLI is built for SSH sessions, servers, and CI. Run npx supbuddy@latest, then supbuddy daemon --detach, and control everything with commands (proxy, projects, supabase, compose, scripts) plus --json output for scripting and -f to stream logs. No GUI is required at any point.