A dedicated, rebranded deployment of our interactive reading platform. You choose the name, the look, the domain and the features; we generate, host or hand over an instance that is entirely yours.
Everything below is configurable per instance: branding, domain, feature switches, payments, AI budget, localization and compliance. Each deployment is isolated and updates itself safely.
Run the platform under your own brand
A dedicated, fully rebranded deployment of our interactive reading platform — your name, your logo, your colours, your domain. One configuration file states your brand identity and which features are switched on; the builder resolves dependencies and generates an isolated instance carrying only the code, database, routes and navigation your selected features need.
Configure brand & feature switches
Builder generates your isolated instance
Deploy on your domain, update automatically
Eight independent layers define a white label instance. Each is declared once in the instance configuration and resolved by the builder — nothing ships unless an enabled feature or the base core claims it.
Brand Identity
Display name, logo, favicon, colour palette, font selection and outbound email identity.
Domain & Hostnames
Canonical domain plus additional hostnames. Absolute URLs, cookie domains, OAuth redirects and CORS all key off them.
Feature Switches
On/off per module with automatic dependency resolution and conflict validation before generation.
Database & Migrations
A dedicated instance database and the ordered migration list the schema provisioner applies to it.
Payments & Commerce
Payment providers, methods and currencies, hosted or offline checkout, and the four reader purchase tiers.
AI Budget & Controls
Monthly allowance, non-expiring refill credits, threshold alerts, global toggles, per-book overrides and daily query caps.
Localization
Supported locales, default locale and right-to-left languages, with the UI translated to match.
Compliance & Data
Data residency, consent flows and a full instance export bundle with a manifest and per-file digests.
Every instance is generated the same way and receives the same signed updates. What differs is who operates the infrastructure it runs on.
We run it for you
Your generated instance runs on our managed infrastructure under your own domain. We handle the operations so you can focus on publishing.
On your own cloud
We generate the instance and hand you the artifact tree and database schema. You deploy it on your own server or cloud provider and keep full control of the environment.
Strict data residency
For ministries, universities and institutions that must keep every byte inside their own network. Update packages are transferred manually and verified offline before they are applied.
The same generated platform adapts to very different operators. Each scenario below runs on an isolated instance branded end to end for that audience.
Publisher Storefront
A publishing house sells and streams its own catalog under its imprint, with its own checkout and reader.
University Library
An academic institution offers students a branded reading platform for course texts and reserved titles.
School District
A K-12 district deploys a curriculum reading app across schools under the district brand.
Cultural Ministry
A government body digitizes and distributes national heritage under an official, sovereign brand.
NGO & Nonprofit
An organization distributes books in underserved regions with donor branding and offline access.
Corporate Training
A company runs an internal learning library for staff under its own brand and single sign-on.
The guarantees every white label instance carries, regardless of which deployment model or feature set you choose.