Free Tier

The Free tier is the simplest way to learn Thalovant without creating a private workspace setup.

Use it to browse public hubs, create one focused connection, review permissions, and learn what Billing unlocks when you need more.

Start Here If

• you just created a free account;
• a button says locked, unavailable, or upgrade required;
• you want to try Thalovant before creating your own hub;
• you are not sure whether to start with Public hubs, Connections, or Billing.

At a Glance

Question	Simple answer
Best first move?	Open Public hubs and choose one hub to try.
What can I create first?	One Thalovant Voice connection to a public hub.
Which pages matter most?	Dashboard, Public hubs, Connections, Billing, Profile, and Help.
What stays limited?	Owned hubs, private skills, SDK Origins, runtime operations, more connections, analytics, and advanced live views.
Where do locked buttons lead?	Billing explains whether the limit belongs to the plan.

The Free Path

1. Open Public hubs. Pick a listed hub with clear starter prompts.
2. Try the browser preview when available. Use one starter prompt before creating anything.
3. Create one voice connection. Let the setup link pair Thalovant Voice to the public hub.
4. Keep permissions narrow. Use the recommended question-style access first.
5. Check Dashboard. Confirm the connection appears and nothing unexpected needs attention.
6. Open Billing when something is locked. Billing tells you whether the action needs a different plan.

This path teaches the same loop you will use later: hub, connection, permissions, health check.

What Free Is Good For

Learning the model

Learn hubs, connections, permissions, Dashboard, and Help without designing a private setup.

Trying public hubs

Use shared hub listings and starter prompts before deciding what you want to build.

Testing one voice connection

Pair one Thalovant Voice client to understand setup, permissions, and health checks.

Finding the upgrade moment

Let Billing explain when private hubs, more capacity, or managed features become useful.

What Usually Needs a Workspace Plan

Need	Why Billing matters
Create your own hub	Owned hubs use workspace capacity.
Add more connections	Connection count is plan-limited.
Use private skill sets	Private skills need runtime capacity.
Change runtime defaults	Runtime operations belong to workspace plans.
Use custom hub addresses	Address features depend on the plan.
Approve SDK Origins	Browser SDK origin review belongs to workspace plans.
Read analytics or advanced Live Map views	Operational workspace views need owned hub capacity.

If a Button Is Locked

Do not treat a locked button as a setup failure.

1. Read the message beside the button. It usually says what is missing.
2. Open Billing. Check the current plan, limits, and support path.
3. Return to the same page. Continue only if the plan includes the action.

Tip

The Free tier is best when the first setup stays small: one public hub, one connection, one permission set, one health check.

Free Tier Looks Right When

The Free tier path is working when:

• you can explain which public hub you chose;
• one connection is paired to that hub;
• permissions are narrow and easy to read;
• Dashboard shows the expected connection;
• advanced pages stay out of the way until Billing unlocks the workspace path;
• Billing explains any locked action before you change setup.

Next Step

Start with Public hubs if you are exploring. Open Billing when the thing you want is locked.

Browse public hubsCheck Billing