Skip to content

e10s

e10s is an entitlements platform for SaaS vendors. You define features and plans; your customers (subscribers) get access. Your app asks e10s whether a subscriber may use a feature — and, for limits, how much they are entitled to.

Who it’s for

You sell a product with packaged capabilities. Different customers get different features and limits — self-serve tiers, enterprise deals, trials, comps. e10s owns that packaging and the runtime check.

It is not a billing system, usage meter, or credit wallet. Your app still counts seats used; e10s answers “how many seats is this subscriber entitled to?”

Core ideas

Concept Meaning
Organization Your vendor account. Your catalog and subscribers live here.
Feature A catalog key: flag (sso) or limit (seats).
Plan A named set of grants — catalog (self-serve) or custom (sales).
Subscriber Your customer — the subject of entitlements.
Subscription Links a subscriber to a plan.
Override Per-subscriber absolute value outside the plan (flag or limit).
Entitlement The resolved answer for one feature right now.

How checks work

Your backend calls e10s with a service account member API key and a subscriber_id:

POST /api/organizations/{organization_id}/subscribers/{subscriber_id}/entitlements/check
X-API-Key: e10s-mk-1-…

{ "feature": "sso" }

{ "feature": "sso", "kind": "flag", "allowed": true, "source": "plan" }

Limits:

{ "feature": "seats" }

{ "feature": "seats", "kind": "limit", "limit": 10, "source": "plan" }

limit: null means unlimited. End users of your product do not call e10s directly.

Resolution order

For a given subscriber and feature:

  1. Override — if a non-expired override exists, use its value
  2. Plan — if the active subscription’s plan grants the feature, use that grant
  3. None — flag denied / limit 0

Next