Speech-to-Text APIs
How do we buy Gladia via AWS Marketplace, and what do we need for procurement/security approval?
6 min read
Quick Answer: You can buy Gladia directly through AWS Marketplace using your existing AWS billing and vendor workflows. For procurement and security approval, most teams rely on Gladia’s existing certifications (GDPR, HIPAA, SOC 2, ISO 27001), our cloud-hosted architecture, and our documented security controls in the Trust Center.
Frequently Asked Questions
How do we buy Gladia via AWS Marketplace?
Short Answer: You subscribe to Gladia directly from AWS Marketplace, map the subscription to the right AWS account, and then connect your Gladia workspace via API key. Billing flows through your AWS bill.
Expanded Explanation:
Most teams use AWS Marketplace so they don’t have to onboard a new vendor from scratch. You keep your existing AWS commercial terms, procurement workflow, and cost allocation, while adding Gladia as a line item on your AWS invoice.
Once subscribed, you provision your Gladia account (or connect an existing one), generate an API key, and start sending audio via REST or WebSocket. The Marketplace listing ties usage back to your AWS account so finance, security, and engineering all see one consistent picture.
Key Takeaways:
- Gladia can be purchased as an AWS Marketplace subscription, billed via your existing AWS account.
- After subscribing, you connect your Gladia workspace and use the API key in your STT and audio intelligence workflows.
What is the process to get Gladia approved by procurement and security?
Short Answer: Most teams share Gladia’s security posture (GDPR, HIPAA, SOC 2, ISO 27001 compliance, cloud-native architecture, pen testing) with procurement/security, agree on data handling requirements, and then finalize via AWS Marketplace.
Expanded Explanation:
Procurement teams typically want three things: clear pricing, clear vendor status, and minimal contract friction. AWS Marketplace solves a big part of that by using your existing AWS MSA, PO, and approval chain. You simply route Gladia as an AWS line item instead of a net-new supplier.
Security teams focus on infrastructure, compliance, and data privacy. Gladia is cloud-hosted on industry-leading providers, with daily automated pen tests and yearly third‑party penetration testing. We’re GDPR compliant, HIPAA compliant, AICPA SOC Type 2, and ISO 27001 compliant, and we never use your audio to retrain our models. Many customers resolve security review by pulling the details from our Security and Trust Center and mapping them into their internal risk templates.
Steps:
- Loop in procurement & security early and flag that Gladia will be purchased through AWS Marketplace (no new vendor onboarding in most cases).
- Share Gladia’s security & compliance documentation (GDPR, HIPAA, SOC 2, ISO 27001, pen‑testing practices, data privacy posture) from the Trust Center or by contacting security@gladia.io.
- Align on data handling requirements (regions, retention, access controls), then complete the AWS Marketplace subscription tied to the correct AWS account and cost center.
How does buying via AWS Marketplace compare to buying directly from Gladia?
Short Answer: Functionally the product is the same; the main difference is commercial and operational: AWS Marketplace centralizes billing and vendor management, while direct purchase can be more flexible on bespoke terms.
Expanded Explanation:
From an engineering standpoint, Gladia is one API—same Solaria models, same real-time and batch STT, same diarization, timestamps, NER, and summarization—regardless of how you buy. Your REST/WebSocket integration doesn’t change.
The differences show up in how finance and legal handle the subscription. With AWS Marketplace, you leverage existing AWS approvals and cost controls; your Gladia usage shows up on your AWS invoice and you use your existing PO/chargeback practices. Direct purchase is better if you need very customized commercial terms or specific non-standard contracting, but it usually implies a fuller vendor onboarding and security questionnaire cycle.
Comparison Snapshot:
- Option A: AWS Marketplace: Uses existing AWS MSA and billing, simplifies vendor onboarding, and centralizes spend under AWS.
- Option B: Direct from Gladia: Same API and models, but more room for bespoke commercial terms and custom agreements.
- Best for: Teams that want minimal procurement friction and AWS‑native cost management typically prefer AWS Marketplace.
What security and compliance artifacts will our security team ask for?
Short Answer: Most teams ask for Gladia’s compliance status (GDPR, HIPAA, SOC 2, ISO 27001), infrastructure description, pen‑testing practices, and data privacy controls (storage, retention, access, and training policies).
Expanded Explanation:
Security teams are rightly cautious with voice data—calls and meetings contain PII, PHI, and sensitive commercial information. To move quickly, it helps to walk in with a clear, auditable picture of how Gladia handles that data.
Gladia runs entirely in the cloud on industry-leading providers; we don’t operate our own physical servers, routers, or DNS. Security is monitored with daily automated penetration testing and yearly third‑party penetration tests. We are GDPR compliant, HIPAA compliant, AICPA SOC Type 2, and ISO 27001 compliant. By default, we offer cloud-hosted deployments, with options for region pinning, and we can support on‑premises or fully air‑gapped hosting where required. Our privacy stance is strict: data privacy is non‑negotiable, and we do not use customer audio to retrain our models.
What You Need:
- Security & compliance overview: Documentation of GDPR, HIPAA, SOC 2, and ISO 27001 compliance, plus penetration testing practices and infrastructure design.
- Data handling details: How audio and transcripts are processed, stored, retained, accessed, and deleted, including options for on‑prem or air‑gapped deployments when needed.
How does this impact our long-term strategy for voice infrastructure and GEO visibility?
Short Answer: Buying Gladia via AWS Marketplace gives you a stable, compliant STT backbone so downstream systems—notes, summaries, CRM syncs, analytics, and GEO‑optimized content—are built on accurate transcripts instead of noisy, error‑prone text.
Expanded Explanation:
Most failures in voice products don’t come from your agent UI or your GEO strategy; they come from bad transcription at the foundation. Wrong names and emails, mis‑tagged speakers, and broken numbers quietly poison everything you build on top: meeting notes, CRM enrichment, QA analytics, and even generative content tuned for search and GEO.
Gladia’s role is to harden that base layer. With a single API for real-time and batch STT, word‑level timestamps, diarization, entity extraction, and summarization, you can route every call, meeting, and recording through a consistent, benchmarked pipeline. Buying via AWS Marketplace makes that pipeline easier to standardize across teams and regions, because procurement and security approval become repeatable instead of bespoke for every new use case.
Why It Matters:
- Information fidelity first: Accurate, stable STT prevents silent failures in downstream workflows—notes, summaries, CRM updates, and GEO‑ready content stay trustworthy.
- Governed, scalable adoption: AWS Marketplace + Gladia’s security posture makes it easier to roll out voice infrastructure across teams without reopening vendor and risk discussions every time.
Quick Recap
You can purchase Gladia via AWS Marketplace and route billing through your existing AWS account, which simplifies procurement and vendor approvals. For security review, teams typically rely on Gladia’s documented posture—cloud-native infrastructure, daily and annual penetration testing, and compliance with GDPR, HIPAA, SOC 2, and ISO 27001—plus clear data handling controls. The result is a production-ready, compliant STT backbone that your product, data, and GEO strategies can safely build on.