Google Cloud Text-to-Speech alternative without a cloud project

Teams look for a Google Text-to-Speech alternative when they do not want a cloud project for one feature, or when they want a cheaper custom voice. Here is the trade.

Who switches

  • You do not otherwise use Google Cloud
  • You want a custom voice without Google's Instant custom voice rate
  • You need quick prompt audio and do not want to decode base64

What you gain

  • An API key instead of OAuth and a cloud project
  • A custom voice at $6 per million characters versus $60
  • A $0.70 catalog rate
  • A checked phrase library, industry packs (47 live across 23 industries today, more being built for every industry)

What you give up

  • Many voice families and languages
  • SSML and Google Cloud IAM and quotas
  • Google's enterprise support and compliance programmes
  • A custom voice in languages beyond English (Speakvora: English supported, French and German beta)

The code change

Request shapes were taken from each provider's own documentation on 2026-10-08. Provider APIs change; check theirs before you migrate.

Google Cloud Text-to-Speech (docs: cloud.google.com/text-to-speech/docs/reference/rest/v1/text/synthesize)

curl -X POST https://texttospeech.googleapis.com/v1/text:synthesize \
  -H "Authorization: Bearer $(gcloud auth print-access-token)" -H "Content-Type: application/json" \
  -d '{"input":{"text":"Hello, how can I help you today?"},"voice":{"languageCode":"en-US","name":"en-US-Neural2-C"},"audioConfig":{"audioEncoding":"MP3"}}'
# JSON reply: {"audioContent":"<base64 audio>"}  (OAuth scope cloud-platform)

Speakvora text to speech

curl -X POST https://speakvora.com/api/v1/speak \
  -H "x-api-key: $SPEAKVORA_KEY" -H "content-type: application/json" \
  -d '{"text":"Hello, how can I help you today?","voice":"af_heart","lang":"en"}'
# JSON reply: {"url":"https://speakvora.com/...m4a","lang":"en","voice":"af_heart","characters":32,"format":"m4a"}
curl -s "$URL" --output prompt.m4a        # second step: download (or play) the link

What changes in practice: Google's call needs an OAuth token (service account or gcloud), a voice object with language code and name, and an audioConfig, and replies with base64 `audioContent`. Speakvora replaces all three with text, voice and lang, and replies with a URL instead of base64. The text limit is 500 characters per request, and Speakvora returns JSON with a url that you fetch or play. Library links are stable public files; custom-voice links last about five minutes.

A safe migration order

  1. Create a Speakvora key in the portal.
  2. Swap the synthesize call for /v1/speak and read the URL instead of decoding audioContent.
  3. Compare voices on the voices page.
  4. Retire the Google Cloud project once nothing else uses it.

Is it actually cheaper?

Google's pricing page lists Standard at $4, Neural2 at $16, Chirp 3: HD at $30 and Studio at $160 per million characters. Its Instant custom voice is $60 per million. Speakvora's catalog voices are $0.70 and a custom voice made from your own recording is $6, so the custom-voice list-price gap is about 90%.

Full numbers, scenarios and sources: Speakvora vs Google Cloud Text-to-Speech.

Test these before you commit

  • List every Google voice and language you use and check coverage in Speakvora's seven languages.
  • Check whether you use SSML, which Speakvora does not accept.
  • If you use Instant custom voice, create a Speakvora custom voice from the same recording and listen side by side; confirm you have consent for the voice.
  • Confirm nothing else in your company depends on the Google Cloud project before closing it.

Speakvora is in early access with billing is live; questions to support@eyeguide.ai. Latency: see the speed page.

Full comparison with Google Cloud Text-to-SpeechBrowse packsGet your free API key