Pricing
The full pricing matrix lives on the landing page . This page is the developer-facing summary.
The model in one sentence
You bring your own provider key. You pay the provider directly for tokens. You pay us a flat tier for the gateway. No token markup.
Tiers
| Tier | Cost | Best for |
|---|---|---|
| Local | Free, forever | Single developer, sensitive workloads, anyone who wants to own the data. |
| Pro | $20 / month | Solo devs and small projects, 1M included tokens/month. |
| Team | $99 / month | Teams; shared keys, per-user quotas, 10M included tokens/month. |
| Bring Your Own Cloud | Custom | Dedicated deployment in your own cloud account. Your IAM, your data, your controls. |
| Enterprise | Custom | SLA, on-prem-or-VPC deployment, custom modules. |
See full feature breakdown at prxy.monster/#pricing .
Why no token markup?
Token markup is a tax that compounds with your scale. We charge a flat tier so the math is simple — if you want to move 10× the requests through the gateway tomorrow, your prxy.monster bill doesn’t 10× too.
You pay your provider for the tokens you use. We get out of the way.
Local mode is genuinely free
Not “free trial”. Not “free with strings”. Genuinely free.
The local edition is the same gateway, with the same modules. The only thing it doesn’t have is managed billing, shared cloud storage, and cross-device sync — and you don’t pay for what isn’t there.
Local mode is not “ad-supported”, “telemetry-supported”, or “data-mining-supported” either. The container does not phone home. See Local mode → Privacy for the audit checklist.
What about the modules in v1.1?
The new modules in v1.1 (router, rehydrator, compaction-bridge, prompt-optimizer, tool-cache, guardrails) ship at no additional cost on every paid tier and in local mode. Official built-in modules are included.