Billing and Plans

Billing shows what your plan allows right now.

Start here when a button is locked, disabled, or says upgrade required. Many blocked actions are plan or usage questions, not broken setup questions.

Billing is the source of truth for exact allowances: owned hubs, private skill setups, runtime operations, hub release operations, client connections, hub addresses, paid Skill Store access, and help options.

Some readers call this a billing wall, can’t add problem, plan gate, or upgrade required state. Check Billing before changing setup.

If you are just starting, Free Tier explains the smallest path: public hubs, one connection, narrow permissions, and Billing when a button is locked.

Daily Desk follows the same plan ladder. The public Daily Desk demo is memoryless. A Private workspace is the first self-serve upgrade path for Daily Desk memory, analytics, clients, and private skills. Team is for shared operations. Paid vertical pilots are scoped separately with Thalovant when a real workflow needs hands-on packaging.

Start Here If

• a button is locked or disabled;
• a message says upgrade required;
• you cannot create a hub or cannot add another connection;
• runtime updates, hub updates, or private skill actions are unavailable;
• hub addresses, paid Skill Store entries, or Live Map access are unavailable;
• you need to separate a plan limit from a setup problem.

Billing shows plan limits, hub addresses, skill access, and help options before a limit blocks you.

What Billing Shows

Limits

How many hubs, skills, clients, permissions, and daily uses your plan allows.

Runtime

Whether private skill setups, runtime config, skill updates, and runtime updates are available.

Hub updates

Whether owned hub capacity is available for hub creation and hub release operations.

Hub addresses

Whether custom hub addresses are available.

Skill Store

Whether paid Skill Store access is available for the workspace.

Help options

The help choices available for your plan.

Common Plan Effects

Private skill setups means your plan includes space for your own skill groups and shared runtime settings. In plain language, it is what lets your workspace run hubs with their own skills instead of only using public hubs.

Plan item	Why it matters
Owned hubs	Needed to create and run private workspace hubs.
Runtime slots	Needed when private hubs need their own skills and runtime config.
Private skills	Needed when your own hubs need custom skill groups.
Client limit	Controls how many client connections can be created.
Policies	Controls how many access policies can govern clients and hubs.
Daily intents	Controls daily live hub intent previews and usage.
Hub addresses	Allows custom hub addresses for the workspace.
Public hub listing	Allows hubs to appear in discovery.
Paid Skill Store access	Shows whether the workspace can use paid entries if they are offered.
Live Map	May depend on owned hubs or private workspace features.

Free Path vs Workspace Path

Path	Good for	Usually includes
Free path	Learning, trying public hubs, and creating a simple connection.	Public hub discovery and an included connection allowance.
Workspace path	Running owned hubs and private skill setups.	Owned hubs, private skill setups, runtime and hub update access, hub addresses, more connections, and help options.

Daily Desk Offer Map

Use this map when a Daily Desk or showroom action sends you to Billing.

Buyer step	Plan or offer	What it means
Try Daily Desk	Free	Public Daily Desk is available as a memoryless proof surface.
Create private workspace	Private	Private Daily Desk can use workspace memory, analytics, private skills, clients, and runtime capacity.
Share operations	Team	Several people, hubs, runtimes, and client groups can use the same workspace with priority support.
Package a workflow	Paid pilot	Office, clinic, hospitality, developer, or private edge workflows are scoped with Thalovant outside self-serve checkout.

Note

Paid pilots are commercial engagements, not a Billing plan switch. Billing still controls the workspace plan, limits, payment status, and checkout path.

Context Banners

If you land on Billing from a locked button or page, Billing explains why. For example:

• owned hubs require room for owned hubs;
• private skill groups require the right plan;
• runtime config requires private skill setups;
• runtime updates require runtime capacity;
• hub updates require owned hub capacity;
• more connections require room for more client identities;
• paid Skill Store entries require a plan that explicitly includes them;
• Live Map may require a plan that includes owned hubs.

Read a Plan Gate

When a page sends you to Billing, read the gate in this order:

1. Action: what is unavailable right now.
2. Current limit: whether the workspace has reached a limit.
3. Plan path: whether the action needs a different plan.
4. Status: whether the status page shows a wider incident.
5. Help options: where to ask if the limit does not match what you expect.

This keeps plan questions separate from setup questions. If the plan allows the action but it still does not work, return to the page you came from and read the status message.

Example Plan Questions

Use the locked button scenario when you need to decide whether a blocked action is a plan limit or a setup issue.

Use Free Tier when you want the no-surprises route before choosing a private workspace plan.

Tip

Use Billing before a limit blocks you. It is easier to plan a workspace when limits, hub addresses, and help options are visible up front.

Billing Is Clear When

Billing is clear when you know:

• which plan you are on;
• which limit or feature affects your next action;
• whether current usage has reached that limit;
• whether help options are available for the question;
• which page to return to after the plan check.