Turn sources into your podcast
Vozonda reads them, voices make waves, you listen.
What is Vozonda?
Give Vozonda articles, papers, PDFs, audio files, podcast episodes, screenshots, YouTube videos, RSS feeds or your own notes, and it turns them into the show you want. Audio sources are transcribed locally.
- Fourteen show formats: deep dive, quick brief, debate, critique, morning dispatch of your feeds, feature story, explainer, three-voice roundtable, and more.
- One to three voices, or a single narrator: in ten languages; translates sources into the language you want to hear.
- Watchlists: turn RSS feeds into a daily or weekly digest that fills your feed automatically.
- Every episode comes with: chapters, transcripts, takeaways, highlights, and shareable clips; read and fix the script before it is voiced.
- Self-hosted & private: runs on your hardware with Docker. Voice generation runs on CPU by default with Kokoro (no GPU required). No cloud logins, no telemetry, and no subscriptions.
- Personal RSS feed: publishes episodes to your private podcast feed with chapters and transcripts, compatible with any podcast player, and optionally to Nostr.
Installation
Install the orchestrator package from PyPI:
pip install vozonda
Or with uv:
uv add vozonda
Optional Extras
- Local Kokoro TTS (CPU-friendly):
pip install "vozonda[tts-kokoro]"
- Local Piper TTS:
pip install "vozonda[tts-piper]"
- Local Transcription (faster-whisper):
pip install "vozonda[stt]"
- All TTS & STT extras:
pip install "vozonda[tts]"
- Agent MCP server support:
pip install "vozonda[mcp]"
Usage
Start the orchestrator API server:
vozonda
# or
vozonda-api
By default, the server listens on http://127.0.0.1:8765.
Docker Quickstart
For full self-hosting with web UI and dependencies:
git clone https://github.com/Vozonda/vozonda.git
cd vozonda
docker compose up -d
Prebuilt multi-architecture containers are available from GitHub Container Registry:
docker pull ghcr.io/vozonda/vozonda:latest
Links & Community
- Website & Audio Samples: https://vozonda.com
- GitHub Repository: https://github.com/Vozonda/vozonda
- Bug Tracker: https://github.com/Vozonda/vozonda/issues
- License: MIT
Metadata
Release files for vozonda 0.7.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| vozonda-0.7.4.tar.gz | 787.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vozonda-0.7.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.1 MB
Release files / vozonda-0.7.4.tar.gz
| Download URL | vozonda-0.7.4.tar.gz |
|---|---|
| Size | 787.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a5a6b4b7402d74d61504a1de8090b1248517db4ad0f9d30c7315fce732355754
|
|
BLAKE2b-256 checksum How to use checksums |
28f5a45c5c2c4b94875874f6050afd7018f99e0baa80df6d8d1cd9caa3d864ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency logRelease files / vozonda-0.7.4-py3-none-any.whl
| Download URL | vozonda-0.7.4-py3-none-any.whl |
|---|---|
| Size | 326.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e59580910614cda5d08c31af42bb297989f0eddba60d233d71a2601c286cdc49
|
|
BLAKE2b-256 checksum How to use checksums |
d57a04ba8d6e5adcdaeab5b6b8a771bd4ed7ee164c2be4a98857010b060bf9ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency log