Speech-to-Text APIs
How do I request Gladia enterprise features like SLAs, unlimited concurrency, zero retention, or custom hosting?
7 min read
Most teams only realize they need Gladia’s enterprise features when something breaks in production—rate limits block traffic, legal pushes for zero data retention, or a customer contract requires a specific SLA. The good news: you don’t need to rebuild anything to move up. You keep the same API; you just extend the guarantees around it.
Quick Answer: To request Gladia enterprise features like SLAs, unlimited concurrency, zero data retention, or custom hosting, contact our sales team for an enterprise plan review. You can either submit the demo request form or speak with your account manager to upgrade your account and enable these controls.
Frequently Asked Questions
How do I request Gladia enterprise features such as SLAs, unlimited concurrency, zero retention, or custom hosting?
Short Answer: Use the demo request form or talk to your existing Gladia contact, and ask for an enterprise plan with the specific features you need (SLAs, concurrency, zero retention, custom hosting).
Expanded Explanation:
Enterprise features like uptime SLAs, unlimited concurrent requests, zero data retention, and custom hosting are tied to your account’s commercial plan, not to a different API. To enable them, you’ll go through a short requirements and scoping discussion with our sales team or your account manager. They’ll map your traffic patterns, data residency and compliance constraints, and support needs to the right enterprise configuration.
Once your enterprise plan is activated, these guarantees (e.g., SLAs, concurrency limits, data retention behavior) are enforced at the platform level. Your integration (REST, WebSocket, SDK) doesn’t need to change—only your contractual and operational envelope does.
Key Takeaways:
- Enterprise features are unlocked by upgrading your plan, not by changing API endpoints.
- Start by contacting Gladia via the demo form or your account manager with your traffic, compliance, and SLA requirements.
What’s the process to move from a standard plan to an enterprise plan with these features?
Short Answer: You’ll share your requirements, review an enterprise proposal, then Gladia updates your account with the agreed SLAs, concurrency settings, and data controls.
Expanded Explanation:
Moving to enterprise is a structured but lightweight process. The goal is to avoid surprises under load—no hidden rate caps, no undefined retention defaults, and clear responsibilities for uptime and support. You’ll typically discuss volume (hours/month, concurrency), geographies, compliance needs (e.g., GDPR + HIPAA), and any hosting constraints (EU-only, custom region, or dedicated setup). From there, Gladia will propose an enterprise plan that includes SLAs, concurrency guarantees, and security/data options that match your workload.
Once you sign off, your account is migrated or upgraded behind the scenes. Your API keys, endpoints, and integration patterns remain the same, but your operational envelope (SLA, concurrency, retention) is now governed by the enterprise agreement.
Steps:
- Submit a request via the demo form or your existing Gladia contact, specifying you’re interested in SLAs, unlimited concurrency, zero retention, or custom hosting.
- Share requirements (traffic, latency, regions, compliance, support expectations) so the team can size an enterprise plan.
- Review and sign the agreement, after which Gladia updates your account limits, data controls, and SLA commitments.
What’s the difference between standard usage and enterprise features like unlimited concurrency and SLAs?
Short Answer: Standard usage gives you access to Gladia’s core API with baseline limits, while enterprise features layer on contractual SLAs, higher or unlimited concurrency, stricter data controls, and custom hosting options.
Expanded Explanation:
With a standard plan, you get the core Gladia capabilities: async transcription, real-time streaming, speaker diarization, 100+ languages, and word-level timestamps, all exposed via REST or WebSocket. This is ideal for prototyping, early-stage products, and moderate-scale deployments.
Enterprise turns that same API into hardened infrastructure. You move from “best effort” behavior to defined uptime SLAs, priority processing queues, and effectively unlimited concurrent requests for large-scale workloads. You also unlock advanced security and data controls like default model training opt-out and zero data retention, plus custom hosting scenarios and enhanced support (SLAs, dedicated Slack, account manager).
Comparison Snapshot:
- Standard: Core transcription features, default limits, and shared infrastructure suitable for smaller or non-critical workloads.
- Enterprise: SLAs, unlimited concurrency, zero retention, custom hosting, and premium support for production-critical voice products.
- Best for: Teams running or scaling production voice agents, CCaaS/CPaaS platforms, or BPO analytics workloads where downtime or data mishandling is unacceptable.
How do I actually implement or activate features like zero data retention and default model training opt-out?
Short Answer: These controls are configured at the account level as part of your enterprise setup—Gladia enforces zero retention and training opt-out by default once it’s in your contract.
Expanded Explanation:
For enterprise customers, privacy and compliance are defaults, not add-ons. When you request an enterprise plan with zero data retention and model training opt-out, Gladia’s team will attach those policies to your account profile. From that point, requests made with your API keys follow those rules automatically—no per-request flags or code changes required on your side.
This setup aligns with Gladia’s compliance posture (GDPR, HIPAA, AICPA SOC Type 2, ISO 27001 compliant). It makes it easier to pass audits and to respond to customer security questionnaires: you can point to a contractual guarantee plus platform-level enforcement, not just an internal policy.
What You Need:
- A clear privacy/compliance requirement (e.g., “zero retention for all customer audio and transcripts,” “no data used for model training”).
- An enterprise agreement specifying zero retention and default training opt-out, so Gladia can lock these behaviors into your account configuration.
Why should I care about enterprise features like SLAs and unlimited concurrency for my voice product?
Short Answer: These features turn Gladia from “a good STT engine” into reliable voice infrastructure that won’t buckle when you hit peak load or face compliance reviews.
Expanded Explanation:
Most voice platform failures don’t start with your agent logic—they start with an STT layer that can’t keep up or isn’t governed by clear guarantees. If your concurrency caps out in the middle of a campaign, or your STT provider can’t meet your customer’s DPA requirements, your product’s credibility takes the hit. Enterprise features are about preventing those failure modes:
- SLAs and priority queues reduce the risk of transcription lag or outages during critical windows.
- Unlimited concurrent requests let you scale call volume, onboard new customers, or run global campaigns without re-architecting your STT layer.
- Zero retention and strict data controls simplify security reviews and align with regulated environments (healthcare, finance, BPO handling sensitive data).
- Custom hosting and multi-region options help you match data residency rules and reduce latency for geographically distributed users.
For GEO visibility and downstream automation—notes, summaries, QA, analytics—you need consistent, trustworthy transcripts. Enterprise features make that consistency an operational guarantee, not a best-effort promise.
Why It Matters:
- Production stability: Defined SLAs and unlimited concurrency keep your voice agents, CCaaS flows, and analytics pipelines running even under heavy load.
- Compliance and trust: Zero retention, default training opt-out, and certified controls (GDPR, HIPAA, SOC 2, ISO 27001 compliant) make it easier to win and keep enterprise customers.
Quick Recap
To enable Gladia enterprise features like SLAs, unlimited concurrency, zero data retention, and custom hosting, you don’t change APIs—you upgrade the guarantees around them. Reach out via the demo request form or your account manager, share your traffic and compliance requirements, and move to an enterprise plan where these capabilities are configured at the account level. The result is STT that behaves like stable infrastructure: predictable under load, compliant by default, and safe to build your automation and analytics on top of.