# Gradium Voice Cloning and Voice Design vs Soniox Voice Cloning (slim)

> Soniox Voice Cloning scores 68.7 (B) to Gradium Voice Cloning and Voice Design's 60.8 (C) for voice cloning. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/gradium-voice-cloning-vs-soniox-voice-cloning.md (~5,650 tokens) · this version ~3,280 tokens · JSON https://www.anchorterminal.com/compare/gradium-voice-cloning-vs-soniox-voice-cloning.json · canonical https://www.anchorterminal.com/compare/gradium-voice-cloning-vs-soniox-voice-cloning
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Soniox Voice Cloning scores 68.7 (B) on agent readiness against Gradium Voice Cloning and Voice Design's 60.8 (C), and leads in 6 of 7 scored categories. Gradium Voice Cloning and Voice Design leads on payments & pricing. Both do voice cloning.

- Gradium Voice Cloning and Voice Design: C 60.8, rank #637 of 1486 · https://www.anchorterminal.com/tools/gradium-voice-cloning.min.md
- Soniox Voice Cloning: B 68.7, rank #274 of 1486 · https://www.anchorterminal.com/tools/soniox-voice-cloning.min.md
- Gradium Voice Cloning and Voice Design, good for Builders on Gradium's TTS who want instant clones and designed voices in five European languages with EU residency. Ahead on Payments & pricing, 30 against 20. Also Free to start without a card; No incidents deducted, where Soniox Voice Cloning loses 3 points for them.
- Soniox Voice Cloning, good for A quick clone that has to speak many languages, from a vendor with clean data terms. Ahead on Reliability, 87 against 63; Agent ergonomics, 82 against 67; Security & auth, 67 against 48; Maintenance & community, 75 against 70; Transparency & trust, 71 against 63.

| Category | Gradium Voice Cloning and Voice Design | Soniox Voice Cloning |
| --- | --- | --- |
| Reliability (16%) | 63 | 87 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 86 |
| Agent ergonomics (13%) | 67 | 82 |
| Security & auth (14%) | 48 | 67 |
| Payments & pricing (10%) | 30 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 70 | 75 |
| Transparency & trust (7%) | 63 | 71 |

| Fact (where they differ) | Gradium Voice Cloning and Voice Design | Soniox Voice Cloning |
| --- | --- | --- |
| Vendor | Gradium SAS | Soniox |
| Hosted endpoint | `https://api.gradium.ai/api/voices/` | `https://api.soniox.com/v1` |
| Transports | HTTP, websocket | HTTP |
| Pricing | Freemium | Pay per use |
| Price for voice cloning | not published | $0.0117 per minute of audio |
| Licence | Proprietary service under Gradium's Terms of Service (version of 19 October 2026). The `gradium` Python SDK is on PyPI | Apache-2.0 (Python SDK) |
| Last release | 2026-11-06 | 2026-11-03 |
| Terms last updated | no date given | 2026-06-29 |
| Privacy policy last updated | no date given | 2026-06-29 |
| Customer content may train models | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | none | 12 stars, 22k npm/wk |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Reliability, Soniox Voice Cloning +24: Gradium Voice Cloning and Voice Design 63 (Graded on the hosted voice API with the hosted lines. Atlassian Statuspage at gradium.statuspage.io with five components, one of them Voice Cloning (20). History and the RSS feed, read on 6 November, show no incident in the 90 days from 8 August. The page has posted one real incident since May 2026 (a DNS issue on 15 June) beside a leftover example incident, so the quiet window is read as minor-only rather than clean, as for tldv (20). Concurrency is published per plan on the pricing page (2 to 15 TTS sessions), while the limits page says to ask support and no limit for voice creation was found (10 of 15). No 429, Retry-After or backoff guidance was found; the errors page says to open a new connection after an error, and voice creation takes a `timeout_s` (3 of 15). No SLA in the Terms or on the pricing page (0). Instant cloning carries no beta label (10). 20+20+10+3+0+10 = 63.); Soniox Voice Cloning 87 (Instatus page at status.soniox.com with five components in each of the US, Europe, Japan and India groups plus the Console, and a dated notice history (20). In the 90 days from 6 August the page posted three incidents, failed API key creation in the Console for 1 hour 10 minutes on 24 August, failed new EU real-time STT connections for 9 minutes on 25 August and Japan real-time STT overload for 45 minutes on 8 September, and none for October or November. None touches TTS or voices, so the record is clean for this listing, read as soniox-tts (30; was 20). TTS REST limits published, 100 requests a minute and 3 concurrent requests, and 20 voices per organisation (15). A 429 returns `limit_exceeded`; the OpenAPI file says to retry a 429 after a delay, retry a 408 and retry a 503 with backoff. No Retry-After and no idempotency key on voice creation, though a repeated create with the same name is refused because names are unique per project. Safe-retry guidance without idempotency keys earns 12, as soniox-tts (12; was 8). No SLA found (0). Voice cloning is part of the GA `tts-rt-v2` model (10). 20 + 30 + 15 + 12 + 0 + 10 = 87.)
- Security & auth, Soniox Voice Cloning +19: Gradium Voice Cloning and Voice Design 48 (Graded for voice cloning as the other listings in this category, with consent and misuse controls in place of the read-only line and training and retention of voice data in place of the prompt-injection line. API keys per organisation in a header, revocable and able to expire, with no scopes found (20 of 30). No consent or verification field and no watermark. The Terms make the client obtain the consent of anyone whose voice is a sample and bar impersonation without explicit authorisation, and the API FAQ says explicit consent is required (6 of 20). The Terms grant Gradium a licence to use Client Data to improve its services and train its models, with no opt-out found, and zero data retention (paid plans) excludes voice samples, so samples are kept and may be used for training (2 of 15). Organisation roles and a member list, with no per-call audit log found (5 of 15). SOC 2 Type II and ISO 27001:2022 audited by A-LIGN, a trust centre and security@gradium.ai. No security.txt (404) and no bug bounty found (15 of 20). 20+6+2+5+15 = 48.); Soniox Voice Cloning 67 (Graded for voice cloning, with consent and misuse controls in place of the read-only line and training and retention of voice data in place of the prompt-injection line, since the API returns audio and IDs rather than third-party text. Project API keys carry permissions per resource, with read and write levels for cloned voices, a missing permission returns 403 `permission_denied`, and temporary keys serve browser clients (30; was 25). The terms say Soniox doesn't verify the right to clone a voice, and there's no consent step or watermark, per the 1 October check, not re-read on 4 November (0 of 20). Audio is never used to improve models, and a voice's clip stays until you delete the voice (15). Per-request usage logs and every error's `request_id`, as soniox-tts reads them (10 of 15; was 8). SOC 2 Type 2 and ISO/IEC 27001:2022 stated; the Python SDK's SECURITY.md gives a disclosure route by email, GitHub, a maintainer or Discord; soniox.com/.well-known/security.txt answers 404 and no bug bounty was found, as soniox-tts (12 of 20; was 5). 30 + 0 + 15 + 10 + 12 = 67.)
- Agent ergonomics, Soniox Voice Cloning +15: Gradium Voice Cloning and Voice Design 67 (Voice objects are compact metadata (20 of 25). `GET /voices/` takes `skip` and `limit` (default 100) and since 23 October filters by `locale`, `gender` and `use_case` (20). Validation errors are structured 422 bodies, while synthesis errors arrive as plain-text HTTP 500 with a numeric code to parse (12 of 20). No idempotency key. Saving a design candidate twice answers 409, and the clone call has none (5 of 20). Three required fields with sensible defaults, and one official SDK, in Python (10 of 15). 20+20+12+5+10 = 67.); Soniox Voice Cloning 82 (Responses are small voice objects, and the OpenAPI file says the list returns the voices in your project (22 of 25; was 20). The voices list pages with `limit` (up to 1,000) and a `cursor`, and a count endpoint returns the total, with no filters on custom voices (15 of 20; was 10). Errors say which to retry and which are terminal, and `voice_not_prepared` tells you to recompute (20). No idempotency key; voice processing has a per-model status to poll, and a duplicate name is refused (10 of 20). Two required fields and SDKs for Python, Node, the web and React (15). 22 + 15 + 20 + 10 + 15 = 82.)
- Payments & pricing, Gradium Voice Cloning and Voice Design +10: Gradium Voice Cloning and Voice Design 30 (No x402, MPP or L402 (0). Plan prices and credits are public, 1 credit a character for speech, with no dollar price per unit, as cartesia-voice-cloning is read. Creating a clone uses no credits in the docs (10). The free plan has 45,000 credits a month, 5 custom voices and Voice Design, and the site says no credit card is required. Commercial use starts on the $12 plan (20). Signup is a browser flow in Gradium Studio (0). 0+10+20+0 = 30.); Soniox Voice Cloning 20 (No x402, MPP or L402 (0). Per-unit prices are public, $4 per million input text tokens and $21.50 per million output audio tokens, about $0.70 an hour by Soniox's estimate, with no cloning fee (20). No free tier for new accounts (0). Signup is a human browser flow (0).)
- Transparency & trust, Soniox Voice Cloning +8: Gradium Voice Cloning and Voice Design 63 (Closed service with clear terms, version of 19 October 2026, naming Gradium SAS with its Paris registration (15 of 30). The Terms allow training on Client Data, zero data retention excludes voice samples, the privacy policy gives retention criteria without periods, and a DPA is published as an exhibit. The statements agree but give no retention period for samples (15 of 30). Deprecations appear in dated release notes, with no written notice policy (10 of 20). EU and US residency is documented and selectable from the XS plan. Sub-processors sit in the trust centre, not read (12 of 20). 15+15+10+12 = 52.); Soniox Voice Cloning 71 (Closed service with clear terms, SDKs open source (15 of 30). Terms and privacy updated 2026-06-29 agree that samples aren't used for training and stay until deleted, with Async data auto-deleted after 30 days, but we found no public DPA or subprocessor list (20 of 30). Deprecation guidance and model aliases on the models page (15 of 20). Data residency documented, with regions in the US, Europe, Japan and India, no subprocessor list found (10 of 20). Per the 1 October check for the terms and privacy policy, not re-read on 4 November; the security page still says audio is never used to improve models and Async data is deleted after 30 days. 15 + 20 + 15 + 10 = 60.)
- Maintenance & community, Soniox Voice Cloning +5: Gradium Voice Cloning and Voice Design 70 (Read as a model, on the lines the other hosted cloning listings use (recency 30, dated releases 10, deprecation notice 10, support 15, SDKs 15, health 10). Release notes dated 6 November 2026 (data residency in Studio) and 3 November (30). Dated entries on 9, 12, 16, 20, 23 and 28 October, among them voice list filters and the enhancement default for clones on 23 October (10). `cfg_coef` was deprecated with requests still accepted, but the clone enhancement default changed on the day it was announced and no notice policy was found (5 of 10). Public release notes, support@gradium.ai and a Discord server, with no evidence read of how they answer (10 of 15). `gradium` on PyPI at 0.6.4 (4 September 2026), with no SDK in a second language (10 of 15). The SDK repository was not cloned (5 of 10). 30+10+5+10+10+5 = 70.); Soniox Voice Cloning 75 (Read as a model, on the lines soniox-tts, deepgram-tts and cartesia-tts use for hosted speech models (recency 30, dated releases 10, deprecation notice 10, support 15, issues 10, SDKs 15, health 10); the 1 October note used the tool lines. Python SDK `soniox` 2.11.0 on 3 November 2026 adds voice permissions and voice limits to its types, and the JavaScript tag v2026.11.03 ships `@soniox/node` 2.5.0 the same day (30; was 20). In the 90 days from 6 August, `tts-rt-v2` GA with high-fidelity cloning (11 August), the `tts-rt-v1` removal (31 August), Python 2.9.0 (11 August, adds the voices client), 2.10.0 (2 October) and 2.11.0 (3 November), and JavaScript tags v2026.08.11, v2026.10.12 and v2026.11.03 (10). `tts-rt-v1` was removed 20 days after its deprecation notice, while the deprecation of `api_key` in WebSocket config messages carries a 15 January 2027 deadline with a migration guide (5 of 10). The models page and a support channel, untested (5 of 15). SDK issues couldn't be read because GitHub's pages answered 403 (3 of 10). SDKs for Python, Node, the web and React (15). soniox-js runs a CI workflow on every push (lint and tests); the Python SDK has tests and a lock file but no workflow in its clone (7 of 10). 30 + 10 + 5 + 5 + 3 + 15 + 7 = 75.)