vrr/Pulse
2
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-07-10 00:14:38 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 8

Add the dormant Business tier to the licensing core

Browse source 
TierBusiness: Pro's feature set, 365-day history retention, uncapped
core monitoring like every self-hosted tier, Business display name, and
a slot in the min-tier ordering. Differentiation is by max_users limit,
retention, and support rather than features (multi-user is already a Pro
capability via RBAC; see specs/pricing-segmentation.md binder findings).
Dormant until the license server issues business plan versions; no
checkout, pricing, or UI surface references it yet. Contract shape
recorded as cloud-paid Extension Point 26 and pinned by
TestBusinessTierContractShape.
This commit is contained in:
rcourtman 2026-07-08 16:02:56 +01:00
parent a205ba3498
commit fca5975c38
4 changed files with 61 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/release-control/v6/internal/subsystems/cloud-paid.md
View file

@ -1034,6 +1034,22 @@ hands-on Patrol modes, issue investigation, verified fixes, and longer history`.
Landing behavior for paid and hosted shells must also defer to the
frontend-primitives-owned provider-first landing contract instead of
defining a cloud-paid-specific order.
26. Introduce the self-hosted `business` tier only through this shape:
`TierBusiness` in `pkg/licensing/features.go` carries exactly the Pro
feature set (no feature-level differentiation), 365-day history
retention in `TierHistoryDays`, membership in the self-hosted
core-monitoring-uncapped tier and plan-version sets (`business`,
`business_annual`), the `Business` display name, and a slot between Pro
and MSP in the min-tier ordering. Business differentiates commercially
by the `max_users` license limit (unlimited for Business; newly issued
Pro licenses may carry a finite `max_users` while previously issued
licenses keep their unlimited posture), retention, and support, never
by gating features away from Pro. The tier stays dormant until the
license server issues business plan versions through a governed
rollout; no checkout, pricing-model payload, public pricing page, or
in-product plan surface may reference Business before that rollout, and
monitored-system volume stays out of the Business plan model per the
self-hosted commercial boundary above.
## Forbidden Paths