vox v0.1.0daemon · runningp50 132ms · 35× rt

// hero

Local voice runtime for Apple apps, companion clients, and tools.

Vox provides Swift packages for direct Apple embed mode, voxd for the local companion runtime, @voxd/sdk for local tools, @voxd/client for browser apps, and a CLI for checks and benchmarks.

$ download Vox.dmg Documentation

vox-operator

$ vox perf --client cli

p50=132ms p95=197ms 35x realtime

$ vox transcribe /tmp/sample.wav

done · 127ms (35x realtime)

$ vox warmup --voice parakeet

warm · ready=412ms

// packages

5 surfaces

Pick the surface that fits your app.

The same runtime ideas show up in different forms depending on where the voice work lives: in-process Swift, the local companion, the browser bridge, or operator tooling.

SWIFT PACKAGES

VoxCore · VoxEngine · VoxService · VoxBridge

The embed surface for Apple apps that want speech in process, with explicit warm-up and easy-to-follow runtime behavior.

→ Open the overview

COMPANION RUNTIME

voxd

The local daemon that stays warm for shared-process clients and gives tools a steady WebSocket JSON-RPC runtime to talk to.

→ Read runtime docs

BUN AND NODE SDK

@voxd/sdk

Typed companion client for local tools, agents, and app-side flows that want direct access to the daemon surface.

→ See the SDK

BROWSER SDK

@voxd/client

HTTP bridge client for browser apps that need local speech while keeping the runtime on the same machine.

→ Explore the web SDK

OPERATOR CLI

@voxd/cli

Doctor, voices, benchmarks, warm-up controls, and dashboards for day-to-day work with the stack.

→ Quickstart

// runtime

4 principles

Embed in apps. Run companion mode for the web and local tools.

Apple apps

Swift owns the embed surface. If an Apple app can keep speech local and in process, Vox lets it do that.

Warm-up is part of the product

Cold and warm state stay visible. Apps and tools schedule, inspect, and reason about model readiness instead of guessing where the delay comes from.

Companion, not cloud

Vox Companion serves browser integrations, local tools, and the CLI on the same machine. You do not need to turn every voice workflow into a cloud service.

Shared surfaces

Swift packages, voxd, @voxd/sdk, @voxd/client, and @voxd/cli all share the same runtime ideas, telemetry, and lifecycle semantics.

// companion

Manage Vox from the menu bar.

The companion app lives in the menu bar. Open it for daemon health, allowed origins, and the trust state of any app calling the local bridge.

When a third-party app deep-links into Vox, you get a co-branded landing — verified callers go straight to work, unverified ones get a one-click allow path. No remembering JSON files.

Hudson KitOrigin allowlistLocal-first

Vox · welcome

// related

A few related projects.

TALKLIE

A related product built around the same local voice ideas.

usetalklie.com

LINEA

Another native client direction built around the same local-first approach.

uselinea.com

LATTICES

Related infrastructure work for local agent workflows.

lattices.dev

// observability

See where the time goes.

Every voice request carries stage timings. Slice by client, route, model, and voice.

vox tui

// install

Get the companion running for the web and local tools.

Apple apps can embed Vox directly. For browser and shared-process workflows, install the companion app first. The Node CLI can then register, inspect, and benchmark the same local runtime from terminal workflows.

DOWNLOAD

Drag Vox to Applications. The companion starts automatically on login, so web and tooling integrations have a local bridge ready on the machine.

Vox.dmg

CLI

$ npx -y @voxd/cli install

registers Vox.app or ~/.vox/bin/voxd as a LaunchAgent

$ npx -y @voxd/cli doctor

daemon: running

backend: parakeet

ready