Enterprise

The audio intelligence layer, on your terms.

Bring your recordings under one searchable layer without handing them to a black box. Choose exactly the isolation your security team requires, from a locked-down shared tenant to a dedicated instance.

Get a quote See isolation tiers
audioscrape · isolationforced RLS
search › "fee waivers this quarter" · key: Acme workspace
Acme · support call[ 04:12 ]your workspace
"I'll waive the annual fee for this year, no problem."
private · your data · returned ✓
Contoso · support call[ 11:27 ]another tenant
"...we can waive the annual fee to keep the account this year..."
🔒 isolated · row-level security · never returned to your key

Isolation enforced in the database, not just the app.

Isolation, your way

Pick the boundary your data needs.

Every tier below carries the same product. What changes is where the wall sits, so a security review has a real answer, not a shrug.

Included

Workspace isolation

Shared infrastructure, hard logical isolation.

  • Row-level security forced at the database, not just the app
  • Per-workspace API keys & quotas
  • One tenant's audio is never returned in another's query
Contract

Isolated environments

Separate Dev / Test / Prod, one contract.

  • Independent environments, keys, quotas & audit trails
  • Per-environment overage & usage reporting
  • SLA, DPA, US or EU/EEA processing region, EU/EEA data residency
Dedicated

Single-tenant instance

Your own database & compute. Nothing shared.

  • Physically separate deployment for your org alone
  • Region of your choice · optional BYOC
  • For regulated, security-strict, or high-volume data

Not sure which you need? Most teams start at isolated environments and move to dedicated if a review calls for it.

Security & compliance

Built to pass the review.

Database-enforced isolation

Row-level security forced at the database engine — so an app-layer bug can't leak one tenant's data into another's. Full mechanism in the security pack.

Data residency & subprocessors

Processed in your choice of region — US or EU/EEA, pinned per workspace (GDPR-aligned; US subprocessors under the EU-US Data Privacy Framework and SCCs). A documented map of every subprocessor and data hop, in the DPA.

Never trained on

Your uploads are never added to the public corpus or used to train models. Export or delete on request.

Audit trail

Every key, upload, and access event logged per workspace, exportable on request.

99.5% SLA

Availability target with a named technical contact and a dedicated support channel.

Transparent overage

Usage-based, 20% buffer, alerted before caps, invoiced monthly in arrears. No lock-outs, no surprises.

Where your audio goes

Straight about the pipeline.

No hand-waving: a security team gets a clear map of every hop your audio takes and every subprocessor that touches it, in the DPA.

Transcription

Runs on our own GPUs, not a third-party API. Choose your processing region — US or EU/EEA — pinned per workspace.

Entity extraction

Transcript text goes to a disclosed LLM subprocessor under the EU-US Data Privacy Framework, never used for training. EU-resident processing available on request.

Storage & index

EU-region object storage and database, isolated per workspace. Dedicated instances keep even this separate.

Get a quote

Tell us what your review requires.

Environments, expected volume, residency, and isolation level. We'll come back with a quote, a DPA, and a security pack, usually within a business day.

Talk to us Security overview See self-serve plans →