Plans & limits
Latch Vector is priced by what you register, not who logs in. The metered unit is the application set — one registered application (audience) = one application set. Users, organizations, tokens, and logins are not capped.
Plans
| Plan | Application sets |
|---|---|
| Team | 1 |
| Scale | 3 |
| Regulated | Unlimited |
The Regulated tier also unlocks two things neither lower plan includes, each
gated independently and each Contact us to enable it until it is:
- White-labeling — mark an organization as its own tenant while it stays in your tree, and brand it with your reseller's own name, logo and mail sender.
- Custom token claims — add your own claim names to every access token, for a front end still written against another identity provider's shape.
How the cap is enforced
The cap is enforced server-side, so it can't be bypassed by the API, the SDK, or the Swagger console:
- Registering an application checks the cap first. Over the cap →
HTTP 402
plan_limit_reachedwith a human-readable message. - A bulk import pre-checks the cap in its dry-run, so an over-cap import is reported before anything is committed.
- Existing applications are never deleted on a downgrade — they are grandfathered; you simply can't add more until you're back under the cap.
Your usage is visible in the console: an “N of M application sets used” bar and a ring of used vs remaining.
Checking usage in code
await mgmt.applications.quota(orgId); // { used, limit } (limit null = unlimited)
Changing plans
A downgrade to a smaller plan is only allowed when your current usage fits the target plan's cap. If you're over it, remove enough applications first — the request is refused with a clear message telling you how many to remove. Upgrades and same-or-larger caps are never blocked.