Amazon Polly bills per character converted to speech, so your text-to-speech cost scales directly with usage, and voice quality tiers change the rate. In production, that bill has no ceiling.
Orca Streaming Text-to-Speech runs on-device: cost-effective at scale, private, offline, and faster to first audio than cloud text-to-speech.
Amazon Polly uses pay-as-you-go pricing billed by the number of characters you convert to speech. The per-character rate depends on the voice type you pick, and the tiers (Standard, Neural, Long-Form, and Generative) each carry a different rate, with the higher-quality voices costing more. Polly is part of AWS, so usage rolls into your AWS bill alongside any data transfer and storage.
The model is transparent, but the structure means one thing for product teams with high-volume use cases: unbounded text-to-speech cost.
Usage-based cloud pricing is fine at prototype volume. In production it becomes a problem. Every notification read aloud, every IVR prompt, every voice agent response consumes characters, and the cloud bill climbs with adoption. Success makes it costlier: the more users you serve, the more you pay, with no upper bound, and choosing the natural-sounding Neural or Generative voices multiplies the rate.
Orca Streaming Text-to-Speech runs entirely on the device or your own server with flexible usage tracking methods at scale.
Open-source TTS latency benchmark shows that Orca Streaming TTS outperforms Amazon Polly on both first-audio and end-to-end response time.
| Factor | Orca | Amazon Polly |
|---|---|---|
| First token to speech | 128 ms | 1,538 ms |
| Voice assistant response time | 204 ms | 1,614 ms |
| Deployment | On-device / on-prem | Cloud API (AWS) |
| Audio handling | Stays on device, offline | Sent to the cloud |
| Cost model | Cost-effective at scale, no unbounded cloud bill | Per character, rate rises with voice tier |
Amazon Polly is a strong choice when you're prototyping, already deep in AWS and want text-to-speech that plugs into that ecosystem, or need a specific stock voice or language it offers.
Lightweight, on-device TTS wins when you are shipping speech at production scale, need to keep audio on the device for privacy, or want dual-streaming TTS for real-time applications where latency matters