Skip to content

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.

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. On every gated action, check entitlements for that subscriber
  6. Sales deals: custom plan and/or overrides without breaking the model

Actors

Actor Role
Vendor admin Someone on your team. Manages the organization, service accounts, and API keys at e10s.io.
Vendor backend Your servers. Calls the API with a service account member API key (catalog, subscribers, checks).
Subscriber end user Uses your product. Does not call e10s directly.

What e10s does not own

  • Charging cards, invoices, tax
  • Usage (how many seats are filled, bytes stored, API calls this month)
  • Login for your customers’ end users
  • Fine-grained resource ACL inside a subscriber (documents, rows, …)

Those stay in billing or your app. e10s returns the entitled amount; you compare to local usage.