Keep software packages and service tiers in one catalogue
Software companies, AI platforms and cloud providers package application features, model access and hosted services. When each product has its own access rules, package changes spread across integrations. Keep their features, limits and allowances in a versioned catalogue.
Explore the exampleAccess rights
- Export to PDF
- Included
- Source: Inherited from Pro, version 1
- Single sign-on
- Included
- Source: Added in Team, version 1
Configured limits
- Support response time
- 24 hours
- Source: Inherited from Pro, version 1
- Workspace seats
- 20 seats
- Source: Team, version 1; overrides Pro’s 5 seats
Team inherits Pro’s unchanged features and keeps its own seat limit and single sign-on.
Explore software examples
Change an inherited feature and preserve a custom limit
Team inherits from Pro but overrides its seats and adds single sign-on. Change Pro’s support response time, then decide whether Northstar keeps its earlier agreement or receives Team’s new version.
Step 1 of 4: Read Team’s feature sources
See the inherited features alongside Team’s own seat limit and single sign-on.
DevelopmentTestDevelopment is a test environment: test money and sample customers only.
Access rights
- Export to PDF
- Included
- Source: Inherited from Pro, version 1
- Single sign-on
- Included
- Source: Added in Team, version 1
Configured limits
- Support response time
- 24 hours
- Source: Inherited from Pro, version 1
- Workspace seats
- 20 seats
- Source: Team, version 1; overrides Pro’s 5 seats
Team inherits Pro’s unchanged features and keeps its own seat limit and single sign-on.
Feature types across software and technology products
These are separate illustrative products. Each row names its plan: application access, AI capabilities and hosting services can each combine feature switches, configured limits and usage allowances.
| Feature | Type | Plan value |
|---|---|---|
| Team: Single sign-on | On or off | Included. Added in Team, version 1 |
| Team: Workspace seats | Configurable | 20 seats. Team, version 1; overrides Pro’s 5 seats |
| Builder: Premium model | On or off | Not included. Not included in Builder |
| Builder: Maximum context | Configurable | 32,000 tokens per request. Builder, version 1 |
| Cloud team: Automated backups | On or off | Not included. Not included in Cloud team |
| Cloud team: Backup retention | Configurable | 0 days. No backup service subscribed |
| Pro: Report exports | Metered | 100 exports per period. Pro, version 1 |
| Builder: Generation credits | Metered | 10,000 credits per period. Builder, version 1 |
| Cloud team: Compute hours | Metered | 1,000 hours per period. Cloud team, version 1 |
More situations your team can handle
A company needs its own package
One customer needs Team with a different seat limit. Create a plan based on Team and override the limit, while retaining its unchanged features.
Explore custom packagesAn earlier promise must survive a launch
A new public tier removes a feature an earlier cohort was promised. Preserve that cohort’s plan version when releasing the new terms.
Explore plan versionsA new model is a paid capability
The premium model should appear only for entitled customers. Define an access feature and package it in a compatible plan or add-on.
Explore feature upgradesA contract needs a larger context window
An enterprise integration needs a different per-request maximum. Use a configurable feature value in a contract plan or an individual grant of a higher limit.
Explore negotiated limitsPrivate networking is a paid option
A service is available only on selected plans. Model it as an access feature and use compatible add-ons or tier changes to enable it.
A contract needs longer retention
One customer requires a different backup retention period. Set the configurable retention value in a custom package instead of changing the shared plan.
Explore contract packages
Questions about software and technology
More solutions
Explore all solutions, organised by team, company size, industry and use case.
Try your plans in Entitler
Start with sample plans and customers. Then try a change you expect to make, such as a new tier, a usage allowance or an exception for an early customer. Request an invite to try it with your team.