A hosted library of teacher tools, or an AI platform the district owns and runs inside its own perimeter
On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.
Last updated:
MagicSchool is the most widely adopted AI toolset in K-12, and for good reason: it puts dozens of ready-made teacher tools — lesson plans, rubrics, IEP support, family communication — in front of a teacher who has had no training and no setup time.
It is a hosted product. Districts subscribe, teachers sign in, and the prompts and student work they enter are processed on MagicSchool's infrastructure under MagicSchool's terms.
A self-hosted platform answers a different question. Instead of buying tools, the district runs the AI itself — inside its own network, on its own storage, integrated with PowerSchool and Google Classroom, with every interaction logged where the district's own auditors can see it.
The honest comparison is not tool count. It is whether a district wants a subscription that is fast to adopt, or infrastructure it owns and can still be running in five years on its own terms.
by ibl.ai
Owned agentic AI platformby MagicSchool
Hosted K-12 teacher toolset| Criteria | Self-Hosted AI | MagicSchool AI |
|---|---|---|
| Out-of-the-Box Readiness | Production agents for lesson planning, differentiation, family communication, tutoring, and instructional feedback once deployed, configured to how your organization actually works. | Immediately useful — an unusually large library of ready-made teacher tools that need no training or setup. |
| Integration With Your Systems | Deep integration with PowerSchool, Clever, ClassLink, and Google Classroom over APIs and MCP, running inside your own network. | Connects to common systems, bounded by the connectors the vendor has built. |
| Extensibility | Build and own workflows the vendor has not thought of, because you hold the code. | Configurable within the product; capabilities outside it require the vendor to build them. |
| Any-LLM & Model Control | Run any open or commercial model, route by cost, latency, and capability, and switch anytime. | Runs on models MagicSchool selects and manages. |
| Criteria | Self-Hosted AI | MagicSchool AI |
|---|---|---|
| Self-Hosting / On-Prem / Air-Gapped | Runs on your servers, your private cloud, or fully air-gapped with zero external calls. | Runs in MagicSchool's cloud; it cannot be self-hosted or air-gapped. |
| Where the Data Lives | minors' student data never leaves your environment, and every interaction is logged for audit. | Processed and retained on the vendor's infrastructure under your agreement. |
| Source Code Ownership | You hold the full source and can audit, fork, and extend every layer. | You rent access; the platform and its roadmap belong to the vendor. |
| Fit With FERPA and COPPA | Data stays inside your perimeter, which is the simplest posture to evidence under FERPA and COPPA. | Vendor compliance coverage under shared-responsibility terms. |
| Criteria | Self-Hosted AI | MagicSchool AI |
|---|---|---|
| Cost at Scale | Flat license plus compute you own — extending access across K-12 districts does not multiply the bill. | per-teacher and district licensing, so cost grows with the size of the organization rather than the work done. |
| Time-to-Value | Requires deployment and integration, or a partner who does both for you. | Usable almost immediately with no infrastructure work. |
| Support & Maintenance | Self-managed, or fully supported with forward-deployed engineers. | Fully managed by MagicSchool. |
| What You Keep If the Relationship Ends | A working platform and all your data, still running on your own infrastructure. | Whatever the contract allows you to export. |
A district-owned deployment keeps student work on district infrastructure, so the privacy review is about systems the district already controls rather than a vendor's data-handling policy.
MagicSchool's advantage is that a teacher can produce something useful in their first five minutes, with no district IT project standing between them and the tool.
If teacher adoption this semester is the goal, the hosted toolset wins on speed. If the constraint is that minors' data must not leave district systems, that is not a speed question.
An owned platform is extensible: the district can build agents for its own workflows — attendance outreach, MTSS documentation, translation for its specific family languages — rather than choosing from a catalog.
MagicSchool ships a broad, curated catalog. What it does not do is let a district add a capability the vendor has not built.
Districts wanting a fixed set of well-made tools are well served by a hosted catalog. Districts with workflows nobody else has need infrastructure they can extend.
ibl.ai is licensed with the source code and self-hosted, so a district that changes vendors, budgets, or leadership still has a working platform and its own data.
A subscription ends when it ends. The prompts, the generated materials, and the usage history live in the vendor's product.
For a one-year pilot this rarely matters. For a district building AI into instruction as permanent infrastructure, it is the whole decision.
When policy or a state statute requires that minors' data stay on district-controlled systems, self-hosting satisfies it directly rather than through a vendor agreement.
A hosted catalog needs no IT project, no infrastructure, and no procurement cycle — for a single school that is decisive.
Per-teacher licensing multiplied across thousands of staff scales with headcount, while a flat self-hosted license does not.
MTSS documentation, translation for specific family languages, and local reporting are not in anyone's catalog — they require a platform you can extend.
Timeline: Four to ten weeks depending on integration count and review requirements
Timeline: Days to a few weeks
ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.
ibl.ai gives a district the platform rather than the subscription. It runs inside district infrastructure — on-premise or in the district's own cloud — so prompts containing student work never leave systems the district controls, and every interaction is logged where district auditors can reach it. Agentic OS integrates with PowerSchool, Clever, ClassLink, and Google Classroom over APIs and MCP, runs guardrails and PII redaction before any model sees student data, and lets the district build agents for its own workflows rather than picking from a catalog. You own all the code and the data, run any model, and can deploy on any cloud, on-premise, or air-gapped — with a flat license instead of per-teacher fees.
Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform — the stack itself is yours.
Run any LLM — Claude, GPT, Gemini, Llama, Command, or your own fine-tune — and switch providers without rewriting the platform.
Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.
Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.
1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.
ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.
See how ibl.ai deploys AI agents you own and control—on your infrastructure, integrated with your systems.