Speech-to-Text APIs
How do I request Gladia enterprise features like SLAs, unlimited concurrency, zero retention, or custom hosting?
6 min read
Most teams only realize they need enterprise features when things start breaking: note-takers missing half the call, CRM syncs failing, or a voice agent timing out because your STT vendor throttled concurrency. That’s exactly where Gladia’s enterprise options—SLAs, unlimited concurrent requests, zero data retention, and custom hosting—come in, and the process to request them is intentionally straightforward.
Quick Answer: To request Gladia enterprise features like SLAs, unlimited concurrency, zero retention, or custom hosting, you’ll need to talk directly with our sales team via the demo request form or your existing account contact. These options are part of our Enterprise tier and are activated on a per-account basis after scoping your traffic, compliance, and hosting needs.
Frequently Asked Questions
How do I request SLAs, unlimited concurrency, zero data retention, or custom hosting from Gladia?
Short Answer: Use the Gladia demo request form or contact sales to discuss your requirements; these features are bundled into our Enterprise offering and enabled once your plan is upgraded.
Expanded Explanation:
SLAs, unlimited concurrent requests, default training opt-out, zero data retention, and custom hosting are not toggle-on UI settings in the self-serve dashboard. They’re part of an Enterprise-grade contract because they affect infrastructure allocation, compliance posture, and support commitments.
To get them, you start by sharing your expected usage (traffic patterns, regions, and workloads) with the Gladia team. From there, we size the deployment, confirm your security and compliance requirements (GDPR, HIPAA, SOC 2, ISO 27001 constraints), and move you onto an Enterprise plan that explicitly includes the features you need in the contract.
Key Takeaways:
- Enterprise features are provisioned via an Enterprise plan, not enabled by default on self-serve tiers.
- The path is simple: reach out through the demo request form or to sales, scope requirements, then finalize an Enterprise contract that includes SLAs, concurrency, retention, and hosting terms.
What’s the process to upgrade my Gladia account to Enterprise for these features?
Short Answer: Submit a demo request or contact your account manager, then work through a short scoping and contract phase where concurrency, SLAs, retention, and hosting options are defined and activated.
Expanded Explanation:
Upgrading to Enterprise is about aligning Gladia’s infrastructure and guarantees with your production workload, not just flipping a billing switch. We’ll look at your expected call volume, concurrency spikes, regions (US/EU or multi-region), and any specific compliance rules around data residency and retention.
Once we understand the load and risk profile, we’ll propose an Enterprise plan that includes unlimited concurrent requests, SLAs, a zero-retention posture if required, and, where needed, custom hosting. After contract signature, your account configuration is updated, and these guarantees become part of your operational baseline.
Steps:
- Submit a request: Go to https://www.gladia.io/demo-request and share your use case, expected volumes, and required enterprise features (SLAs, unlimited concurrency, zero retention, custom hosting).
- Scope and sizing call: Meet with Gladia’s team to review concurrency needs, data residency/compliance requirements, and voice traffic patterns (e.g., telephony-heavy, SIP/8kHz, multilingual).
- Contract and activation: Finalize an Enterprise agreement that specifies SLAs, concurrency guarantees, data retention settings, and any hosting customizations; Gladia then configures your account accordingly.
What’s the difference between standard plans and Enterprise with these features?
Short Answer: Standard plans give you core transcription capabilities; Enterprise adds operational guarantees—SLAs, unlimited concurrency, zero retention, and custom hosting—for teams running mission-critical, high-volume voice workloads.
Expanded Explanation:
On a standard plan, you get the core API surface: async and real-time transcription, diarization, 100+ languages, and word-level timestamps, plus reliable performance and transparent pricing. That’s often enough for early-stage products and smaller workloads.
Enterprise is built for BPOs, CCaaS platforms, and voice AI providers where downtime or throttling directly impacts revenue or SLAs with your own customers. Here, Gladia layers on explicit uptime SLAs, priority queues, unlimited concurrent requests, stricter data controls (default training opt-out and zero retention), and custom hosting patterns—often in specific regions—to match your compliance and scaling requirements.
Comparison Snapshot:
- Standard Plans: Core transcription (async + real-time), diarization, 100+ languages, word-level timestamps, and solid performance for typical workloads.
- Enterprise Plan: Everything in growth/standard plus SLAs, unlimited concurrency, default training opt-out, zero data retention, premium support, and custom hosting.
- Best for: Teams where STT is production-critical infrastructure—contact centers, voice agents, and platforms that can’t tolerate rate limits, data ambiguity, or unclear uptime guarantees.
How long does it take to get SLAs, unlimited concurrency, zero retention, or custom hosting activated?
Short Answer: Expect days to a few weeks, depending on how complex your compliance and hosting needs are; straightforward cases can move faster once requirements and contracts are aligned.
Expanded Explanation:
For most teams, the timing depends less on Gladia’s tech and more on how quickly you can finalize requirements and legal review. Simple setups—single region, clear concurrency targets, standard zero-retention posture—can be scoped and activated in a short cycle.
More complex deployments—multi-region hosting, strict data residency (e.g., regulated industries), or bespoke network setups—may require additional security and infrastructure review. In all cases, Gladia’s Enterprise and support teams (US & EU-based) walk you through the deployment and testing so your rollout doesn’t stall.
What You Need:
- Clear volume and concurrency estimates: Peak calls, concurrency ceilings, and latency expectations for both async and streaming.
- Compliance and hosting constraints: Required regions (US/EU/multi-region), retention rules, certifications you rely on, and any custom hosting or network requirements.
Why should I move to Enterprise for SLAs, unlimited concurrency, zero retention, or custom hosting?
Short Answer: Because once your product depends on Gladia for real-time decisions, you need contractual guarantees on uptime, concurrency, and data handling—not just “best effort” performance.
Expanded Explanation:
Most voice platform failures start with STT that isn’t architected for production: unexpected throttling during call spikes, no guarantees around uptime, or data policies that don’t match your own compliance promises. When that happens, everything downstream—notes, summaries, CRM syncs, QA analytics, and agent assist—begins to drift or outright fail.
An Enterprise plan with SLAs, unlimited concurrency, zero retention, and custom hosting turns Gladia into a stable backbone for your voice stack. You get predictable scaling under load, transparent uptime guarantees, and auditable data controls. That lets you safely build higher-order automation (QA analytics, coaching, AI agents) without worrying that a traffic spike or policy gap will break your workflow.
Why It Matters:
- Production stability: Unlimited concurrency and SLAs ensure your contact center, BPO, or voice agent doesn’t buckle under peak loads or fail silently when volumes surge.
- Compliance and trust: Zero data retention, default model training opt-out, and custom hosting aligned with GDPR/HIPAA/SOC 2/ISO 27001 mean your transcription layer won’t undermine your security or privacy posture.
Quick Recap
To unlock Gladia’s enterprise features—SLAs, unlimited concurrent requests, zero data retention, and custom hosting—you need to move onto an Enterprise plan. That happens through a short scoping and contracting process with the Gladia team, where you define concurrency, compliance, and hosting needs. Once active, these features give you a stable, auditable STT backbone for high-volume, production-grade voice workloads.