The platform

One platform. Multiple worlds.

A book, a phone, a headset, a classroom display and a cloud that ties them together. Here is exactly how the pieces connect, and what happens when the network does not.

  1. Physical books
  2. Mobile app
  3. Cloud platform
  4. AI engine
  5. Learning analytics
  6. Creator Studio
  7. Immersive experiences

Physical books, mobile app, cloud platform, AI engine, learning analytics, creator studio, immersive experiences. Content flows down the stack. Evidence flows back up.

Seven layers, one experience

  1. Physical books

    The entry point, and the reason this works in places other platforms cannot reach. A printed title needs no charge, no signal and no account. It is also the most trusted object in a classroom. Every page is designed as a trigger, so the digital layer is invited rather than imposed.

  2. Mobile app

    The scanner, the player and the offline store. Content packs download once and run without a connection. The app is built for entry level Android first, with an install size and memory budget set by the cheapest device our schools actually use.

  3. Cloud platform

    Accounts, classes, licensing, content delivery and sync. Schools, teachers, students, parents and administrators each get their own view and their own permissions. Content updates ship centrally without anyone reinstalling anything.

  4. AI engine

    Adaptive sequencing, explanation on demand, and question generation mapped to the curriculum rather than to a general model's guesswork. The teacher sees what the AI told a student, and can correct it. No automated decision sets a child's placement or grade.

  5. Learning analytics

    Time on task, attempts, misconceptions, class-level gaps and term-level progress. Written to be read in five minutes by someone teaching four classes, not by a data analyst.

  6. Creator Studio

    The authoring layer. Teachers assemble lessons from the asset library, add their own media, set assessments and publish to their class. Advanced users build new interactions without writing code.

  7. Immersive experiences

    The output. AR scenes, VR environments, virtual laboratories, interactive stories and classroom displays, all drawing on the same asset library so nothing is built twice.

Placeholder: platform-stack.png, the book, phone, tablet and headset in a line, from above

The constraints we designed around, on purpose

  • Offline first. Full lessons, laboratories and assessments run with no network. Results sync when a connection appears, and nothing is lost while it does not.
  • Low bandwidth. Asset budgets, texture sizes and download packs are set for 3G. A school on a shared mobile connection is our design target, not an edge case.
  • Entry level devices. We test on the cheapest Android in the deployment, not on the newest.
  • Power. Content is cached so a lesson survives an outage mid session, and the tablet is specified for a full school day of use.
  • Local pricing. Charged in naira, VAT inclusive, on school term cycles.

It has to live with what schools already run

  • Curriculum mapping to [the Nigerian national curriculum, WAEC and NECO practicals, and the Kenyan CBC].
  • Export and integration through [SCORM, xAPI, LTI, CSV]. [Confirm which are live today and which are on the roadmap, and label them accordingly. Do not list an unbuilt integration without the word roadmap next to it.]
  • Single sign on with [Google Workspace for Education, Microsoft Entra]. [Confirm.]
  • Bulk import of classes and rosters, with a supported import file and a real human on the first migration.

A classroom is not an advertising market

  • No advertising in any product, at any age, on any tier.
  • No sale, rental or brokerage of student data, and no behavioural profiles built for anyone outside the school.
  • Learner data handled under the Nigeria Data Protection Act 2023, with [hosting arrangement] and published retention limits.
  • The school is the data controller. Schools and parents can inspect, export or delete a learner record, and we act within [X] working days.
  • Role based access, audit logs, and encryption in transit and at rest.
Read our full position on children's data

Build on CR8LAB

Publishers, ministries and partners who want to bring their own content into the platform can do it through our content pipeline today, and through a public API [on the roadmap for [timeframe]]. Documentation, asset specifications and a sandbox are available on request.

    Talk to us about integration

    The fastest way to understand the platform is thirty minutes with it in your hands.

    Book a demo