Daily Desk to HubOS

Start with Daily Desk. Upgrade when memory matters.

Try a useful, memoryless public assistant first. When the workflow is worth keeping, move it into a private workspace with memory, analytics, clients, skills, and a paid pilot path.

  • Voice
  • Web
  • API
  • Agents
  • Embedded
  • Headless Linux
Try

Use Daily Desk.

Prove usefulness in public with no personal memory stored.

Public Memoryless Useful
Upgrade

Make it private.

Workspace memory, clients, private skills, analytics, API, and MQTT come online when needed.

Package

Book a pilot.

Turn one office, clinic, hospitality, developer, or edge workflow into a paid hub.

Scoped Paid Reusable
Thalovant Explore in light mode showing public hubs, prompt examples, source categories, voice-ready flows, API surfaces, and signup actions Thalovant Explore in dark mode showing public hubs, prompt examples, source categories, voice-ready flows, API surfaces, and signup actions
Real public Explore surface from dash.thalovant.com Product

Product journey

Public proof, private memory, paid rollout.

The first path is intentionally light: use Daily Desk in public, create the private workspace only when memory matters, then package the workflow when a real buyer wants it deployed.

Try Daily Desk

Start with a live public assistant that proves the platform without retaining personal memory.

Public proof Usefulness first, account setup second.
Try Daily Desk
Create the workspace

Move to private memory, clients, skills, and analytics when the workflow needs context.

Private memory Workspace context is opt-in and controlled.
Create private workspace
Connect every surface

Add voice, web, API, agent, embedded, desktop, room, or headless clients when the assistant becomes operational.

HubOS layer One workflow can speak through many clients.
Create free account
Book a paid pilot

Scope the first office, clinic, hospitality, developer, or private edge workflow with Thalovant.

Revenue signal A charged pilot becomes a reusable hub template.
Book paid pilot

Console

The console is the product center.

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.

Thalovant public hubs console showing hub search, certification filters, and live public hub cards
Explore first

Use a real assistant surface before you configure infrastructure.

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.

Public hubs 9 visible
Certified 3 reviewed
Next step Create account

Product validation

Real surfaces, not a marketing mockup.

These captures come from the public Thalovant workspace: hub discovery, fleet operations, and connected clients in the same dashboard-native theme.

Thalovant public hubs console with search, filters, and public hub cards in light mode Thalovant public hubs console with search, filters, and public hub cards in dark mode
Public discovery Explore before you commit.

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.

  • Published hubs
  • Starter prompts
  • Private or public
  • No setup first
Thalovant fleet overview with hubs, clients, intent usage, live load, and operational health in light mode Thalovant fleet overview with hubs, clients, intent usage, live load, and operational health in dark mode
Operations Fleet posture without noise.

Workspace limits, live load, telemetry health, maintenance, private hubs, public publishing, and hub counts stay visible in a single operational overview.

  • Intent limits
  • Fleet load
  • Maintenance
  • Status
Thalovant connections console showing connected clients, hub placement, roles, and policy coverage in light mode Thalovant connections console showing connected clients, hub placement, roles, and policy coverage in dark mode
Connections Clients become manageable surfaces.

Voice, web, API, agent, and local clients can be tracked by hub, role, state, policy coverage, and last event.

  • Roles
  • ACL
  • Scopes
  • Last event

Plans

One ladder from public demo to private workspace.

Daily Desk starts free and memoryless. Private and Team plans add the owned hub, runtime, client, skill, and analytics capacity needed when the assistant becomes part of real work.

Daily Desk
Free

$0 for public discovery

Try public hubs and Daily Desk without private memory.

  • Memoryless Daily Desk demo
  • 1 active client
  • Starter public-hub usage
Create free account
Connection pack
Connect

$12/mo for more public clients

Add client and ACL room without running private hub infrastructure.

  • 5 active clients
  • 10 ACL policies
  • No private hub required
Open console
Shared operations
Team

$149/mo per workspace

For companies, labs, and teams running several hubs, runtimes, and client groups.

  • 8 private hubs + 5 runtime slots
  • 250 clients + 125 ACL policies
  • Priority support for operations
Open console
Flexible paths

On Demand stays available for intermittent usage, Enterprise is for custom terms, and paid pilots are scoped separately when a workflow needs hands-on packaging.

Paid pilots

Turn one useful workflow into a vertical hub.

When Daily Desk proves the need, Thalovant helps scope the private memory, skills, analytics, consent posture, and rollout path for a real buyer workflow. The goal is a paid deployment and a reusable template, not another free pilot.

Clinic front desk

Administrative FAQ, appointment prep, forms guidance, and staff lookup.

Hospitality hub

Concierge answers, service requests, local info, and escalation paths.

Developer hub

API, MQTT, SDK clients, private skills, and analytics for one workflow.

Cross-platform

One assistant layer for builders, teams, and products.

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.

Voice and local builders Desktop, room, and headless assistants. Pair macOS, Windows, Linux, browser, room, embedded, or headless clients to the same assistant layer.
Developers API-shaped flows without a control plane detour. Start from public hubs, source-backed prompts, BYOS, and client context before creating a private workspace.
Agent workflows Assisted or autonomous work with governed context. Run agents that can use hubs, tools, APIs, skills, sources, and workspace policy.
Product teams Embedded assistants with portable operations. Bring assistants into apps, devices, services, and customer experiences while keeping skills and sources portable.
BYOS Bring Your Own Skill when the workflow is yours. Attach custom capabilities to private workspaces, public hubs, API flows, agents, and client experiences.
Labs and teams Private operation and public publishing in one console. Run private hubs, publish public hubs, manage billing, policy, GitOps, audit, and watcher telemetry.

Trust posture

Private by default. Observable by design.

The quiet user experience is backed by encrypted specs, scoped access, signed telemetry, audit history, and GitOps context.

Private boundaries Encrypted hub and client specs, tenant ownership, RBAC, scopes, and ACL policy.
Operator memory Audit logs, billing posture, plan changes, runtime updates, and GitOps drift stay attributable.
Live signals HMAC-signed watcher events, status history, presence, and SSE updates reach the console.

Thalovant.com

Start with a surface. Grow into the platform.

Public hubs, private hubs, BYOS, free account onboarding, voice, web, API, agents, embedded clients, governed skills, and live operations in one calm system.