Home Plan Developers
What developers get on the Home and Family plans, the personal-use terms, the token and rate limits, and when to move to a Work plan.
Use this page if you build on Thalovant from a Home or Family plan: a script for your kitchen hub, an MQTT sensor, an agent that manages your household devices, or a skill you write for yourself.
The Home line keeps full developer access to your own hubs. You get the same API, SDKs, MQTT, and MCP server as Work plans. What changes is the scale, and what you may do with the result. This page lists the scopes your plan can grant, which locked developer features belong to the Work line, and where a personal project ends and a commercial one starts.
What You Get
Section titled “What You Get”| Tool | Home and Family |
|---|---|
| API tokens | Every standard scope, including hubs:write, listed explicitly on the plan. |
| SDKs | All managed SDKs against your own hubs. |
| MQTT | Your own devices and sensors on your own hubs. |
| MCP server | Discovery, provisioning, runtime, hub skill, and memory tools on your own hubs. |
| Provisioning | Create and release hubs and runtime groups up to your plan’s hub count. |
| Your own skills | Install skills you write on your own runtime groups. |
Home and Family Limits
Section titled “Home and Family Limits”| Limit | Home | Family |
|---|---|---|
| Owned hubs | 1 | 2 |
| Runtime groups | 1 | 2 |
| Client connections | 5 | 12 |
| Access rules | 10 | 10 |
| Intents per day | 300 | 1,000 |
| Active API tokens | 5 | 10 |
| Token rate | 120 a minute | 240 a minute |
| Token calls per day | 20,000 | 60,000 |
| Token calls per month | 400,000 | 1,200,000 |
| Runtime resources | Fixed size | Fixed size |
| Memory items | Unlimited | Unlimited |
Over a token limit, calls return HTTP 429 with a Retry-After header. Over a plan limit, such as a sixth device on Home, calls return HTTP 403 with the code plan_limit.
What Stays on the Work Line
Section titled “What Stays on the Work Line”These features are not available on any Home plan, even from code:
- listing a hub in the public catalogue;
- custom hub addresses on your own domain (Home and Family get a managed address);
- approved browser SDK origins for web apps served from your own site;
- autoscaling hubs and tunable runtime resources;
- staff invites, apart from Family’s one extra adult login;
- invoices.
A browser app on the Home line cannot use an approved SDK origin. Run it from a server or device you control, or move to a Work plan. See SDK origins.
Personal Use Only
Section titled “Personal Use Only”Home plans are for personal and household use. Build whatever you like for yourself and the people you live with.
Use a Work plan when the project serves a business, customers, visitors, or the public. That includes selling access to a hub, running a hub for a shop or an office, or offering a skill as a paid service. The Terms of Service and the End User Licence Agreement hold the exact rules.
Check Your Setup
Section titled “Check Your Setup”Your Home developer setup is ready when:
- your token carries only the scopes your script needs;
- the script acts on your own hub and stays within its daily intent allowance;
- nothing you build serves a business or the public;
- you know Billing is where the Work line starts if you outgrow the Home line.