Industry software development
Education Software Development
EdTech software serves learners — often children — so it lives under strict student-privacy and accessibility rules that vary by region. We build learning platforms and education tools that are engaging, accessible to everyone, and compliant from the US to the EU to Asia.
Education software has a particular duty of care: many of its users are minors, its data is sensitive student records, and it must work for learners of every ability. That combination puts privacy and accessibility at the center of the build rather than at the edges — and the rules governing both differ significantly across regions.
We build learning platforms, LMS and courseware, assessment tools, and education AI — designed to engage learners, integrate with the systems schools already use, and meet the student-data and accessibility obligations of each market. Here's what makes EdTech distinct and the regulatory landscape we design for.
What makes education software different
Accessibility is non-negotiable, not a nice-to-have. Learning tools must work with screen readers, keyboard navigation, captions, and sufficient contrast so that no learner is excluded — and in many contexts that's a legal requirement, not just good practice. We build to WCAG from the start, because retrofitting accessibility is far harder and often incomplete.
Integration and engagement are the other differentiators. EdTech usually has to plug into existing school systems through standards like LTI and SSO with rostering, and it has to hold attention — progress, feedback, and thoughtful design matter because a tool students won't use has no impact. Increasingly, education AI (tutoring, feedback, grading assistance) adds a layer that must be handled responsibly given the age of the users.
Student-privacy and accessibility regulation across the globe
In the United States, FERPA protects the privacy of student education records, COPPA imposes strict rules on collecting data from children under 13, and state student-privacy laws (such as California's SOPIPA) add further duties, with PPRA covering surveys and sensitive topics. Accessibility is required under Section 508 and the ADA.
In the European Union, GDPR applies with heightened protection for children — the age of valid consent varies by member state between 13 and 16 — and demands data minimization and clear lawful bases for processing pupils' data. Accessibility obligations come via the Web Accessibility Directive for public-sector bodies and, increasingly, the European Accessibility Act, both anchored to WCAG and the EN 301 549 standard.
Across Asia-Pacific, rules are tightening: China regulates minors' data under PIPL and has strict rules around online education, India's DPDP Act adds specific protections for children's data with parental-consent requirements, and Singapore, Japan, and Australia apply their own privacy regimes. We build consent, age-gating, data-minimization, and residency as configurable features so a platform can serve schools across borders responsibly.
How we build education software
We build accessibility in from the first component — WCAG-conformant interfaces, keyboard and screen-reader support, captions, and tested contrast — so inclusion is structural. Integration with school systems via LTI, SSO, and rostering means the product fits into teachers' and administrators' existing workflows rather than adding another silo.
On privacy, we design for the strictest applicable regime: minimal data collection, clear consent and age-gating, parental controls where required, transparent handling of student records, and configurable residency. For education AI, we add guardrails and human oversight appropriate to working with young learners. The result is a platform that engages students, includes everyone, and keeps their data safe under the law of each region.
What you get
Accessible to every learner
WCAG-conformant, screen-reader and keyboard friendly, with captions and tested contrast — built in, not bolted on.
Fits school systems
LTI, SSO, and rostering integration so the product slots into existing education workflows.
Student-privacy first
FERPA, COPPA, GDPR-child, and APAC rules handled with consent, age-gating, and minimization.
How we work
- 01
Discover
We pressure-test the idea, map the users, and define the smallest thing worth building. You leave with a plan, not a proposal.
- 02
Design
Flows, prototypes, and a design system that makes the product feel real before a line of production code ships.
- 03
Build
Weekly releases in your stack. You see working software every Friday and steer with real feedback, not guesses.
- 04
Scale
We harden, instrument, and document the system — then hand off cleanly, or stay embedded. It runs without us.
Frequently asked questions
Do you build accessible (WCAG) learning tools?
Yes — accessibility is built in from the start: WCAG conformance, screen-reader and keyboard support, captions, and tested contrast, as US and EU rules require.
How do you handle student data privacy?
We design to the strictest applicable regime — FERPA and COPPA in the US, GDPR's child protections in the EU, and APAC rules — with consent, age-gating, minimization, and residency.
Can your platform integrate with our LMS or SIS?
Yes — we build LTI, SSO, and rostering integrations so the tool fits into the school systems teachers and administrators already use.
Is education AI safe for children?
We build education AI with guardrails, grounding, and human oversight appropriate to young learners, and with the privacy protections their age demands.
Let’s build
Have something worth building?
Tell us what you’re working on. We’ll come back within one business day with real, specific thoughts — not a sales deck.