--- title: "AI Tutoring Platform Districts Can Own: Student Data Stays in the District" slug: "ai-tutoring-platform-districts-can-own" author: "Blanca Amigot" date: "2026-06-09 13:05:00" category: "Premium" topics: "AI tutoring platform districts can own, district-owned AI tutoring, self-hosted K-12 AI, COPPA compliant AI tutoring, FERPA AI tutoring, Khanmigo alternative, MagicSchool alternative, student data ownership" summary: "A district-owned AI tutoring platform is one where the district owns the source code and the model, self-hosts it on its own infrastructure, and pays a flat license — not a per-student fee. Student data never leaves district systems, so COPPA and FERPA hold by architecture." banner: "" thumbnail: "" --- ## The Short Answer **An AI tutoring platform a district can own is one where the district holds the source code, runs the model on its own infrastructure, and keeps every student record inside district systems — instead of renting a cloud tool that ships student data to a vendor.** The ibl.ai platform is built this way. The district self-hosts it, picks any LLM (Claude, GPT, Gemini, Llama, DeepSeek) and swaps models anytime, and pays a flat license rather than a per-student or per-teacher annual fee. Why own instead of renting Khanmigo or MagicSchool? Per-student SaaS scales your bill with enrollment whether or not students use it, and your students' interactions live on someone else's servers. Ownership flips both: fixed cost, and data that never leaves the district. ## How is a district-owned AI tutor different from Khanmigo or MagicSchool? Khanmigo, MagicSchool, and SchoolAI are cloud-only, hosted services. The district subscribes, and student prompts and responses flow to the vendor's infrastructure for processing. With a district-owned platform, the relationship inverts. The district receives the source code and runs it on its own servers or private cloud tenancy. There is no vendor inbox collecting student conversations. Pricing is publicly reported as per-student or per-teacher per year for the major K-12 tools — a recurring fee that climbs with enrollment. A district-owned deployment is a flat license plus the compute you run. The other structural difference is model choice. Most hosted tutors lock you to one provider's model. ibl.ai is model-agnostic: run any LLM and switch when a better or cheaper one ships, without re-platforming. ## Where does student data go? In a self-hosted deployment, it goes nowhere outside the district. Student prompts, tutoring transcripts, and progress data sit on infrastructure the district controls — on-premise or in the district's own cloud account. That is the core promise. The platform processes everything inside your boundary. No third-party vendor receives, stores, or trains on student records. You choose where the LLM runs too. Use a private model endpoint inside your network, or route to a hosted model under your own data-processing terms. The data path is yours to define. ## Is it COPPA and FERPA compliant? COPPA and FERPA both hinge on who holds and discloses student data. When student records never leave district infrastructure, there is no third-party disclosure to manage in the first place. With a hosted tutor, compliance depends on the vendor's contract, sub-processors, and data-handling promises. You are auditing someone else's stack. With a district-owned, self-hosted platform, the district is the data controller end to end. FERPA's directory-information and disclosure rules stay inside systems your administrators already govern. COPPA's under-13 protections are simpler to satisfy when no outside operator collects children's data at all. Compliance becomes a property of the architecture, not a clause you hope a vendor honors. ## What does it cost vs per-student pricing? Per-student SaaS is structurally wrong at scale. The bill grows with enrollment regardless of how much the tools actually get used — a 12-school district pays for every student on the roster, every year, forever. A district-owned deployment is a flat license plus GPU compute. Add 2,000 students and the cost does not move. The table below uses publicly reported, approximate per-student pricing against a flat self-hosted model.
Option Unit price (approx.) 8,000 students Data location
Per-student SaaS (low) ~$15/student/yr ~$120,000/yr Vendor cloud
Per-student SaaS (high) ~$40/student/yr ~$320,000/yr Vendor cloud
ibl.ai (self-hosted) flat license + GPU flat (does not scale per student) District infrastructure
At a 12-school district, the per-student approach can cost many times the flat license for the same workload — and the gap widens every year enrollment grows. ## How do teachers stay in control? The platform is built around teacher oversight, not autonomy. Teachers configure what a tutor can and cannot do, review transcripts, and set the guardrails for each class or grade band. Tutoring agents run on OpenClaw and NVIDIA NemoClaw runtimes, which carry programmable guardrails: jailbreak and prompt-injection defense, PII redaction, role-based access, and audit logging. Administrators see who did what. Because the district owns the deployment, your team defines the curriculum alignment, the allowed topics, and the escalation rules — rather than accepting a vendor's defaults. ## How is it deployed? The platform deploys anywhere: on-premise in a district data center, in the district's private cloud tenancy, or air-gapped where policy requires it. Student data follows the deployment and stays inside your boundary. ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, long-term partner rather than a vendor that sells a license and moves on. For public-school buyers, that continuity matters. You can explore the platform on the [ibl.ai K-12 solutions page](/solutions/k-12) and the flagship [Agentic OS product](/product/agentic-os), which the tutoring agents are built on. ## Frequently Asked Questions ### Can a district really own the source code? Yes. A district-owned deployment means the district receives and runs the platform's code on its own infrastructure, rather than subscribing to a hosted service. ### Do we have to use one specific AI model? No. The platform is model-agnostic — run Claude, GPT, Gemini, Llama, or DeepSeek, and switch to a different model anytime without re-platforming. ### How does this keep us COPPA and FERPA compliant? Student data never leaves district infrastructure, so there is no third-party disclosure to manage. The district stays the data controller end to end. ### What happens to our cost as enrollment grows? It stays flat. A self-hosted license plus GPU compute does not scale per student, unlike per-student SaaS that bills for every name on the roster each year.