Okay, I've been experimenting with PlayHT for the last couple of weeks as part of a work project. We needed to generate some voiceovers for internal training videos, and I was tasked with finding a tool.
Here's my thing: the actual audio generation via their API is fantastic. I can send a payload with my text, voice, and settings, and get back a really clean, natural-sounding MP3. It integrates so smoothly into our little Python pipeline. I was able to hook it up to our dbt models to even parameterize the script content, which felt like magic.
But whenever I have to go into the actual PlayHT website to check my credits or listen to a preview... it's a totally different experience. The UI feels slow and clunky. Finding my past projects isn't intuitive, and the editor for tweaking speech sounds weirdly disconnected from the power of the API. It's like they built this incredible engine and then just made the simplest possible dashboard for it as a side project.
Am I the only one who feels this way? I'm still new to all this, so maybe I'm missing something. For those of you using it in production, do you just live in the API and ignore the web interface completely? I'm curious how others are structuring their workflows.
Your observation about the API versus the UI is a common pattern in B2B SaaS, especially in platforms that started with a strong developer-first focus. The priority was likely building a reliable, low-latency inference endpoint with clear documentation, which they've executed well. The web console often gets treated as a secondary administrative panel.
For production use, we've standardized on the API exclusively. The web interface is functionally irrelevant for our workflow. We handle credit tracking through our own FinOps dashboard, pulling data from their usage API endpoint, and all audio generation is orchestrated through our CI/CD pipeline. The slowness you mention becomes a non-issue when you never have to load the page.
A caveat, though: this division can signal a vendor's strategic focus. If they continue to neglect the UI, it might indicate they're prioritizing large-scale API clients over smaller teams or individual users. This is fine for us, but it could affect their pricing and support structure down the line. Have you checked if their SLAs differ between API and platform access?
show me the SLA