Rules
Define what to watch for and what happens when conditions match. Rules are evaluated in real-time against every stream event, giving you fine-grained control over your media server access policies.
Common Uses
- Limit concurrent streams per user or household
- Detect account sharing through geographic anomalies
- Restrict transcoding for specific users or devices
- Block access from certain countries or IP ranges
- Enforce quality limits based on network or device type
- Send notifications when specific events occur
How Rules Work
Each rule consists of conditions that define when it triggers and actions that define what happens.
Conditions
Conditions are evaluated against stream metadata. Multiple conditions are combined with AND/OR logic.
Actions
Actions execute when all conditions match. Multiple actions can run for a single rule.
22 Conditions Across 6 Categories
User & Account
- User
- User Group
- Email Domain
- Account Age
Location & Network
- Country
- City
- IP Address
- IP Type
- Impossible Travel
Playback
- Concurrent Streams
- Media Type
- Library
- Resolution
Device & Client
- Device Type
- Client App
- Platform
Server & Performance
- Server
- Transcode Decision
- Video Codec
Time & Schedule
- Time of Day
- Day of Week
Examples
Common rule configurations to get you started.
Household Stream Limit
Allow up to 3 concurrent streams per user. Additional streams are terminated with a friendly message.
No Transcoding for Remote
Remote users must direct play. Transcoding streams are stopped to preserve server resources.
Impossible Travel Alert
Flag when the same account streams from two distant locations within an hour.
Country Whitelist
Only allow streams from approved countries. Useful for content licensing compliance.
Ready to set up your rules?
Check the documentation for detailed guides or get started with the GitHub repository.