Features & Properties
Features are the core capabilities you want to control and monetize in MonetizationOS. They provide a stable way to represent entitlement decisions across web, app, and API experiences.
A feature can represent a capability such as reading premium articles, watching video, or using an AI tool. Feature properties then define how that capability is delivered for a specific user or context.
Articles
A monetizable content type defined by your development team
Why features matter
Features separate business intent from implementation details. Instead of hard-coding entitlement logic in each application, you define capabilities once and evaluate them consistently at decision time.
This model helps teams:
- Package access levels cleanly through plans
- Adjust delivery with property values (for example, limits, quality levels, or toggles)
- Add runtime logic with workflows without reworking core configuration
Feature Properties
Feature Properties are configurable attributes that let you control how users experience a feature. They allow you to define different dimensions of access - for example, a Video Content feature might have properties for video resolution (HD vs 4K), ad frequency (with or without pre-roll ads), or download permissions. These properties give you the flexibility to test different monetization strategies and optimize the user experience.
Features, properties, and workflows
A feature answers what capability a user can access.
Feature properties answer how that capability is delivered.
Feature workflows can override property values during access checks and surface decisions, allowing contextual behavior based on identity, request data, or external systems.
Learn More
Getting Started guides
References
API references
Perform Surface Decision
Compute surface and component behavior with feature data.
Perform Access Check
Evaluate feature entitlements for a request.