Preview public hubs.
Test source-backed prompts, voice flows, APIs, and skills before creating an account.
Assistant infrastructure
Thalovant lets you try useful public assistants first, then connect your apps, devices, APIs, agents, and private skills from one console. Explore public hubs, save what works, connect a client, or publish your own hub.
Test source-backed prompts, voice flows, APIs, and skills before creating an account.
The same assistant context follows desktop, browser, API, agents, and embedded clients.
Keep hubs private or publish them publicly. Bring your own skill when ownership matters.
Product journey
The first path is intentionally light: inspect a live public surface, keep your intent, connect the client, then grow into private operation or publish a useful hub to the world.
Browse source-backed hubs, starter prompts, browser previews, and API-shaped experiences before setup.
Keep hubs, prompts, client intent, and workspace context without choosing paid infrastructure first.
Add voice, web, API, agent, embedded, desktop, room, or headless clients when the assistant becomes part of a workflow.
Bring private hubs, public hub publishing, BYOS, policy, GitOps, audit, billing, and telemetry online when needed.
Console
Explore public hubs, create an account, connect clients, manage BYOS, publish public hubs, keep private hubs controlled, and watch live operations from the same product surface.
Published hubs stay searchable inside the console, with certification, audience guidance, source-backed cards, and starter prompts. Private hubs stay owned until you choose to expose a public surface.
Product validation
These captures come from the public Thalovant workspace: hub discovery, fleet operations, and connected clients in the same dashboard-native theme.
Start with published hubs, prompts, sources, and certification signals. When something proves useful, keep it private for your workspace or publish it as a public hub.
Workspace limits, live load, telemetry health, maintenance, private hubs, public publishing, and hub counts stay visible in a single operational overview.
Voice, web, API, agent, and local clients can be tracked by hub, role, state, policy coverage, and last event.
Plans
Start with Free, add connection capacity when public hubs are enough, then move into private or shared operations only when the assistant becomes part of real work.
$0 for public discovery
Explore public hubs, keep account context, and connect one active client.
$12/mo for more public clients
Add client and ACL room without running private hub infrastructure.
$39/mo for one owned workspace
Run private hub and runtime capacity for one operator or focused project.
$149/mo per workspace
For companies, labs, and teams running several hubs, runtimes, and client groups.
On Demand stays available for intermittent usage, and Enterprise is for security review, deployment shape, SLA, SSO, procurement, or custom support terms.
Cross-platform
Thalovant is not only a voice assistant surface. It is the control layer for assistants that run through voice, browser, API, agent workflows, embedded products, local devices, public hubs, private workspaces, and BYOS.
Trust posture
The quiet user experience is backed by encrypted specs, scoped access, signed telemetry, audit history, and GitOps context.
Thalovant.com
Public hubs, private hubs, BYOS, free account onboarding, voice, web, API, agents, embedded clients, governed skills, and live operations in one calm system.