Built around the
preschool day.

Shaped by the experience of running a school, Canopy connects classroom updates, parent communication, and school administration in one preschool-focused platform.

Multi-tenant School-scoped operationsWeb & mobile Role-specific workflowsPostgreSQL Tenant-scoped dataLive schools Real operating context

From the classroom to the school office.

Attendance and parent messaging are expected in a school platform. Canopy’s focus is how the work fits together in a preschool: a child’s day, the family’s next action, and the administrative records behind both.

Shaped by school operations

Canopy is developed alongside an education venture and used by live schools. The operating context is concrete: teachers recording the day, parents following their child, and administrators keeping the school running.

A preschool-specific focus

Daily activity reports and parent updates sit alongside attendance and leave requests. The product centers the routines of early-years education, where understanding a child’s day matters as much as keeping a roster.

Beyond classroom records

The codebase also covers admissions, fee collection, finance, and payroll. These workflows extend the platform into the school office, connecting family-facing work with the administrative work that supports it.

The engineering supports that focus: tenant-scoped access separates school contexts, and local tenant resolution provides a fallback when the management service is unreachable.

Inside Canopy.

School setup and tenant management live in a control plane. A separate data plane handles the daily work. Explore each component to see where its responsibility starts and ends.

Different roles. Shared school context.

Administrators, teachers, and parents access Canopy through web and mobile interfaces. Each role has its own workflows and access, while working within the same school context.

The clients connect school staff and families to attendance, daily reports, leave requests, and parent updates.

Connects to: school operations API

Built around the people in a school.

The platform connects everyday records and communication while respecting the different responsibilities of administrators, teachers, and parents.

Administrators

Bring school operations into one place, with access appropriate to the administrative role.

  • Attendance records
  • Daily activity reports
  • Leave requests and school updates

Teachers

Use daily workflows to keep school records and family communication connected.

  • Attendance workflows
  • Daily activity reporting
  • Parent updates

Parents

Follow school updates and participate in the routines that connect home and school.

  • Updates from the school
  • Daily activity reports
  • Leave requests

Resolve the school. Then do the work.

Tenant resolution sits at the boundary between platform management and daily school operations. Canopy includes a local fallback when the control plane is unreachable.

Why separate the two planes?

School setup and tenant configuration have different responsibilities from attendance, reports, and parent communication. Separate service boundaries let each concern be managed independently.

What happens when the control plane is unavailable?

The school operations API can use tenant data in the local database to resolve the school when the control plane is unreachable.

How does school context reach the data?

The data plane resolves the current school and scopes database access to that tenant, keeping day-to-day operations tied to the right school.

Incoming school request

Web or mobile client connects to the school operations API.

Resolve tenant context

Consult the control plane, with local database resolution as a fallback.

Run the school workflow

Handle the operation through tenant-scoped data access.

Software shaped by operating a school.
Canopy serves live schools across web and mobile. Canopy World School is part of the wider education venture behind this work.

Visit Canopy World School