License
BYOK package selection, billing path, and self-host deployment access.
Choose the path that matches your deployment stage
Start with the evaluation if you need deployment-fit proof first. If you already know your footprint, move directly to a production BYOK pack. Use custom deployment only when your requirements do not fit the standard package sizes.
Step 1 · Start with a paid evaluation
BYOK Evaluation
Designed for teams that want to validate deployment fit, provider setup, and operational workflow before moving to a production BYOK license.
- Self-hosted OWL evaluation deployment
- Customer-controlled provider configuration
- Evaluation JWT with fixed term
- License verification endpoint
- Core transcription and translation access
- Single deployment / evaluation footprint
- Evaluation support (business-hours / limited scope)
Production deployment is separate. If you proceed, we issue a new production BYOK license and provide access to the production deployment package.
How BYOK pricing works
- Evaluation first, if needed: use the paid BYOK evaluation to validate deployment fit before moving to a production package.
- Docker-based self-host deployment: production BYOK packages are priced around the supported deployment footprint, seat count, support level, and node allowance for the self-hosted Docker package.
- Additional seats: standard production packs bundle seat counts in fixed package sizes. Custom deployments are quoted separately using the same commercial model.
- Artifact family: package entitlements also map to a runtime artifact family and manifest profile, keeping commercial and delivery logic aligned.
Start with a paid evaluation or move directly to a production BYOK package. If your footprint does not fit neatly, choose Request Invoice or the Custom deployment option and we will size a quote aligned to the same package logic.
Production BYOK packs (annual, prepaid)
Pick the packaged production rail that matches your expected footprint. Starter and Pro can be self-purchased. Enterprise and custom stay invoice/sales-led so larger deployments can be handled carefully.
- Priority 8×5: +12%
- Premium 8×5: +18%
- 24×7 / 1h P1: +25%
BYOK Starter 25
Best for smaller controlled deployments that want a clean entry point into self-hosted OWL with fixed footprint and predictable commercial scope.
- Self-hosted OWL deployment
- Customer-controlled provider configuration
- License JWT with domain binding
- License verification endpoint
- Core transcription and translation access
- Single-domain deployment model
- Updates while active
- Basic audit trail
BYOK Pro 100
Best for teams moving beyond the entry package and needing a larger deployment footprint, more clusters, and mid-tier operational capability.
- Self-hosted OWL deployment
- Customer-controlled provider configuration
- License JWT with domain binding
- License verification endpoint
- Core transcription and translation access
- Multi-domain deployment model
- Webhook support
- Glossary support
- Updates while active
- Basic audit trail
BYOK Enterprise 250
Best for larger organizations that need the broadest packaged footprint, enterprise-tier controls, and onboarding-assisted higher-tier deployment posture.
- Self-hosted OWL deployment
- Customer-controlled provider configuration
- License JWT with domain binding
- License verification endpoint
- Core transcription and translation access
- Multi-domain deployment model
- Domain pinning capable
- Webhook support
- Glossary support
- SSO / SAML capable
- Advanced audit controls
- SIEM export capable
- Custom branding capable
- Updates while active
Custom deployment
Use this for footprints that do not fit neatly into Starter, Pro, or Enterprise. This is the right path for larger seat counts, stricter compliance requirements, hybrid environments, or unusual network/security constraints.
- 250+ seats or multiple regions
- Strict compliance or data residency requirements
- Hybrid or special network / security constraints
- Seat: named user on that deployment; enforced by JWT claims and app checks.
- Cluster: one logical deployment, such as production. Pro and Enterprise include additional clusters.
- Server limit: max nodes per cluster that the license permits.