Built for edtech
We build the systems institutions and publishers run their academic operations on — admissions, scheduling, grading, and content delivery, replacing spreadsheets with software people actually want to use. Most institutions we meet are running admissions in one tool, grading in another, and communication over email chains nobody can search later. We consolidate that into one system administrators, teachers, and parents each see their own slice of, without asking anyone to relearn how they already work.
Solutions for edtech
Admissions, scheduling, grading, and communication in one multi-tenant system built for institutions. Each school gets its own isolated data and configuration but shares the same underlying platform, so a fix or feature ships to every institution at once instead of one deployment at a time.
Built for how institutions actually operate
Multi-tenant by design
One platform serving many institutions, each with isolated data and configuration. Onboarding a new school is a setup flow, not a new deployment, because tenant isolation was the first architectural decision, not a retrofit.
Accessibility
Built to WCAG standards so every student can use what you ship. Keyboard navigation, focus order, and screen-reader labelling are part of the build from day one, not a remediation project after a complaint or an audit.
Data privacy
Student data handled under FERPA-aware access controls and retention policies. Parents, teachers, and administrators each see only the slice of a student's record their role actually requires, by design rather than by convention.
Fast onboarding
Migration tooling that gets a new institution live in days, not months. Data import, account provisioning, and configuration are self-serve flows we build as part of the platform, not a manual process repeated for every new school.
Classhub: EdTech · School management
A legacy system rebuilt into a multi-tenant school-management platform serving 40 institutions.
Read the case study ↗The tools we build with
Multi-tenant from the first commit, because retrofitting tenant isolation later is a rewrite.
Platform
Next.js
React
TypeScript
TailwindBackend & data
Node.js
PostgreSQL
Redis
PrismaContent & search
AWS
Cloudflare
GraphQL
AlgoliaOps
Docker
GitHub Actions
Grafana
SentryEdTech FAQ
Yes, and we build multi-tenant from the first commit. Retrofitting tenant isolation into a single-tenant system later is effectively a rewrite, so it isn’t a decision we defer.
Related work
Related reading
Building something in this space?
Bring us the constraints and the goal. We'll handle the rest.