Lennex Zinyando

Lennex Zinyando

@zinyando.bsky.social

AI Engineer | Technical Writer | ember.js | https://www.zinyando.com

170 followers571 following109 posts

IBM’s Granite Speech 4.1 2B Plus is built for rich transcription: speaker labels, word timestamps, keyword biasing. Best way to test it locally: Izwi. `izwi pull Granite-Speech-4.1-2B-Plus` Local-first voice AI stack. OpenAI-style APIs. github.com/izwi-ai/izwi

github.comGitHub - izwi-ai/izwi: Voice AI runtime. Local first transcription, speaker diarization, TTS, and voice cloning with an OpenAI compatible API.Voice AI runtime. Local first transcription, speaker diarization, TTS, and voice cloning with an OpenAI compatible API. - izwi-ai/izwi

Building infrastructure without VC means consulting to survive. Every hour consulting is an hour not building. Funded competitors sprint ahead while you're stuck in the consult-build loop. Wouldn't have it any other way. Heads down, back to building Izwi AI.

Every time I pitch Izwi, people think I've lost my mind. "How do you compete with billion dollar labs as a solo founder?" Simple: They are building for their cloud. I'm building for your local device. As Jack Altman says, there is massive alpha in being willing to look crazy.

1/ Every day I get questions about what Izwi is and what business we are in. Short answer: We're building the private audio runtime for production voice AI. Let me explain what that actually means 🧵

View full thread

5/ We're not competing with cloud speech APIs on convenience. We're building for teams who need privacy, control, and cost predictability. The teams that can't, or won't, send voice data to someone else's cloud. That's Izwi. That's the bet we're making. #voiceAI #AIinfrastructure #startup

1/ Every day I get questions about what Izwi is and what business we are in. Short answer: We're building the private audio runtime for production voice AI. Let me explain what that actually means 🧵

View full thread

3/ Neither works when you're a healthcare company that can't send patient data to the cloud. Or a fintech with strict data residency rules. Or any team needing sub-100ms latency. The market is telling us: private deployment is no longer a niche feature. It's a standard buying requirement.

4/ Izwi gives you one unified runtime that runs entirely on your own infrastructure, on-device, in your VPC, behind your firewall. OpenAI-compatible API. No audio leaves your environment. No usage-based billing that explodes at scale. Just production-ready voice infrastructure you control.

1/ Every day I get questions about what Izwi is and what business we are in. Short answer: We're building the private audio runtime for production voice AI. Let me explain what that actually means 🧵

2/ If you're building voice AI today, you have two options: 1. Send audio to the cloud (Google, AWS, OpenAI) - easy to start, but expensive at scale + data privacy headaches 2. Stitch together open-source tools - each with different APIs, barely production-ready Neither works for many teams.

How do you build features people want when nobody opts into telemetry? Open source founders know the trap: ship, celebrate, nada. Just vibes and prayer. Izwi launched with optional telemetry. <1% opted in. Now we're flying blind. Startup problems. github.com/izwi-ai/izwi

github.comGitHub - izwi-ai/izwi: On-device audio AI runtime. Local first transcription, speaker diarization, TTS, and voice cloning with an OpenAI compatible API.On-device audio AI runtime. Local first transcription, speaker diarization, TTS, and voice cloning with an OpenAI compatible API. - izwi-ai/izwi

Fireworks AI shutting down their audio APIs is a reality check. Given 30 days' notice, you realize the brutal truth: You’re not building a product. You’re renting one. Portable audio inference. Run it anywhere, cloud or on the edge. Own your stack. github.com/izwi-ai/izwi

github.comGitHub - izwi-ai/izwi: On-device audio AI engine. Local first transcription, TTS, and voice cloning with an OpenAI compatible API.On-device audio AI engine. Local first transcription, TTS, and voice cloning with an OpenAI compatible API. - izwi-ai/izwi

ElevenLabs biggest flaw: you're locked into their cloud. Their servers. You pay per character. You need API keys. I built Izwi AI. Open-source voice AI that runs 100% on your machine. No API keys. No cloud. No subscription. 276 ⭐ on GitHub. github.com/izwi-ai/izwi

github.comGitHub - izwi-ai/izwi: Open-source, on-device audio AI engine. Local first transcription, TTS, and voice cloning with an OpenAI compatible API.Open-source, on-device audio AI engine. Local first transcription, TTS, and voice cloning with an OpenAI compatible API. - izwi-ai/izwi

🚀 Just shipped v0.1.0-beta-11, the biggest UI update in this beta cycle. Redesigned UI + new features that make Izwi feel like a real product. Hot take: "Open source ElevenLabs" Try it and tell me I'm wrong: github.com/izwi-ai/izwi... ⭐ If you believe in open source voice AI

github.comRelease Izwi v0.1.0-beta-11 · izwi-ai/izwiWhat's Changed ✨ New Features System Tray Integration: Added system tray controls for the desktop app, including settings for startup behavior and visibility. In-App Updater: Introduced a cross-pl...

I asked Grok to tell me about myself, and it said: "You're the guy quietly (but very deliberately) building infrastructure so voice AI can actually work offline, cheaply, and, hopefully, soon in languages and contexts that big cloud providers still ignore." IzwiAI 🚀🔥

Most transcription tools give you text. Speaker diarization tells you who said what — and when it matters most (attorney-client calls, medical conversations, financial advisory). The problem? Cloud solutions create compliance nightmares. izwiai.com/blog/speaker...

izwiai.comSpeaker Diarization: The Feature Nobody Talks About But Everyone Needs - Izwi BlogWhat speaker diarization is, why regulated industries can't afford cloud solutions, and how Izwi handles it locally.

2.6 billion people are offline. Cloud AI latency: 200–800ms. Local-first: 5–50ms. Your "AI-powered" app breaks the moment someone walks into a building with bad signal. Local-first AI isn't a niche. It's the future. Blog post → izwiai.com/blog/why-you...

izwiai.comWhy Your AI App Needs to Work Offline - Izwi BlogCloud costs don't scale. Latency kills user experience. And 2.2 billion people are offline. The practical case for local-first AI, and how to add it to your app.

Sending customer data to the cloud? That's a compliance nightmare in Financial services. On-device AI changes that: • Real-time, no cloud latency • Call center transcriptions, no third-party access • Customer communications, no external servers izwiai.com/blog/on-devi...

izwiai.comOn-Device AI Use Cases: Financial Services - Izwi BlogHow on-device AI enables real-time fraud detection, secure customer communications, and regulatory compliance in banking—without sensitive data leaving your infrastructure.

Legal AI has a privilege problem A federal judge just ruled: using cloud AI can WAIVE attorney-client privilege. Uploading client info to third-party AI tools? That may not be protected. Blog post - izwiai.com/blog/on-devi... #LegalAI #OnDeviceAI #AttorneyClientPrivilege

izwiai.comOn-Device AI Use Cases: Legal - Izwi BlogHow on-device AI protects attorney-client privilege, secures client communications, and streamlines legal workflows—without data ever leaving your firm.

🩺 Healthcare AI + privacy = headache Cloud AI = patient data leaves your control. HIPAA compliance gets messy. On-device AI? Data never leaves the device. Privacy and productivity aren't mutually exclusive. izwiai.com/blog/on-devi... #HealthcareAI #OnDeviceAI #HIPAA

izwiai.comOn-Device AI Use Cases: Healthcare - Izwi BlogDiscover how on-device AI enables HIPAA-compliant healthcare workflows—clinical documentation, patient intake, accessibility, and decision support without data ever leaving the device.