"Self-hosted" gets used loosely enough that it's worth being specific about what it means here, and why it's the default rather than a paid add-on.
Your sources never become someone else's training data
Podcast Creator Studio runs on your own infrastructure. The documents you upload, the sites you scrape, the episodes you generate — none of it passes through a third-party SaaS backend that might retain it, log it, or use it for anything beyond producing your episode. If your source material is internal, unpublished, or simply not something you want sitting in a vendor's database, that's the baseline, not an upgrade.
Bring your own API keys — literally your own
For the AI providers that write scripts (OpenAI, Anthropic, DeepSeek, Gemini, Perplexity, Mistral) and the ones that voice them (ElevenLabs), you can supply your own API key and talk to that provider directly. Keys are encrypted at rest and never leave your instance. That means no markup on usage, no vendor lock-in, and no middleman with visibility into your API traffic. If you'd rather not manage keys yet, the studio's built-in AI covers the free tier — the option to bring your own is there when you want it, not a bait-and-switch later.
Why this matters even if you have "nothing to hide"
Privacy-by-default isn't only about secrets. It's about not having to think about a third party's retention policy, breach history, or terms-of-service changes every time you want to feed it a new source. A self-hosted pipeline means the question of "who else can see this" has one answer: whoever you gave access to your own infrastructure.
What you give up, honestly
Self-hosting means you're responsible for your own deployment — updates, uptime, and infra decisions are on you, not a vendor's SLA. For a lot of people that's exactly the trade they want; for others, especially at the very start, it's worth knowing going in rather than discovering later.