| Primary strength | Deep, native control inside one AI environment. | Consistent district policy across supported AI products. |
|---|
| Policy reach | Usually strongest within the vendor's own suite and accounts. | Designed for supported AI surfaces used on district-managed Chrome devices. |
|---|
| Classroom context | Can be tightly connected to the suite's native classroom workflows. | Tenet District adds roster, class, teacher, period, and schedule differentiation. |
|---|
| Administration | One vendor console and one product experience can simplify standardization. | One district governance plane coordinates policy while each AI product keeps its own experience. |
|---|
| Content path | Interactions live within the suite under that provider's architecture and terms. | The AI service still receives content needed to answer, but routine prompts and responses are not sent to TrueMadeAI servers. |
|---|
| Best fit | Districts that want one standardized AI environment. | Districts that expect students and staff to use a mixed set of supported AI products. |
|---|