Thalovant docs Plan paths, pairing, runtime groups, skills, operations, and references
Thalovant Request access

Documentation

Build an assistant infrastructure workspace without guessing.

Start with the operating path the dashboard already uses: public hub discovery, private workspace setup, client pairing, hubs, runtime groups, skills, ACL policy, GitOps, billing posture, and watcher telemetry.

Request access Satellite downloads

Quickstart

Five steps from product path to observable assistant network.

This first docs surface stays implementation-light until the full API reference is ready, but it gives operators the correct order of work.

Step 01

Create the workspace

Choose Free, Connect, Private, Team, On Demand, or Enterprise based on whether you need public hubs or private capacity.

Step 02

Pair a satellite or client

Use a setup link to connect Thalovant Voice, a web client, a developer client, or a headless Linux satellite.

Step 03

Route through a hub

Use a public hub for discovery, or attach the client to an owned hub when private routing is needed.

Step 04

Run skills in a runtime group

Assign a runtime group, install skills, review inventory, and keep release posture visible.

Step 05

Attach policy and observe

Review ACLs, audit context, watcher telemetry, billing posture, usage, and GitOps alignment.

Plan paths

Billing posture describes infrastructure access, not just payment.

The dashboard keeps Billing visible during onboarding so users know which capabilities are available before they try to create private infrastructure.

Free Public hub discovery Browse public hubs, preview prompts, and connect one client before needing private infrastructure.
Connect More public clients Add client and ACL capacity while continuing to rely on public hub runtime surfaces.
Private Owned hub and runtime Operate a private workspace with a hub, runtime slot, clients, ACLs, managed domains, and paid skills.
Team Shared production workspace Use several hubs, runtime slots, clients, ACLs, public listings, and priority support for shared operations.
On Demand Metered infrastructure Request usage-based billing for intermittent, experimental, or bursty workloads with budget guardrails.
Enterprise Dedicated requirements Scope dedicated, regulated, high-volume, customer-owned, SLA, or support-specific deployments.

Pairing

Create a setup link, then let the client claim its identity once.

The setup page is designed to feel like pairing headphones: create a connection, send a link, open the app or client, and wait for the dashboard to show ready.

Voice satellite Thalovant Voice Native macOS, Windows, and Linux app that installs compatible HiveMind voice packages, writes identity, and starts the satellite.
Headless Linux SSH-friendly install Use the dashboard-provided shell command to install the AppImage wrapper, register thalovant:// links, and pair.
Web and developer Copy the setup link Use the same setup URL for webchat, embedded clients, or provisioning tools that claim a one-time identity.

Runtime

Hubs route clients; runtime groups run the assistant brain.

Private workspaces use owned hubs and OVOS runtime groups to keep routing, runtime configuration, inventory, release posture, and GitOps output connected.

Hubs Routing units Public or private hubs connect clients to assistant runtime with visibility, locking, managed domains, and ownership.
Runtime groups OVOS bundles Runtime groups track managed images, persona config, storage, live bus sync, skill inventory, and release state.
GitOps Kubernetes output Render hubs, clients, ACLs, and runtime groups to tenant-scoped CRDs and inspect diffs or drift.

Skills

Assistant capabilities are packaged, sourced, billed, and observed.

Thalovant skills keep the conversational layer separate from provider services, so public hubs and private workspaces can share a consistent capability model.

First-party skills Source Scout, Local Pulse, Ops Copilot Public-hub skills for source-backed answers, local planning, and read-only Kubernetes/GitOps/runbook help.
Service-backed skills Weather, News, Joke Garden OVOS skills stay conversational while Go services handle provider calls, caching, metrics, alerts, previews, and fallbacks.
Marketplace Included and paid add-ons Catalog entries carry source refs, support level, compatibility, billing SKU, featured state, and runtime inventory context.

Operator checklist

A concise readiness check before production use.

Use this as the first internal runbook shape while the deeper API reference is being assembled.

Production readiness 
Workspace
- Account created and verification path complete
- Plan posture reviewed for public, private, team, or metered capacity
- Billing visibility checked before scaling clients, hubs, runtime groups, or paid skills

Connectivity
- Satellite, web client, developer client, or embedded client paired through setup link
- Public or owned hub route selected and visible in topology
- Runtime group assigned when private assistant infrastructure is active

Governance
- ACL policy attached to client, hub, and assistant behavior scope
- Namespace and tenant boundaries reviewed
- Admin, billing, plan, and GitOps changes auditable

Operations
- HMAC watcher telemetry flowing
- Runtime skills staged, stable, or intentionally alpha
- GitOps drift checked
- Audit trail, billing posture, and usage visible

References

Start from the surface that matches your next task.

These links keep the documentation connected to the current product routes.

Create an account Request access and begin workspace setup. Satellite downloads Prepare the voice edge path for paired assistant devices. Explore public hubs Review public assistant hubs before creating owned routing units. Open console Return to dashboard, topology, runtime skills, policy, audit, and billing.