Usage / request volume
Plans are capped by monthly requests through the gateway. Moving from Minimum to Pro to Founding 100 mainly changes how many requests you can send, not which features you get.
Pricing
Start small, scale when needed, and secure prompts before sensitive data reaches GPT, Claude and other models.
BYOK · Privacy-first · Zero raw prompt retention
Plans
For solo builders and small AI projects.
For production workloads and growing teams.
Early supporter pricing for the first 100 customers during beta. Equivalent access to the Pro plan.
Early supporter pricing for teams helping shape Privian during beta. Fair-use limits apply. Limited to the first 100 customers. See Founding 100 terms.
For organizations with custom requirements.
The same core platform is included in every plan. Plans differ by monthly request volume and support level.
LLM provider usage costs (OpenAI, Anthropic and others) are billed directly by your provider through BYOK. Privian only charges for the gateway and security layer.
How pricing works
The core gateway, PII masking and prompt security are included on every plan. What actually changes the bill is usage, configuration and how far along you are toward enterprise deployment.
Plans are capped by monthly requests through the gateway. Moving from Minimum to Pro to Founding 100 mainly changes how many requests you can send, not which features you get.
Privian is bring-your-own-key: you connect your own OpenAI, Anthropic or other provider account. Provider token usage is billed by the provider directly, on your account, separate from your Privian plan.
Support level scales with tier — email support on Minimum, priority support from Pro upward. See the plan comparison for the exact breakdown of what each tier includes.
Custom requirements — security review, procurement, dedicated onboarding — move a team to Enterprise, which is scoped individually rather than priced as a fixed self-serve tier.
See how the gateway itself works on the LLM Gateway page, and what masking covers on the PII Masking page.
Fit
Minimum
Solo builders and small AI projects that need PII masking and prompt security in place from day one, without committing to a larger contract.
Pro / Founding 100
Production workloads and growing teams that need higher request volume and priority support, with Founding 100 adding grandfathered pricing for early supporters during beta.
Enterprise
Organizations with custom requirements — security review, procurement, roadmap discussions and priority onboarding — that need a scoped, individually negotiated setup.
Compare
| Feature | Minimum | Pro | Founding 100 | Enterprise |
|---|---|---|---|---|
| Requests / month | 50k | 250k | 250k | Custom |
| PII masking | Yes | Yes | Yes | Yes |
| Prompt security | Yes | Yes | Yes | Yes |
| BYOK | Yes | Yes | Yes | Yes |
| Supported entity masking | Yes | Yes | Yes | Yes |
| Email support | Yes | Yes | Yes | Yes |
| Priority support | Yes | Yes | Yes | |
| Priority beta feedback | Yes | Yes | ||
| Grandfathered pricing | Yes | Custom | ||
| Custom onboarding | Yes |
Alternatives
These are the operational tradeoffs between the common approaches teams consider — not a cost comparison.
Calling OpenAI, Anthropic or another provider directly is the fastest way to prototype. It means your team owns masking, prompt security and provider-switching logic yourself, with no shared privacy layer in front of the model.
Running your own gateway in your infrastructure gives full control over the request path, but your team is responsible for building and maintaining masking, routing and observability, and for keeping the deployment current.
An open-source gateway gives visibility into the code and avoids vendor lock-in, but typically requires your team to operate it, extend privacy features like masking, and handle updates and support directly.
A managed gateway like Privian provides PII masking, prompt security and BYOK provider routing as a maintained service, so your team integrates once instead of building and operating that layer.
Compare providers and gateway options on Supported Models and Compare.
Enterprise path
If your team is heading toward a security review, procurement process or enterprise deployment, these resources cover what reviewers typically ask for.
What enterprise deployment of Privian looks like end to end.
Architecture, data handling, retention and subprocessor details in one place.
A packaged set of trust assets for procurement and security teams.
Practical guidance for teams preparing their AI stack for larger customers.
FAQ
FAQ
Transparency
Privian is evolving in public with implementation-grounded documentation, transparent limitations and privacy-first defaults.
You bring your own OpenAI, Anthropic or other provider keys. Privian never owns provider billing or quotas.
Prompts and rehydrated responses are not persisted. Observability is built from counters and latencies.
Supported entity types are listed in the docs so you can verify coverage before integrating.
What's not yet supported is published on the Updates page — no compliance theater.
Architecture, data handling and the request lifecycle are documented openly.
Masking is on by default. The model only ever sees the masked prompt.
See our architecture, security and updates pages.
Start with Minimum, or join the Founding 100 to lock in early supporter pricing.
Enterprise review resources
The Trust & Security Review Center collects everything a procurement or security reviewer typically asks: data path, retention, BYOK, subprocessors and scope. The Privian Blueprint packages the same content as a single shareable PDF.