Media and subscription platforms
Streaming and subscription products need identity that understands a household, a device limit and a plan. LumoAuth models households as relationships, limits sessions per account, and makes the subscription tier an attribute your access rules can use.
Shared accounts, too many devices, the wrong region
A family shares one login; a password leaks to a hundred people; content licensed for one country plays in another.
How LumoAuth solves it
Households and profiles
Relationships model "member of household" with per-profile permissions. Docs
Session and device limits
Concurrent session caps, device lists, remote sign-out. Docs
Tier as an attribute
An attribute policy reads the subscription tier and the region on every check. Docs
Anonymous to subscribed
Magic link or social sign-in at the paywall; passkey afterwards. Docs
Downstream content APIs
Token exchange gives the player a token limited to the content API. Docs
Setting it up
Enable session limits
Sync the subscription tier as a user attribute
Write the geography and tier policy
Standards involved
Plain names on the left, the specification on the right. The full map is in the standards reference.
- Token exchange
- RFC 8693
- Authorization API
- OpenID AuthZEN
Which plan you need
Sessions and roles are on every plan. Attribute rules and relationships are the Fine-grained authorization add-on.
Documentation
Ship passwordless sign-in this week. Put guardrails on your agents today.
The Developer plan is free for 10,000 monthly users and ten agents, with no card. Everything speaks open standards, so moving in or out is a config change.