Skip to main content

Platform

The architecture behind the three environments

One parent brand, one Core, consistent authentication, a common organization model, several business modules.

Overall system architecture

A unified platform with a shared foundation and specialized environments. Products depend on the Core, never the other way round.

goobelo.com

Institutional website

app.goobelo.com

Sign-in / Portal

GOOBELO Core

Shared foundation

  • GOOBELO School

    Primary • Lower secondary • Upper secondary

  • GOOBELO Campus

    Universities • Institutes • Grandes écoles

  • GOOBELO Public

    Inspectorates • Academies • Ministries

Control Plane
Can remain centralized at GOOBELO. It does not hold operational school data.
Data Plane
Resides in the infrastructure provided for the client. Isolation and residency governed by the deployment mode.

GOOBELO Core

The shared foundation

Identity, Organizations, Roles, Audit, Billing, Documents, Notifications, API, Analytics and AI: everything that should not have to be rewritten three times.

  • Identity & Access

    Authentication, sessions, account recovery, MFA to come.

  • Organizations

    Client entities: School, Campus, Public or group, with status, country, timezone and currency.

  • Roles & Permissions

    Roles carried by membership of an organization, not by a global profile.

  • Product Entitlements

    Modules enabled per organization and plan limits.

  • Branding & Domains

    Logo, palette, display name, domain or subdomain and branded emails.

  • Audit

    Sensitive events with actor, organization and timestamp.

  • Billing

    GOOBELO subscription, kept distinct from school billing.

  • Documents

    Storage abstraction and access rules.

  • Notifications

    Email and in-app; SMS and WhatsApp only through explicit integration.

  • API & Integrations

    Versioned API, signed webhooks and connectors.

  • Analytics

    Aggregated measurements and authorized reporting.

  • GOOBELO AI

    A layer connected only to explicitly authorized data.

Control Plane and Data Plane

Control Plane

Can remain centralized at GOOBELO. It does not hold operational school data.

  • Licences, plans and versions
  • Module catalogue and configuration
  • Domains and deployments
  • Technical monitoring and support

Data Plane

Resides in the infrastructure provided for the client. Isolation and residency governed by the deployment mode.

  • School and university students
  • Grades, attendance and report cards
  • Payments and documents
  • Establishment data

Domain structure

Example domain architecture.

Domain structure
DomainRole
goobelo.comInstitutional website
www.goobelo.comRedirect
app.goobelo.comSign-in / Portal
admin.goobelo.comAdministration
status.goobelo.comPlatform status

For establishments

For establishments
DomainRole
goobelo.com/schoolGOOBELO School landing page
goobelo.com/campusGOOBELO Campus landing page
goobelo.com/publicGOOBELO Public landing page
goobelo.com/platformGOOBELO Core
establishment-name.goobelo.comSubdomain
gestion.ecole-excellence.snCustom domain

Understand where your data lives

We explain precisely what lives in the Control Plane and what stays in the Data Plane of your establishment.

Request a demo