We built CurioPilot because EdTech AI deserves actual transparency.
Not the kind that’s a checkbox in a marketing deck — the kind that survives a DPO review.
The bet behind CurioPilot.
In every conversation with a school admin or DPO over 18 months of discovery, the same question came up — sometimes politely, sometimes not — within the first 15 minutes: “If a parent comes to me next semester and asks what your AI said to their child, what can I show them?”
Most AI EdTech products built in 2024 and 2025 had no answer. The AI call happened; the prompt was assembled; the response came back. The intermediate steps — what model was chosen, what was redacted before the prompt left the tenant, who approved the output — none of it was captured. So the answer to the parent was “we don’t have that information.”
That answer is fine for an internal tool. It is unacceptable for a K-12 platform. So we made it impossible to give: every AI call in CurioPilot is gated through TraceLayer, which logs consent, redaction, model choice, and review state before the prompt can leave the tenant.
That’s TraceLayer. It was the first feature we shipped — before anything else could run on it.
The bet is that K-12 will look back on this decade and ask why we didn’t demand transparency from EdTech AI sooner. We’re betting they will — and we’d rather build that platform than wait for someone else to.
Long form on the same argument: Why we built TraceLayer first.
Six things we don’t compromise on.
Transparency is a feature, not a tax.
Every AI decision logged in TraceLayer. Every consent state enforced at the call site. Every parent can ask 'why?' and get a real answer.
Teachers stay in the loop.
AI suggests; teachers decide. We will never ship a feature that replaces a teacher's judgement on a child's learning.
The platform is the procurement.
Schools shouldn't need a 60-page security questionnaire to evaluate us. Our compliance docs are public, our PII attestation is generated, our DPA is downloadable.
Children's data is theirs.
We don't train models on your students. We don't share data with advertisers. We delete on request — Article 15 export and Article 17 erasure are one-click.
Build with the systems schools already have.
SIS via OneRoster. LTI 1.3 for your LMS. Google Classroom. Stripe billing for procurement. We meet your IT stack where it lives — we don't ask schools to change theirs.
Honest about what we don't have.
Native mobile apps? Not yet. SOC 2 Type II? Audit in progress. We say what's live and what's coming. Marketing copy is the contract.
Small enough that the founder still writes the code.
CurioPilot is built by MoizLabs LLC — a one-person studio with help from contractors and partners. The team grows when there’s a product reason to grow it, not before.
We don’t publish team photos until we have a real team to photograph. We don’t list investors until we have permission to disclose. We don’t cite school deployments until they’ve given us logo permission. When any of those happen, this page changes.
We’re a small team. We hire carefully.
We don’t have a full careers page yet. When we hire we hire intentionally and post a single specific role at a time. If you’re excited about K-12 + AI + compliance + transparency, we’d like to hear from you anyway.
- Press: press@moizlabs.com
- Partnerships: hello@moizlabs.com
- Hiring (when open): hello@moizlabs.com
- General: hello@moizlabs.com
Company facts.
Want to evaluate CurioPilot for your school?
30 minutes. We’ll show TraceLayer, walk through compliance, and answer the questions your IT will ask before you do.