About Thalovant

We make open assistant infrastructure feel calm enough to use.

Thalovant turns the HiveMind and OpenVoiceOS lineage into a modern product surface: public hubs to discover, agents and API clients to connect, private workspaces to own, and one console for the operational work behind it.

Open voice roots. Private cloud discipline. Product-grade UX.
Mission
Make assistants usable across voice, web, API, agents, apps, and devices.
Approach
Hide setup friction without hiding ownership, policy, or telemetry.
Standard
Quiet interfaces, clear limits, source-backed skills, and observable operations.

Mission

Assistants should belong to the people running them.

Voice assistants have often been trapped between hobbyist setup and opaque consumer clouds. Thalovant exists to make owned assistant infrastructure practical: easy to start, cross-platform by default, and serious enough for private operations.

Cross-platform first

Voice, browser, API, agents, embedded products, desktop apps, and headless Linux should share one assistant layer.

Ownership without ceremony

Users should understand public hubs, private workspaces, ACLs, runtime capacity, and billing without becoming operators first.

Operations in sight

Telemetry, audit, GitOps, skills, releases, and watcher events need to be visible when the assistant becomes part of real work.

Open ecosystem

Built with respect for HiveMind and OpenVoiceOS.

Thalovant is shaped by the open assistant ecosystem: HiveMind's hub, agent, API, websocket, client, and satellite patterns, OpenVoiceOS' privacy-respecting voice assistant work, and the practical reality that users need one product path from discovery to private operation.

01 Control plane

Console, API, account, billing, hub, client, agent, ACL, runtime, and tenant workflows around assistant infrastructure.

02 Runtime operations

Watcher telemetry, status ingestion, GitOps publishing, release posture, and private workspace operations.

03 Skills and services

Source-backed skill workflows, marketplace posture, sample services, and deployment paths that make assistants useful quickly.

04 User experience

Console-first onboarding, Explore surfaces, plan posture, connection flows, and approachable paths for non-specialists.

References

The open projects behind the direction.

These are the public sources that explain the ecosystem Thalovant is building around. The Thalovant console remains the place for the product experience, account setup, billing, and operational documentation.

Thalovant

Start with the product, then grow into the platform.

Explore public hubs, create a free account, connect real clients, and bring private assistant operations online only when the work calls for it.