An extension that meets teachers inside Google Docs, or a platform the district runs inside its own network
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:
Brisk Teaching works where teachers already are. It installs as a browser extension and appears inside Google Docs and Google Classroom, so giving feedback on a student essay or checking writing progress takes no new tool and no new tab.
That design is its strength and the source of the question a district has to answer: an extension that reads student writing in the browser is sending that writing somewhere to be processed, and that somewhere is Brisk's service.
A self-hosted platform moves the processing rather than the workflow. The models run inside district infrastructure, so student writing is analyzed by a system the district owns, with logs its own auditors can inspect.
This comparison is about where the work happens, not whether teachers like the interface — and for districts with binding student-data policies, that is the only question that survives the privacy review.
by ibl.ai
Owned agentic AI platformby Brisk
Browser-extension AI for teachers| Criteria | Self-Hosted AI | Brisk Teaching |
|---|---|---|
| Out-of-the-Box Readiness | Production agents for writing feedback, revision history review, differentiation, and instructional materials once deployed, configured to how your organization actually works. | Immediately useful — meeting teachers inside Google Docs and Classroom, so there is no new tool to learn and no workflow change. |
| Integration With Your Systems | Deep integration with Google Classroom, Google Docs, Clever, and PowerSchool 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 Brisk selects and manages. |
| Criteria | Self-Hosted AI | Brisk Teaching |
|---|---|---|
| Self-Hosting / On-Prem / Air-Gapped | Runs on your servers, your private cloud, or fully air-gapped with zero external calls. | Runs in Brisk's cloud; it cannot be self-hosted or air-gapped. |
| Where the Data Lives | student writing and minors' 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 | Brisk Teaching |
|---|---|---|
| Cost at Scale | Flat license plus compute you own — extending access across K-12 districts does not multiply the bill. | per-teacher and school 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 Brisk. |
| 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. |
Self-hosting keeps analysis of student writing inside district systems, so the review question becomes one about infrastructure the district already secures.
Living inside Google Docs is genuinely why teachers adopt Brisk — it removes the friction that kills most edtech rollouts.
Convenience and data location pull in opposite directions here. A district that can accept off-network processing gets a real adoption advantage; one that cannot gets no benefit from the convenience.
An owned platform can be pointed at the district's own rubrics, reading levels, and multilingual family communication needs, and extended into workflows outside the document.
Brisk is focused and does its focused thing well — writing feedback and progress visibility inside the Google stack.
For writing feedback specifically, a focused tool is competitive. For AI as district-wide infrastructure, a single-purpose extension is not the same category of purchase.
A flat, self-hosted license covers every teacher, aide, and administrator without the cost changing as the rollout widens.
Per-teacher licensing is easy to approve for one school and becomes a budget line that grows with staffing across a district.
Small pilots favor per-teacher pricing. District-wide deployment is where the pricing shape starts to dominate the decision.
An extension that processes student writing on a vendor's service cannot satisfy a policy that requires minors' data to stay on district systems.
Living inside Docs and Classroom removes the friction that stops most teacher tools from being used at all.
Tutoring, family communication, MTSS documentation, and administrative agents are outside the scope of a writing-focused extension.
Consolidating on owned infrastructure avoids accumulating separate per-teacher subscriptions for each teaching task.
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 moves the processing rather than the teacher's workflow. The platform runs inside district infrastructure, so analysis of student writing happens on systems the district owns, with logs its own auditors can inspect. Agentic OS connects to Google Classroom, Clever, and PowerSchool over APIs and MCP, applies guardrails and PII redaction before any model sees student work, and extends past writing feedback into tutoring, family communication, and administrative agents the district defines itself. You own all the code and the data, run any model, and can deploy on any cloud, on-premise, or air-gapped — on a flat license rather than per teacher.
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.