Local runtime
The engine that runs speech and voice workflows close to the work.
Product
A local-first runtime, not a patchwork of point tools
Izwi brings the core voice stack into one product shape: runtime, API, CLI, desktop evaluation surface, and a path to supported deployment.
Product shape
Local runtime
The engine that runs speech and voice workflows close to the work.
OpenAI-compatible API
Use /v1 endpoints if your team already integrates cloud AI APIs.
CLI
Pull models, start services, and operate the runtime locally.
Desktop app
A native surface for evaluation and prototyping.
Supported deployment path
Public downloads are for evaluation and self-serve use. Supported production deployment lives in the Enterprise Runtime path.
What Izwi includes
The core product is the runtime layer. The other surfaces help you evaluate it, integrate it, and operate it.
OpenAI-compatible API
Use /v1 endpoints if your team already integrates cloud AI APIs.
CLI
Pull models, start services, and operate the runtime locally.
Desktop app
A native surface for evaluation and prototyping.
Enterprise packaging
Supported deployment for controlled environments.
Where Izwi fits
Izwi sits between raw model components and the workflow product built on top of them. It is the runtime layer, not the full application layer.
Deployment targets
- developer laptop
- Apple Silicon workstation
- NVIDIA-backed server
- on-prem environment
- customer VPC
- isolated or offline environment where supported through enterprise packaging
What it is best at
- private transcription and diarization
- secure dictation and documentation workflows
- local voice layers for agent systems
- embedded voice capabilities inside regulated software products
What Izwi is not
The clearer the product truth is, the easier the deployment story becomes.
- not a generic cloud speech API
- not a collaboration suite
- not a catch-all dashboard for every audio task
- not a biometrics-first product
Product truth matters
Public downloads are for evaluation and self-serve use. Supported production deployment lives in the Enterprise Runtime path.
See how Izwi fits into your stack
Start with the docs if you are integrating. Talk to us if you need a controlled deployment path.