Roadmap
Connect deliberately. Automate responsibly. Expand together.
CampusLayer's direction is interoperability, not a forced replacement for school systems. These phases describe the build order, not promised release dates or completed features.
Phase 1 · Current foundation
Reliable connections
Harden account-scoped provider access and the existing Canvas preview. Extend strict OneRoster validation with a canonical entity model, identity mapping, and preflight diagnostics.
Phase 2 · Planned
Consistent, traceable data
Versioned provider mappings, source references, operational validation, and separately tested OneRoster 1.1/1.2 input and export paths.
Phase 3 · Planned
Workspace and governance
Introduce source-backed role-aware views and a tenant Compliance Center for approved agreements, review scope, and audit evidence.
Phase 4 · Planned
Sync and Flows
Start with a durable runtime, safe workflows, and approval controls, then introduce a React Flow-based editor and selective file sync.
Phase 5 · Planned
Open developer ecosystem
Create a reviewed provider onboarding process, synthetic sandbox, developer registration, canonical and standards APIs, and signed events.
Phase 6 · Longer term
Intelligent orchestration
Let Assistant explain cross-system problems, propose governed actions, and generate draft workflows for people to review and activate.
Built with the ecosystem, not around it.
Schools can request integrations and providers can propose their own. Every production relationship is still subject to review, technical readiness, approved scopes, and school or district authorization.
How integration partnerships work →