mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-13 16:54:48 +00:00
Uncap grandfathered lifetime entitlements
This commit is contained in:
parent
0a71db8b35
commit
b84e4067e8
10 changed files with 124 additions and 13 deletions
|
|
@ -7,7 +7,7 @@ For the canonical, code-aligned entitlement table (including internal tier names
|
|||
|
||||
## Plan Mapping (User-Facing -> Code Tiers)
|
||||
|
||||
Pulse uses capability keys (for example, `ai_autofix`) to gate features at runtime. Those capabilities are bundled into internal tiers in `internal/license/features.go`.
|
||||
Pulse uses capability keys (for example, `ai_autofix`) to gate features at runtime. Those capabilities are bundled into internal tiers in `pkg/licensing/features.go`.
|
||||
|
||||
User-facing plans map to internal tiers as follows:
|
||||
- **Community**: `free`
|
||||
|
|
@ -17,7 +17,7 @@ User-facing plans map to internal tiers as follows:
|
|||
- **Cloud**: `msp` or `enterprise`
|
||||
|
||||
Notes:
|
||||
- `lifetime` keeps the same runtime entitlements as Pro.
|
||||
- `lifetime` keeps the same runtime feature set as Pro, but grandfathered lifetime entitlements are uncapped for monitored systems and guest access.
|
||||
- Items marked **Cloud*** require the `enterprise` tier rather than the base `msp` tier.
|
||||
- If you are self-hosting, you can use capability keys and `GET /api/license/features` to discover exactly what is active in your instance.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue