Railbase for Education
Education Suite for school operations, library, learning, migration and a role-aware native mobile app.
Updated
One private education estate
Education Suite runs on the institution's Railbase instance and Vault. The shared education shell discovers only installed, licensed capabilities; School owns academic operations, Library owns catalog and circulation, and LMS owns courses, progress and certificates. Connector provides preview/apply/rollback migrations for existing institutions.
The suite is sold as one plan while its plugins remain independent Marketplace products:
- Basic: Education shell, School and one controlled migration project.
- Pro: Basic plus Library and three migration projects.
- Max: Pro plus LMS and ten migration projects.
Native iOS and Android companion apps
The native apps connect to an institution by QR, deep link, managed profile or manual HTTPS URL. Users sign in to that Railbase instance, choose an accepted workspace and register the device through the capability registry. Tokens and offline caches are isolated by organization, tenant and user.
The mobile home is role-aware:
- learners receive Digital ID, schedule/check-in, library, progress and inbox;
- parents select an actively linked child before seeing published grades or attendance;
- teachers receive lesson, attendance and grade-entry tools within backend-enforced assignments;
- librarians receive camera scanning and an offline inventory queue.
The offline Digital ID is a signed rbid1 presentation with an explicit stale or
expired state. It is never a bearer API token. Offline inventory scans may queue;
access, attendance, checkout and return always require a backend decision.
Greenfield and existing-institution launch
The Education shell has an idempotent Setup action that creates the instance profile,
role-aware module registry and bounded launch checklist without direct database
edits. Setup returns the exact tenant-safe manifest URL and mobile connection URI
for a QR/deep link. A multi-organisation server uses the opaque instance_id in
that URL; it never exposes or trusts a tenant id before login. School keeps its
private Digital ID signing key plugin-scoped and sends Education only the public
verification half through a declared tenant-bound event. Existing institutions use Connector preview/apply workflows and guarded
rollback for School roster/grades/attendance, Library catalog/copies and LMS
enrollments.
The greenfield acceptance path installs the shipped bundles through the production plugin runtime and verifies manifest discovery, device lifecycle, signed Digital ID, school identity, attendance, grades, library availability, holds, material requests and negative RBAC.
Compare Education Suite plans or browse its component plugins.