QUANTLIX BOUNDARY PRICING
Pricing for prompt protection that scales with your rollout
Start with Boundary to protect prompts before they reach the model, then expand into broader team usage and advanced control needs.
Quantlix Boundary is the product entry point into Quantlix, The AI Runtime Control Plane.
Starter
Best for first-time usersStart with guided prompt protection
Protect AI prompts before they reach the model on supported flows.
- 1 workspace
- 1 protected flow
- 1 seat
- 500 protected runs per month
- 7 days trace retention
- preset protection packs
- prompt test console
- visible policy outcomes
- basic trace visibility
Team
For teams using Boundary regularly
Expand from individual testing to repeatable team usage.
- 3 workspaces
- 3 protected flows
- 5 seats
- 10,000 protected runs per month
- 30 days trace retention
- preset protection packs
- prompt test console
- visible policy outcomes
- expanded trace visibility
- shared team access
- light rollout support
From $499/month
Enterprise
For broader rollout and advanced control needs
Use Boundary as part of a larger production AI control strategy.
- custom workspaces
- custom protected flows
- custom seats
- custom run volume
- custom retention
- advanced policy coverage
- broader deployment support
- implementation support
- custom rollout guidance
Custom pricing
Try it first in the public sandbox: /boundary/sandbox
All plans include access to Quantlix Boundary. As your usage grows, Boundary can expand into broader Quantlix capabilities across runtime control, observability, and evaluation.
Or call it from your code
curl -X POST "https://api.quantlix.ai//run" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"deployment_id":"DEPLOYMENT_ID","input":{"prompt":"Summarize this support ticket in 3 bullet points."}}'Send a prompt to POST /run; policy evaluates before model execution, then outcome and trace metadata are returned.
Compare plans
| Capability | Starter | Team | Enterprise |
|---|---|---|---|
| Workspaces | 1 | 3 | Custom |
| Protected flows | 1 | 3 | Custom |
| Seats | 1 | 5 | Custom |
| Protected runs / month | 500 | 10,000 | Custom |
| Trace retention | 7 days | 30 days | Custom |
| Preset protection packs | Yes | Yes | Yes |
| Prompt test console | Yes | Yes | Yes |
| Visible policy outcomes | Yes | Yes | Yes |
| Trace visibility | Basic | Expanded | Advanced |
| Shared team access | No | Yes | Yes |
| Light rollout support | No | Yes | Yes |
| Advanced policy coverage | No | Limited | Yes |
| Broader deployment support | No | Limited | Yes |
| Implementation support | No | Light | Yes |
Choose the plan that fits your stage
Starter
Best for trying Boundary, validating prompt protection, and getting to your first protected prompt quickly.
Team
Best for teams that want repeatable usage, shared access, and more operational headroom.
Enterprise
Best for broader rollout, advanced controls, and deeper implementation support.
Start with prebuilt policy packs
Every plan starts with Boundary’s core prompt-protection experience, including preset packs for common use cases.
Pack availability and advanced configuration options may vary by plan.
Deploy the way your team needs
- EU owned & hosted
- Self-host or managed
- Signed audit exports (HMAC hash chain, when signing is configured)
- GDPR data subject rights (export & erase)
- MFA, OIDC SSO, scoped API keys
- Enforcement traces and request-level audit
Self-hosted deployments keep raw source data inside your network boundary.
FAQ
What counts as a protected flow?
A protected flow is one configured AI request path protected by Boundary.
Can I start self-serve?
Yes. Starter is designed to help teams get to a first protected prompt quickly.
When should I choose Team?
Choose Team when you need more usage, more shared access, and more operational headroom for regular use.
When should I talk to sales?
Talk to sales when you need broader rollout, advanced policy coverage, or implementation support.
Does Boundary replace the rest of Quantlix?
Boundary is the product entry point into Quantlix. As your usage grows, you can expand into broader runtime control capabilities.
Start with Boundary today
Protect prompts before they reach the model, then grow into broader runtime control as your production AI usage expands.