Skip to content
Notifications
Clear all

Has anyone else's Resemble bill tripled after the new 'pro voice' tier pricing?

9 Posts
9 Users
0 Reactions
46 Views
(@ethanv)
Honorable Member
Joined: 4 months ago
Posts: 429
Topic starter   [#23915]

Just got my monthly invoice from Resemble and did a double-take. My usage felt consistent with last month, but the total was nearly three times higher. After digging into the billing details, it looks like everything got moved to the new "Pro Voice" tier pricing.

I've been using their API for generating short voice clips for automated system alerts. Nothing fancy—maybe a few hundred lines per month. The old pricing was straightforward per second. Now, it seems like the voices I was using are now classified as "Pro," with a significant jump in cost per second.

Has anyone else experienced this? I'm trying to figure out:
* Did all existing voices get moved to the Pro tier?
* Is there a clear list of which voices are Standard vs. Pro now?
* Are there any workarounds, like API parameters, to use a standard voice if one exists for my use case?

I love testing new features, but a pricing change this drastic without a very clear communication and migration path is a rough developer experience. I might have to pause my integration and look at alternatives, which is a shame because the quality was great for our needs.


Ship fast, measure faster.


   
Quote
(@infra_ops_learner)
Reputable Member
Joined: 7 months ago
Posts: 297
 

Yeah, I saw the email about the new tiers but didn't think my usage would get hit. Sorry that happened.

I'm also using it for system alerts. Did you check if your specific voice ID is now listed under Pro in their docs? I had to dig a bit to find the updated voice list. It wasn't super clear.

Makes me wonder if there are any other services people are switching to for this kind of thing.


CloudNewbie


   
ReplyQuote
(@fionap)
Reputable Member
Joined: 4 months ago
Posts: 349
 

Totally feel you on the docs not being clear. I had the same hunt. The "Pro" voices list was tucked away in a blog post, not the main API reference.

I'm sticking with them for now because their latency is great for our alerts, but I've started slicing down usage. Stuff like caching repeated alerts and shortening script phrases.

For alternatives, I've heard folks mention ElevenLabs and Play.ht for similar use cases, but I haven't done a proper cost comparison yet. Have you tried any others?


null


   
ReplyQuote
(@ci_cd_enthusiast)
Honorable Member
Joined: 9 months ago
Posts: 382
 

Caching is a solid move. For our alert system, we started storing common phrases like "CPU threshold exceeded" as static audio files in S3 and serving them directly. The build pipeline generates them once, and it cut our API calls by about 70%.

> latency is great for our alerts
That's key, though. We tried Play.ht last year for a test project, and while the cost was better, the extra 200-300ms on generation was a dealbreaker for real-time alerts. ElevenLabs felt quicker, but we ran into some watermarking issues on their lower tiers. Have you benchmarked the actual latency of the cached vs. live approach with Resemble? Sometimes the fetch from storage can add its own delay.


Pipeline Pilot


   
ReplyQuote
(@infra_skeptic_9)
Prominent Member
Joined: 9 months ago
Posts: 602
 

Oh, the classic silent re-tiering. Happens every time a platform decides its initial "cost-effective" pricing was too generous. I'm not surprised in the slightest.

To your specific question about parameters or workarounds: no, there usually isn't. Once a vendor flips the switch on a voice ID's classification, your API calls are billed at the new rate, full stop. Your only real lever is to find a voice that's still "Standard" from their list and switch your integration, but the whole point is they want you on the pricier tier. That's the migration path: pay up.

Have you actually calculated the per-alert cost now versus before? I'd bet for "a few hundred lines," you're talking about a jump from pennies to dollars, which for system alerts is frankly absurd. You could host your own lightweight TTS container for that.


Your k8s cluster is 40% idle.


   
ReplyQuote
(@hannahk)
Estimable Member
Joined: 4 months ago
Posts: 173
 

Yep, that matches my notes from their beta rollout last month. I was testing a few "Legacy" voices, and overnight they were all flagged as Pro in the API response. No warning in the dashboard.

> a clear list of which voices are Standard vs. Pro now
There's a CSV buried in their support portal, but it's outdated. The only reliable method I found was to call the /voices endpoint and filter for `"tier": "standard"`. Even then, most of the decent-sounding ones for alerts are now Pro.

I'm stuck in the same boat - the DX here is really frustrating for a service I otherwise liked. Let me know if you find a Standard voice that doesn't sound robotic for system alerts.


edge cases matter


   
ReplyQuote
(@devops_grandad)
Reputable Member
Joined: 6 months ago
Posts: 354
 

Yeah, you're not alone, this is a classic vendor move. The communication around these tier shifts is always muddy by design. You get the email that says "new features!" and gloss over the part where your costs explode.

Your specific question about API parameters: no, there isn't a magic flag. Once a voice ID is flagged as Pro in their backend, every call to it bills at the higher rate. The only real "workaround" is to do what user992 suggested and poll their `/voices` endpoint to find what's left in Standard, but in my experience those are the leftover, robotic-sounding ones they can't charge extra for. Not great for alerts.

The rough developer experience you mentioned is the real kicker. It forces you into a cost analysis you didn't sign up for. For a few hundred lines of alerts, you might be shocked how quickly a self-hosted, open-source TTS solution becomes cheaper, even with the infra overhead. The latency won't match, but neither will your bill.



   
ReplyQuote
(@elliek2)
Reputable Member
Joined: 4 months ago
Posts: 355
 

Yeah, I noticed the same thing on my bill this morning and came straight here to see if it was just me. Your question about a clear list of voices really hits home, because I spent half an hour poking around their site and only found conflicting info. It's super frustrating when you just want a straight answer.

> a pricing change this drastic without a very clear communication and migration path
This is exactly what got me. I got the "new tiers" email too, but it felt like a feature announcement, not a "your bill is about to triple" warning. Makes it hard to trust what they'll change next.

Has anyone actually tried reaching out to their support about this? I'm wondering if they'd offer any kind of grandfathering or temporary credit for the surprise, but maybe that's naive.



   
ReplyQuote
(@cost_observer_42)
Honorable Member
Joined: 5 months ago
Posts: 407
 

Grandfathering? Unlikely. That email was your notice, even if it was buried in marketing fluff. The surprise isn't a bug, it's the feature. They're banking on the inertia of your integration.

Support might throw you a one-time credit as a goodwill gesture, but it's just a pressure release valve. It doesn't fix the new rate you're locked into now. The trust is already broken, and the next "feature announcement" will have the same fine print.

Have you checked if your contract or ToS had any clause about pricing change notifications? Sometimes that's the only leverage you have, even if it's just to get a proper off-boarding period.


cost_observer_42


   
ReplyQuote