Five products,
one builder.
Konvertex — scripts become studio-grade audio
What it does: paste a script, pick a voice, get narration — premium neural voices when online, Kokoro entirely offline, with voice cloning, pace and pitch controls, unlimited script length, and batch queues for long jobs.
How it's built: a self-contained local server with a browser interface — download, launch, and it opens on your machine. No telemetry, no usage caps.
Where Kaptain fits: Konvertex runs locally, so a Kaptain on the same box or tailnet can hand it scripts and collect audio as part of a bigger job — write the episode, voice it, package it.
// GitHub repo & README — at release
Konnect+ — own the contact, decide where it moves
What it does: scan a business card at the moment you get it; the contact lands in data you own — not a vendor's CRM — and you choose where it flows next.
How it's built: a mobile capture app with local-first storage; export and sync stay under your control.
Where Kaptain fits: capture is the phone's job, follow-through is Kaptain's — drafting the intro email, filing the lead, scheduling the follow-up from the data Konnect holds.
// GitHub repo & README — at release
TexEd — a LaTeX editor Kaptain can sit at
What it does: edit and compile LaTeX locally, Overleaf-style — and expose the same operations as a control API, so an agent can open a document, make an edit, recompile, and read the result.
How it's built: a single local Node service, standard library only — nothing to install beyond Node itself. Standalone: it needs no changes to Kaptain, and Kaptain needs none for it.
Where Kaptain fits: this is the pattern at its purest — TexEd is used daily as a Kaptain team member: Kaptain drives real résumé and document work through the API a human editor would use.
// GitHub repo & README — at release
Beatbot — your lossless library, your hardware
What it does: keep your FLAC/ALAC collection at home and stream it to yourself — a Spotify-style web player that installs on your phone and downloads tracks for offline, lossless where it lives, everywhere you go.
How it's built: a single server binary serving both the JSON API and the player UI. Private by default: it binds your tailnet interface only — never 0.0.0.0 — so nothing outside your own devices can reach it.
Where Kaptain fits: Beatbot is Kaptain's official reference app — proof that a person with Kaptain can build, host, and run a real self-hosted service on their own hardware and tailnet.
// GitHub repo & README — at release
Kapsion — the household's media brain
What it does: a private media library and TV controller — one responsive interface for browsing and playing what you own, served only to your trusted devices.
How it's built: a local server exposing one responsive UI across the tailnet, with an Android app presenting the same interface in a native shell.
Where Kaptain fits: same ecosystem, same trust boundary — a locally running service Kaptain can reach and orchestrate on your own network.
// GitHub repo & README — at release
Kaptain Voice — talk to it (work in progress)
What it is: a voice channel that installs beside Kaptain and connects to it — speech in, speech out, while Kaptain stays authoritative for reasoning, tools, approvals and history. The first slice already proves the contract: transcript in, response out, end to end.
The design: the channel owns the audio side — wake-word, speech-to-text, text-to-speech, interruptions — and each user keeps a voice profile in the app itself, including what name it should call them. Coming after the current release.
// in development
Controllable,
by design.
Everything above runs on hardware you own — which means Kaptain can work with it, not just near it. Today that happens over each app's local interface. Next: first-class plugins on these apps with keyed access, so a Kaptain you authorize can connect, drive, and coordinate them the way a connector does — one runtime, many instruments, all yours.