Quick start — Local

Run the full gateway in a single Docker container. SQLite for storage, no cloud, no telemetry, no signup.

Local mode is free forever. The same modules. The same API. Only difference: storage lives in a SQLite file on your machine instead of our cloud Postgres.

Run the container


docker run -d \
  --name prxy \
  -p 3099:3099 \
  -v ~/.prxy:/data \
  -e ANTHROPIC_API_KEY=sk-ant-xxx \
  prxymonster/local:latest

That’s it. The container is stateless — all data lives in the host volume at ~/.prxy/.

Point your app at it


export ANTHROPIC_BASE_URL=http://localhost:3099
export ANTHROPIC_API_KEY=prxy_local_anything

In local mode, the gateway accepts any token. Auth + tier + billing are bypassed because you already paid for your own infra by running it.

Make a call


curl http://localhost:3099/v1/messages \
  -H "Authorization: Bearer prxy_local_anything" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "claude-sonnet-4-6",
    "max_tokens": 256,
    "messages": [{"role": "user", "content": "hi"}]
  }'

Same wire shape as cloud. Same modules. Just runs on your box.

What’s stored where


~/.prxy/
├── prxy.db              ← SQLite. Patterns, cache, sessions, embeddings.
├── blob/                ← Local blob store (compressed conversation archives).
└── config.yaml          ← Optional pipeline config (overrides PRXY_PIPE).

That’s the whole thing. No phone-home. No telemetry. No background sync.

Set your provider keys

The gateway needs at least one provider configured. Pass any of:


-e ANTHROPIC_API_KEY=sk-ant-xxx
-e OPENAI_API_KEY=sk-xxx
-e GOOGLE_API_KEY=xxx
-e GROQ_API_KEY=gsk_xxx

Check what’s wired:


curl http://localhost:3099/health

Customize the pipeline

Two ways:

Env var


docker run -d \
  -p 3099:3099 \
  -v ~/.prxy:/data \
  -e ANTHROPIC_API_KEY=sk-ant-xxx \
  -e PRXY_PIPE='exact-cache,semantic-cache,patterns,ipc' \
  prxymonster/local:latest

Privacy hardening (airgap)

Add the airgap module to enforce zero outbound network calls except to your chosen provider:


-e PRXY_PIPE='airgap,ipc,patterns,semantic-cache'

The airgap module lives in v1.1 — but the principle (no telemetry from prxy.monster itself) applies today. See Local mode → Privacy.

Upgrade path

When the cloud features start to make sense (sync across devices, hosted dashboard, team sharing), you can upgrade without losing anything. See Local mode → Upgrading.

Next steps

Local mode docs — full container reference.
Pipeline customization — pick which modules run.
Modules — what each one does.