Get access
Platform How it works API FAQ Get access
Theme
Onboarding open

Entitlement as a service

Aurem sits between users and digital content. It authenticates identity, checks entitlement, issues opaque tokens and routes every decision through one API.

Request access See how it works
  • Card data never stored
  • Opaque tokens
  • Own checkout, coming soon

Platform

One layer between the user and the content.

Aurem does not host content. It decides who is entitled to see it, and answers that question the same way every time.

Authentication

A single identity layer across every connected experience.

Entitlement

A standardised access status: active, tier and expiry.

Tokenization

Opaque tokens abstract identity and access state away from the platform.

Routing

Access decisions are enforced before content is delivered.

How it works

From checkout to verified access.

Four steps. No per-platform integration on your side.

  1. 01

    Redirect in

    The media site sends the user to Aurem with a site ID and the requested tier.

  2. 02

    Checkout

    The user completes checkout in a single step. Payments are handled by our payment processors.

  3. 03

    Entitlement

    Aurem records the entitlement and issues an opaque token bound to that site.

  4. 04

    Verify

    Your backend calls /verify and receives one standard answer.

API

One endpoint. One answer.

Point your backend at a single URL. Aurem absorbs the per-platform logic and returns a normalised entitlement: active or inactive, tier, expiry.

  • Single call: GET /verify?token=…
  • CORS restricted to your allow-list
  • Opaque tokens, so no platform details leak downstream
Request access
verify.sh 200 OK 
# one request, one decision
$ curl https://auremapp.com/verify?token=aurem_9f2c

{
  "active":  true,
  "tier":    "premium",
  "site":    "MediaSite",
  "status":  "active",
  "expires": "2026-11-21 00:00:00"
}

Discretion

Built for private platforms.

Card details are handled by our payment processors. Aurem keeps only the entitlement and an opaque reference.

Card data never reaches our database

Card numbers, billing addresses and payment credentials are processed by our payment processors. Aurem does not store any of that data.

Neutral membership aliases

A site can be configured to appear under a neutral alias in a customer's membership list, keeping the platform and the billing statement separate.

FAQ

Common questions

What is Aurem?

An entitlement access gateway that sits between media sites and their users. It handles authentication, entitlement verification, tokenization and access routing in a single system.

How is checkout handled?

Checkout runs through Aurem. Card details are sent directly to our payment processors. Aurem does not store card numbers, billing addresses or payment credentials.

Is my card data stored?

No. Card details are processed by our payment processors and never reach Aurem's database. We keep only the resulting entitlement status and an opaque reference token.

Read the full FAQ

Interested in joining?

Aurem is currently available through an onboarding process. Media sites interested in integrating can reach out to our team for access.

Contact us