EdTech
Scale the EdTech team you already have.
Most EdTech companies do not have an idea problem. They have a capacity problem: a roadmap the current team cannot ship before the next school year. We add engineers who already know LTI 1.3, OneRoster, SCORM, xAPI and what FERPA lets you log, so they contribute in week one instead of week six.
Where edtech engineering gets complicated
EdTech has unique engineering constraints.
The academic calendar is a hard deadline
Miss a September launch and you wait a year, not a quarter. That is why EdTech capacity problems compound: a two-month slip in March is a twelve-month slip in reality, and it is the reason teams end up pushing back customer commitments rather than shipping late.
Interoperability standards are unforgiving
LTI 1.3 with LTI Advantage (Deep Linking, Names and Role Provisioning, Assignment and Grade Services), OneRoster 1.2 for rostering, QTI 3.0 for assessment portability, plus Clever and ClassLink for district SSO. Each has a certification process and a spec that punishes guessing. An engineer who has shipped an LTI 1.3 tool before saves you a month.
COPPA, FERPA, GDPR and state privacy laws all apply at once
K-12 products in the US need verifiable parental consent under COPPA, FERPA-compliant handling of education records, and increasingly a signed Student Data Privacy Consortium (SDPC) agreement per district. California's SOPIPA and dozens of state analogues add more. Engineers who have not worked in education routinely log data they are not allowed to retain.
Accessibility is a procurement gate, not a nice-to-have
Districts and universities ask for a VPAT based on WCAG 2.2 AA before they will sign, and public institutions are bound by Section 508 and ADA Title II. Retrofitting keyboard navigation, focus management and screen reader semantics after launch costs several times what building it in does.
Enterprise buyers audit your security posture
Once you sell to districts or universities, SOC 2 Type II shows up in every RFP, along with penetration test reports, subprocessor lists and incident response commitments. Engineering has to produce the evidence: audit logging, access controls, encryption at rest, and data retention that matches what you promised.
Concurrent load is predictable and brutal
Class start times, exam windows and assignment deadlines all spike at once, and video is usually the largest cost and the highest risk. Encoding pipelines, adaptive bitrate streaming, CDN strategy and offline access all need real engineering rather than a default configuration.
What we build
Specific capabilities for edtech teams.
LTI 1.3, OneRoster and QTI integrations
LTI 1.3 tool and platform implementations with LTI Advantage services, OneRoster 1.2 rostering against district SIS data, QTI 3.0 assessment import and export, and Clever or ClassLink SSO. Engineers who have been through IMS Global certification before, not reading the spec for the first time.
LMS development and customization
Custom LMS platforms, Moodle customization, Canvas and Blackboard integrations, and SCORM 1.2, SCORM 2004 and cmi5 compliant content players. Engineers who understand IMS standards.
Accessibility and VPAT readiness
WCAG 2.2 AA remediation, keyboard and screen reader support, accessible assessment components, and the audit work behind a VPAT that survives a district procurement review. Section 508 and ADA Title II obligations included.
Student data privacy engineering
COPPA consent flows, FERPA-aligned data retention and deletion, audit logging, role-based access control, and the SOC 2 Type II evidence trail enterprise buyers ask for. Built so the compliance answer is a query, not a scramble.
Video delivery infrastructure
Transcoding pipelines, HLS/DASH streaming, DRM integration, and offline download systems. Engineers who've worked with Mux, Cloudflare Stream, or AWS MediaConvert.
Assessment and proctoring tools
Question banks, randomized assessments, rubric-based grading, and anti-cheating tooling for high-stakes assessments.
AI in this industry
AI tutoring systems, automated essay scoring, and intelligent content recommendation are moving from research prototypes to production features in edtech. Engineers working in this space need to understand not just the models but the pedagogical evidence base: what actually improves learning outcomes versus what just looks impressive in a demo.
Common tech stack
What edtech engineering teams typically use.
React
Next.js
React Native
TypeScript
Node.js
Python
Java
PostgreSQL
Redis
Elasticsearch
AWS
CloudflareProof
Four EdTech engagements we have already shipped.
EdTech is the largest part of our portfolio. These are real engagements, described with the client's permission where they are named.
FAQ
Common questions
Tell us what your roadmap needs. We will send profiles in 3 days.
Engineers who already know the standards, the compliance rules and the academic calendar. Two-week trial, month-to-month after that.