Concepts overview

e10s models who can use what (and how much) inside your product. Everything is scoped to your organization (your vendor account). Organizations never share catalog or subscriber data.

What e10s is not: Who it’s for.

Model

Organization (you, the vendor)
├── Features[]                 # flag | limit keys
├── Plans[]                    # catalog | custom
│     └── grants[]             # feature + value
└── Subscribers[]              # your customers
      ├── Subscription → Plan  # active assignment
      ├── Overrides[]          # optional absolute values
      └── Entitlements         # computed at read time

Lifecycle (typical)

1. Define features your product can gate on (flags and limits)
2. Build catalog plans (Free, Pro, Enterprise) with grants
3. Create a subscriber when a customer signs up in your app
4. Create a subscription to a plan
5. Check entitlements from your backend — live check, snapshot, cache, or a mix. Check access
6. Sales deals: custom plan and/or overrides

Pack 1–4 in the console or via the API. Step 5 uses a member API key from your backend.

Actors

Actor	Role
Vendor admin	Someone on your team at e10s.io.
Vendor backend	Your servers. Calls the API with a member key.
Subscriber end user	Uses your product. Does not call e10s.

Related

• Features · Plans · Subscribers
• Subscriptions · Overrides · Entitlements