PorticoMany services, one front door

Start your dev servers, APIs and containers, and reach all of them through one port.

Get Started

GitHub

Runs Your Services

Shell commands, container images and compose files, with their output in one stream and a clean stop on Ctrl-C.

One Origin

/ goes to the frontend, /api to the API. No CORS, no per-port auth. Websockets and server-sent events pass straight through.

Dev-Server Friendly

Upstreams see Host localhost:<port>, so Vite and webpack host checks pass; X-Forwarded-* headers say where the app really lives.

Knows What's Up

JSON 503s for services that are down, crashed (with their last lines) or still starting per Docker's healthcheck.

Quick to Set Up

portico init writes the config, and flags cover the rest.

Production Parity

Swap the builtin proxy for nginx, generated from the same routes, when you need to match production.

Why Portico

A web app in development is rarely one process: a frontend dev server, an API, maybe a config server and a websocket service, each on its own port. That works on a laptop. It breaks behind a gateway that gives every port its own origin (Cloud Workstations, Codespaces, a remote dev box): the browser sees cross-origin calls, CORS and auth redirects get in the way, and localhost points at the wrong machine.

Portico starts those services and puts one port in front of all of them. The browser only talks to Portico, and Portico routes each path to the right service.

portico init    # finds compose files and package.json dev scripts
portico up      # starts everything on http://localhost:4400