Current Free limits and the planned launch catalog.
Free
$0/month
- Currently enforced: 500 managed records
- Currently enforced: 1 program · 5 territory nodes
- Currently enforced: hierarchy depth 2
Starter
$99/month
- Planned launch limit: 5,000 managed records
- Planned launch limit: 3 programs · 25 territory nodes
- Planned launch limit: hierarchy depth 3
Growth
$249/month
- Planned launch limit: 25,000 managed records
- Planned launch limit: 10 programs · 150 territory nodes
- Planned launch limit: hierarchy depth 5
Scale
$599/month
- Planned launch limit: 100,000 managed records
- Planned launch limit: 25 programs · 500 territory nodes
- Planned launch limit: hierarchy depth Configured
Custom
Quote
- Planned launch limit: Over 100,000 managed records
- Planned launch limit: Negotiated programs · Negotiated territory nodes
- Planned launch limit: hierarchy depth Configured
The planned annual totals equal ten monthly payments. No paid charge can be created from the current deployment.
What the current Free runtime enforces.
Public early-access workspaces are limited to 500 managed CRM records, one ownership program, five territory nodes, and a maximum hierarchy depth of two. Those limits are enforced by the running service, although the current public ZIP editor creates flat, top-level territories only. Newly eligible records beyond the managed-record limit enter a visible plan_limit state and receive no desired owner or write.
Compare current Free limits with planned paid tiers.
| Limit | Free | Starter | Growth | Scale | Custom |
|---|---|---|---|---|---|
| Managed CRM records | 500 | 5,000 | 25,000 | 100,000 | Over 100,000 |
| Programs | 1 | 3 | 10 | 25 | Negotiated |
| Territory nodes | 5 | 25 | 150 | 500 | Negotiated |
| Hierarchy depth | 2 | 3 | 5 | Configured | Configured |
| Planned annual total | $0 | $990 | $2,490 | $5,990 | Contract |
| Planned audit-retention entitlement (not live) | 7 days | 90 days | 1 year | 2 years | Contractual |
| Planned workspace-access entitlement (not live) | 1 editor; unlimited viewers | Unlimited editors, publishers, and viewers | Unlimited editors, publishers, and viewers | Unlimited editors, publishers, and viewers | Negotiated |
| Current availability | Free early access; no purchase | Not purchasable | Not purchasable | Not purchasable | Not purchasable |
Only the Free values labeled currently enforced describe today's runtime. Starter, Growth, Scale, and Custom values are the approved launch model, not purchasable or active entitlements. The launch design includes one rollback per month on Free; that monthly quota is not currently metered or enforced.
What counts as a managed record?
A managed record is one unique HubSpot record covered by an active TerritoryLogic ownership program in that portal. Companies, contacts, deals, tickets, leads, and qualifying custom objects are counted by their object type and record ID. The same record is counted once if more than one future overlay evaluates it.
What happens at a limit?
Existing managed records continue to be evaluated. Newly eligible records beyond the limit enter a visible plan_limit state and receive no desired owner or write. TerritoryLogic does not create automatic overage charges.
What happens on a future downgrade?
A downgrade must not silently choose which programs survive. Enforcement pauses until an Account Owner selects a configuration within the new limit. Binding billing terms will be published before paid checkout opens.
Paying will not make an unfinished feature available.
The current early-access engine supports companies, contacts, deals, tickets, leads, and qualifying custom objects with a per-program ZIP-property mapping and fixed owners. Exact U.S. ZIP5 is authoritative; explicit whole-state fallback can use normalized city/state only when ZIP is missing. Activities, round robin, weighted pools, advanced criteria, custom polygons, and association-derived locations remain outside the public release even if future entitlements appear in internal plan design.