HEW-NODE-0141 · How Education Works · digital public infrastructure, public digital learning platforms, interoperability, open standards, identity, APIs, content repositories, public digital goods, accessibility, modular architecture, data portability, vendor neutrality, governance and digital education
A country can buy thousands of education apps and still have no digital education infrastructure.
The difference is architectural. Apps solve particular tasks. Infrastructure provides shared foundations that many tasks can use: identity, access, data exchange, content distribution, authentication, standards, public interfaces and common rules.
Digital education becomes infrastructure when schools stop rebuilding the same basic functions separately and begin relying on shared, governed foundations that remain useful across many services.
This node sits beside the How Education Works hub, Education Management Information Systems, Learner Identity & Education Data Interoperability, School Connectivity, Education Cybersecurity & Digital Service Continuity, Open Educational Resources & Open Licensing and School Technology Fleet & Device Lifecycle Management.
Those pages keep their jobs. EMIS owns recurring administrative information systems. Learner Identity owns persistent identity and cross-system data interoperability. Connectivity owns network access. Cybersecurity owns protection and continuity. OER owns content licensing. Device Lifecycle owns endpoints. This node owns the shared digital foundation: how public education systems assemble modular digital components, standards and platforms so content and services can connect without every institution becoming dependent on a separate closed stack.
The 60-Second Read
- Digital infrastructure is not the same as devices or bandwidth.
- A public digital learning platform is not merely a national website.
- Shared identity, standards and APIs reduce repeated integration work.
- Interoperability is a governance decision as much as a technical standard.
- Open standards can reduce lock-in and increase supplier competition.
- Modular architecture makes replacement easier because components can change without rebuilding the whole system.
- Public platforms should support teaching and learning needs before feature accumulation.
- Content repositories are useful when metadata, search, licensing and curriculum alignment are governed.
- Offline access can be part of infrastructure design rather than a patch for poor connectivity.
- Accessibility should be a platform requirement, not left to individual schools.
- Data portability matters when learners or institutions move between systems.
- Public infrastructure can coexist with private providers if interfaces and responsibilities are clear.
- Vendor neutrality does not mean banning proprietary products; it means preventing one vendor from becoming technically unavoidable.
- APIs create reuse but also new security and privacy surfaces.
- Public digital infrastructure needs lifecycle funding, not one-off project funding.
- Governance must define who owns standards, who can connect and who certifies compliance.
- Platform success should be measured by public value and educational use, not login counts alone.
- Exit planning should be designed before a component becomes critical.
- Infrastructure should become easier to extend over time, not more brittle.
- The goal is a digital education ecosystem that can evolve without losing public control.
One-Sentence Definition
Education digital public infrastructure is the governed set of reusable digital foundations, standards and public platforms that allow learning, administration and support services to connect securely and interoperably across institutions and providers.
The First Distinction: Infrastructure Is Not an App
An attendance app can record presence. Infrastructure provides the identity, authentication, school registry and data-exchange rules that allow many attendance apps to work without each one inventing a separate student identity system.
The infrastructure layer becomes valuable because many services can reuse it.
The Second Distinction: Public Platform Is Not State Monopoly
A government can operate a public learning platform while allowing universities, schools, publishers and private technology providers to connect through open standards. Public infrastructure defines common rails; it need not build every train.
The Third Distinction: Interoperability Is Not Data Centralisation
Systems can exchange information without placing every record in one giant database. Interoperability concerns whether systems can understand and use exchanged information under agreed rules. Architecture can remain distributed.
Current International Direction: Modular, Interoperable and Public
UNESCO’s 2026 proposed Charter for Public Digital Learning Platforms argues for modular and interoperable architecture, open standards, open licensing and public control. It explicitly links modularity and interoperability with lower duplication, lower long-term cost and reduced vendor lock-in.
The OECD’s 2025 report Policies for the digital transformation of school education, based on 37 jurisdictions, similarly treats digital education as a system policy problem spanning governance, regulation, procurement, infrastructure, teacher capacity, curriculum and monitoring rather than a hardware programme.
Start With Shared Functions
- learner and staff identity;
- institution registry;
- authentication and permissions;
- curriculum and course metadata;
- content distribution;
- assessment exchange;
- credential verification;
- messaging and notification;
- payment or grant interfaces where relevant;
- analytics interfaces;
- search and discovery;
- accessibility services;
- integration with external learning tools.
Each function should be built once where commonality creates value, rather than copied independently across hundreds of institutions.
Use Stable Identifiers
Systems cannot interoperate reliably if one school identifies a learner by a local admission number, another by email and a third by a vendor-specific account. Persistent identifiers create continuity across transitions while privacy controls determine who can use them.
Use Open Standards Where They Create Real Portability
An open standard is useful when multiple parties can implement it and the specification is available under conditions that permit genuine interoperability. Requiring a standard only on paper is weak if every implementation adds proprietary extensions that recreate dependence.
APIs Are Policy Interfaces
An application programming interface determines which services can connect, which fields they can request, how frequently they can call the system and what happens when the interface changes. API governance therefore shapes competition, privacy and innovation.
Version APIs Deliberately
If a national platform changes an interface overnight, hundreds of connected services can fail. Stable versioning, notice periods, test environments and deprecation rules turn a technical change into a manageable public-service transition.
Modularity Creates Replaceability
When identity, content, analytics and communication are tightly fused into one platform, replacing one function may require replacing everything. Modular architecture allows components to evolve independently while common interfaces preserve connection.
Replaceability Is a Governance Objective
A component that performs well today can become expensive, obsolete or unsupported. The system should be able to replace it without losing years of learner records or shutting down teaching.
Public Digital Learning Platforms Need a Narrow Educational Job
UNESCO’s current platform guidance stresses starting with focused goals. A national platform that begins as a reliable repository of curriculum-aligned materials can create more public value than a feature-rich portal that attempts video conferencing, assessment, social networking, tutoring, credentialing and analytics simultaneously before any one function works well.
Content Needs Metadata
A million resources without reliable metadata become a digital warehouse. Search and recommendation depend on fields such as subject, level, language, curriculum relation, format, accessibility, licence and publication date.
Open Licensing Improves Reuse
When content licences permit adaptation, schools can translate, localise or reformat resources without renegotiating every use. Open licensing does not remove quality assurance; it makes lawful reuse easier after quality has been established.
Offline Architecture Matters
A platform designed only for stable broadband can exclude the very learners public infrastructure is supposed to reach. Offline packages, low-bandwidth modes, delayed synchronisation and downloadable resources can be part of the platform specification.
Accessibility Should Be Systemic
Shared platforms can make captioning, keyboard navigation, screen-reader compatibility, contrast and accessible document standards default requirements rather than optional local improvements.
Interoperability Lowers Switching Cost
If student data, course structures and content libraries can be exported in documented formats, changing vendors is easier. The system gains negotiating power because migration remains possible.
Vendor Neutrality Does Not Mean Technology Neutrality Everywhere
Some functions legitimately require specific technical capabilities. The goal is not to refuse technical requirements. It is to express them in terms of public-service outcomes and interoperable standards where possible rather than writing one vendor’s implementation into permanent infrastructure.
OECD Warns About EdTech Market Concentration
The OECD Digital Education Outlook 2023 notes that repeated procurement from a reduced set of EdTech providers can create vendor lock-in, reduce competition and make alternative tools harder to adopt. The same chapter highlights interoperability, equity and effectiveness as legitimate procurement objectives for digital education ecosystems.
Standards Need a Governance Home
Who approves a data standard? Who decides when it changes? Who certifies suppliers? Who resolves conflicting implementations? Technical standards without institutional ownership can fragment quickly.
Certification Can Reduce Integration Risk
A system may allow vendors to demonstrate compliance against standard interfaces, security requirements and data rules before schools adopt them. OECD’s 2025 review of digital education policy in the Netherlands describes the Edu-V agreements, which establish shared standards and quality labels around secure and reliable data exchange among schools and suppliers.
But Certification Can Also Raise Entry Barriers
If compliance becomes expensive or slow, smaller providers may be excluded even when their products are useful. Requirements should be proportionate to risk and designed with clear testing routes.
Public Infrastructure Needs Sustainable Funding
Initial development attracts grants and political attention. Maintenance, security updates, standards governance, support, accessibility remediation and API continuity are less visible but determine whether the system survives.
Infrastructure should have recurrent funding because it creates recurrent obligations.
Measure Public Value, Not Login Counts
- share of schools connected to common services;
- successful data exchanges;
- time to integrate a new provider;
- service availability;
- accessibility compliance;
- offline use;
- cost of migration;
- supplier concentration;
- percentage of content with reusable licensing;
- teacher and learner task completion;
- support burden;
- security incidents;
- API breakages;
- user outcomes tied to the platform’s actual job.
Do Not Build the Data Lake Before the Use Case
Collecting every possible data field because it may become useful later increases privacy, security and governance burden. Shared infrastructure should enable appropriate exchange without becoming a justification for unlimited central collection.
Case Study: The National Platform That Became a Monolith
Invented example: a ministry commissions one platform for content, attendance, assessment, communication and analytics. Five years later, schools dislike the assessment module but cannot replace it because identity and content access depend on the same proprietary database.
The next architecture separates identity and data exchange from application functions. Competing assessment tools can connect through common interfaces while the public identity layer remains stable.
Case Study: The Open Standard That Was Not Open in Practice
Invented example: every vendor claims support for the national student-data format. Each uses different optional fields and incompatible extensions. Schools still require custom integration.
The authority adds conformance profiles, test suites and certification. Interoperability becomes something suppliers demonstrate rather than declare.
Case Study: Offline First
Invented example: rural schools have intermittent connectivity. Instead of requiring constant login, the public platform allows teachers to download weekly content bundles and synchronise records later. The architecture treats poor connectivity as a design condition rather than user failure.
Failure Modes and Repairs
- App collection mistaken for infrastructure: repair by defining reusable shared functions.
- Monolithic platform: repair with modular components and stable interfaces.
- Interoperability by declaration: repair with testable conformance requirements.
- Vendor-specific standards: repair by expressing public outcomes through open, implementable specifications.
- Feature accumulation: repair by starting with a narrow educational job.
- Always-online assumption: repair with offline and low-bandwidth modes.
- Accessibility delegated locally: repair by making it a platform requirement.
- One-off project funding: repair with recurrent operations and standards-governance budgets.
- Centralise everything: repair by distinguishing interoperable exchange from unnecessary central storage.
- No exit path: repair with portability, data export and replaceability designed from the start.
The Digital Public Infrastructure Operating Chain
- Define the public educational jobs.
- Map shared functions used across institutions.
- Separate shared foundations from application features.
- Define identity and institutional registries.
- Define data minimisation and permissions.
- Select interoperable standards.
- Publish conformance profiles.
- Design APIs and versioning rules.
- Design modular architecture.
- Specify accessibility.
- Specify offline and low-bandwidth behaviour.
- Define content metadata and licensing.
- Create supplier integration environments.
- Certify compliance where proportionate.
- Procure replaceable components.
- Operate shared services.
- Monitor availability and security.
- Monitor integration cost and supplier concentration.
- Review standards as needs change.
- Deprecate interfaces gradually.
- Preserve data portability.
- Fund maintenance and governance recurrently.
- Measure public value.
- Retire obsolete components.
- Maintain continuity while replacements enter service.
Canonical Owner Boundaries
- Education Management Information Systems owns recurring administrative information systems.
- Learner Identity & Education Data Interoperability owns persistent learner identity and data linkage.
- School Connectivity owns network access.
- Education Cybersecurity & Digital Service Continuity owns cyber resilience and continuity.
- Open Educational Resources & Open Licensing owns open-content licensing.
This node owns the shared architecture above those components: reusable public digital foundations, public learning platforms, modularity, standards governance, open interfaces and the public-control conditions that let many services connect without becoming one irreversible stack.
The Return Path
Return to the school choosing its next digital tool.
If every purchase requires a new identity system, a new data export, a new login, a new content format and a new integration contract, the school is not standing on infrastructure. It is rebuilding foundations repeatedly.
Good digital public infrastructure makes the ordinary things boring: identity works, records move safely, content is discoverable, services can connect, suppliers can be replaced and schools can focus on education rather than integration.
The sign of mature digital education is not that every school uses the same app. It is that different services can change while the public foundations remain trustworthy.
Return to the How Education Works hub.