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

If you want your locally-forged patterns and caches available in cloud:

# Export from SQLite (from inside the container)
docker exec prxy /usr/bin/sqlite3 /data/prxy.db ".dump patterns" > patterns.sql
docker exec prxy /usr/bin/sqlite3 /data/prxy.db ".dump semantic_cache" > cache.sql
 
# Send to cloud import endpoint (v1.1)
curl -X POST https://api.prxy.monster/v1/import \
  -H "Authorization: Bearer prxy_live_xxx" \
  -H "Content-Type: application/sql" \
  --data-binary @patterns.sql

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

# v1.1 endpoint
curl https://api.prxy.monster/v1/export?type=patterns \
  -H "Authorization: Bearer prxy_live_xxx" \
  -o patterns.sql
 
# Import into local SQLite
docker exec -i prxy /usr/bin/sqlite3 /data/prxy.db < patterns.sql

Step 4. (Optional) Cancel cloud subscription

app.prxy.monster/billing  → portal → cancel.

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