This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
speech-swift
The whole speech stack, on your laptop.
One Swift package for every speech capability you'd normally rent from a cloud API — transcription, expressive TTS, voice cloning, speaker-aware diarization, denoising, full-duplex speech-to-speech — running on-device on Apple Silicon. brew install soniqo/tap/speech ships a CLI, a local HTTP server, and the Swift API. Apache 2.0. No cloud, no keys, no per-minute bills.
Five API keys to build a voice AI app: ElevenLabs, Deepgram, Pyannote, OpenAI, and whoever's hosting your VAD. Five bills, five round-trips, five companies hearing your users.
Whisper.cpp killed cloud ASR. speech-swift does the same for the rest — expressive TTS, voice cloning, diarization, full-duplex speech-to-speech. One Swift package, one brew install, runs on Apple Silicon. brew install soniqo/tap/speech speech-server --port 8080
Your Mac is now a local speech API. Point your app at localhost:8080. Apache 2.0, no keys, no per-minute billing, no internet required.
Genuinely curious: which of the five cloud APIs would you replace first? And which one do you think is still worth paying for? I have opinions but I'd rather hear yours before I post them.
speech-swift was submitted on Product Hunt and earned 4 upvotes and 5 comments, placing #81 on the daily leaderboard. One Swift package for every speech capability you'd normally rent from a cloud API — transcription, expressive TTS, voice cloning, speaker-aware diarization, denoising, full-duplex speech-to-speech — running on-device on Apple Silicon. brew install soniqo/tap/speech ships a CLI, a local HTTP server, and the Swift API. Apache 2.0. No cloud, no keys, no per-minute bills.
On the analytics side, speech-swift competes within Open Source, Developer Tools, GitHub and Audio — topics that collectively have 624.5k followers on Product Hunt. The dashboard above tracks how speech-swift performed against the three products that launched closest to it on the same day.
Who hunted speech-swift?
speech-swift was hunted by aufklarer. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of speech-swift including community comment highlights and product details, visit the product overview.
aufklarer
Five API keys to build a voice AI app: ElevenLabs, Deepgram, Pyannote, OpenAI, and whoever's hosting your VAD. Five bills, five round-trips, five companies hearing your users.
Whisper.cpp killed cloud ASR. speech-swift does the same for the rest — expressive TTS, voice cloning, diarization, full-duplex speech-to-speech. One Swift package, one brew install, runs on Apple Silicon.
brew install soniqo/tap/speech
speech-server --port 8080
Your Mac is now a local speech API. Point your app at localhost:8080. Apache 2.0, no keys, no per-minute billing, no internet required.
Genuinely curious: which of the five cloud APIs would you replace first? And which one do you think is still worth paying for? I have opinions but I'd rather hear yours before I post them.
→ https://github.com/soniqo/speech-swift · https://soniqo.audio
And Discord server invitation