Create a Hub

Creating a hub adds a new place for clients to connect.

Use this guide when you need an owned hub. If you only want to explore, start with Public Hubs instead.

After creation your hub appears here as a card. Open it to review setup, clients, access rules and health.

Good Defaults

Choice	Good default
Hub visibility	Keep it private unless it should appear in public discovery.
Capacity	Use Standard unless the hub needs to absorb concurrent traffic automatically.
Skill set	Use workspace default skills for the first owned hub.
Runtime	Leave runtime unchanged unless the hub needs different language, location, or speech behavior.
Next item	Create one connection and narrow access rules before adding another hub.

Before You Create

Confirm:

• Billing shows room for another owned hub;
• you know whether the hub should be private or public;
• you know whether the hub needs Standard or Autoscaling capacity;
• you know whether it should use the default skills or separate skills;
• you know whether those skills need different runtime settings;
• you’ve a short name that describes purpose;
• you know whether it needs a custom address.

If you can’t answer one of these yet, pause and open Billing, Skills, or Runtime before creating the hub.

Creation Steps

1. Open Hubs. Select Create hub. If the button is locked, open Billing to review your plan.
2. Name the hub. Use a readable name.
3. Choose public or private. Private keeps it inside the workspace. Public lists it in the shared directory.
4. Choose capacity. Standard is the normal choice. Select Autoscaling only when Billing shows an available autoscaling hub slot.
5. Choose skills. Use workspace default skills for most hubs, or choose separate skills when this hub needs something different.
6. Add discovery details. For public hubs, add description, tags, audience, age guidance, and starter prompts.
7. Review launch settings. Check active state, capacity, public labels, lock state, and final setup.

Choosing Capacity

Standard provides fixed capacity for the chosen skill set. It’s the right default for personal use, normal device traffic, and hubs that don’t need automatic burst capacity.

Autoscaling keeps two workers ready and adjusts capacity as demand changes. This profile answers through installed skills; Persona and general LLM replies aren’t available in this profile.

Billing shows whether your plan includes autoscaling hub slots and the maximum workers allowed for each hub. An inactive Autoscaling hub still reserves its slot. Return a hub to Standard when another hub needs that capacity.

Choosing Skills and Runtime

Use workspace default skills when this hub should behave like most other hubs in the workspace.

Use separate skills when this hub needs a different skill mix, different runtime config, or a slower update pace.

Runtime config belongs to the skill set. Change runtime when you need different language, location, speech, blocked skills, or advanced defaults.

Public Hub Requirements

Public hubs should have:

• a description;
• at least one tag;
• at least one starter prompt;
• appropriate audience guidance;
• age guidance when needed.

Starter prompts must be plain language and should avoid links, email addresses, or markup.

After Creation

Open the hub inspector to review:

• hub address;
• public or private setting;
• clients;
• access rules;
• usage details;
• recent status details;
• public discovery details.

Then create a connection for the hub and set access rules.

If the hub uses a separate skill set, review Runtime before changing runtime config.

What to Do Next

After the hub exists, the next useful action is usually not another hub. Create one connection for the hub, set access rules for that client, then confirm Dashboard and Topology show the relationship clearly.

Hub Creation Is Done When

Hub creation is done when:

• the hub exists with the intended public or private setting;
• the skill set choice is correct;
• the capacity choice matches expected traffic;
• public details are complete when the hub is public;
• the next client is clear;
• Dashboard shows the expected hub count and no unexpected warning.