Upgrading

Local mode and cloud mode use the same database schema. You can move between them. v1.1 will ship a one-command migrator; v1 needs a couple of manual steps.

When to upgrade local → cloud

Consider switching when:

• You want sync across devices (same patterns / cache on your laptop and your server).
• You want a hosted dashboard.
• Your team needs shared keys and per-user quotas.
• Your workload outgrows a single container (multi-region, autoscaling).

When to downgrade cloud → local

Consider switching when:

• A regulatory or contractual requirement forbids hosted services.
• The workload is one developer with no need for sync.
• You want to lock down outbound traffic to your provider only.

Both directions work. Neither is destructive — your data stays put unless you explicitly migrate it.

Local → Cloud (v1)

Step 1. Sign up

prxy.monster  → mint a key.

Step 2. Update env

- ANTHROPIC_BASE_URL=http://localhost:3099
+ ANTHROPIC_BASE_URL=https://api.prxy.monster
- ANTHROPIC_API_KEY=prxy_local_anything
+ ANTHROPIC_API_KEY=prxy_live_xxxxxxxxxxxx

That’s the minimum. From this point forward your requests run through cloud.

Step 3. (Optional) Migrate patterns + cache

Cloud import/export ships in v1.1. In v1, your locally-forged patterns stay local and the cloud patterns module starts fresh from new traffic.

Step 4. Decommission local container

docker stop prxy && docker rm prxy
# Keep ~/.prxy/ around as a backup until you're confident the cloud is working.

Cloud → Local (v1)

Step 1. Run the local container

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

Step 2. Update env

- ANTHROPIC_BASE_URL=https://api.prxy.monster
+ ANTHROPIC_BASE_URL=http://localhost:3099
- ANTHROPIC_API_KEY=prxy_live_xxx
+ ANTHROPIC_API_KEY=prxy_local_anything

Step 3. (Optional) Export patterns from cloud

Cloud export ships in v1.1. In v1, start local mode fresh and let it learn from new traffic.

Step 4. (Optional) Cancel cloud subscription

Open the Stripe customer portal from your billing email, or contact [email protected] and we’ll send a fresh portal link.

Your cloud data is preserved for 30 days after cancellation. After that, it’s permanently deleted.

Hybrid mode (planned, v1.2)

Future: run local for the latency-sensitive part of your stack, with periodic sync of patterns + caches to cloud for cross-device availability. Tracked in the roadmap.

See also

• Quick start: cloud
• Quick start: local
• Pricing