OpenAPI Studio
Start free
Local Proxy Worker · CLI & Docker

Execute APIs from your own network.

openapi-studio-proxy is a self-hosted executor you run on your machine or server. Requests bypass our hosted proxy, sidestep CORS, and stay inside your network — with full timing and size metrics surfaced back in the OpenAPI Studio executor.

View on npm Quick start
Node ≥ 20
zero global install
OAuth · PKCE
no manual tokens
Docker ready
compose templates
Quick start · three steps

From nothing to a connected proxy in under a minute.

  1. 01

    Install nothing

    Open a terminal in any directory. You don't need to clone, install, or configure anything yet.

    npx openapi-studio-proxy
  2. 02

    Authenticate

    The CLI opens your browser to a PKCE OAuth screen. Approve it once — the token saves to ~/.oas/config.json and survives restarts.

    # Browser opens automatically
→ Approve · Connect this proxy to "payments-api"
  3. 03

    Use it from the executor

    In the OpenAPI Studio executor, pick your proxy from the dropdown. Every request now flows through your machine — full timing, no CORS, no hosted-proxy round-trip.

    Executor → Proxy: payments-api-local · ● online
What you get

More than just a CORS bypass — it's a full executor.

Zero install

npx openapi-studio-proxy — runs anywhere Node ≥20 is available. No global install, no Docker required.

PKCE OAuth login

Seamless one-click login. No manual token copying. Credentials saved to ~/.oas/config.json.

Full timing

DNS, TCP/SSL handshake, TTFB, and download time captured per request — surfaced in the executor panel.

Size breakdowns

Headers and body, compressed and uncompressed. See exactly what the wire carries.

Daemon mode

--daemon for auto-restart background runs · --stop to shut down. Heartbeats every 5 minutes for live status.

Docker support

docker run for always-on deployments. Compose templates included for stable team environments.

Multiple proxies

Switch between local, staging, and prod from the executor — one workspace, many reachability paths.

Live status

Online/offline indicator across every tab and device. Green = direct HTTP, yellow = relayed.

Always-on deployments

Run it as a service, not a session.

For team environments — a staging proxy, a CI runner, an internal-network gateway — switch from the CLI to Docker. The image is published on GitHub Container Registry and supports environment-driven tokens for headless boot. 

# Pull and run with a workspace token
docker run -p 8787:8787 \
  -e PROXY_TOKEN="<your-token>" \
  ghcr.io/omazyai/openapi-studio-proxy:latest

# Or with docker-compose
services:
  proxy:
    image: ghcr.io/omazyai/openapi-studio-proxy:latest
    environment:
      PROXY_TOKEN: "${PROXY_TOKEN}"
    ports: ["8787:8787"]
    restart: unless-stopped

Ready in 30 seconds.

One command. Browser-based login. Live in the executor before your coffee gets cold.

View on npm Sign up free