AI for every department —
inside one approved budget.
Per-department hard caps that hold the academic year, four RLS-enforced roles so leads manage their own keys, and content guardrails applied the same way across every course and lab.
No per-feature paywalls · every control on every plan
- 3Budget scopesInstitution · department · key
- 4Access rolesOwner · admin · member · viewer
- 3Reset cyclesDaily · weekly · monthly
- 4 → 0%Platform feeNo per-feature paywalls
Hold AI spend to the budget you approved in the spring.
An academic budget is set once and defended all year. Each department is a Nemo Router team with its own hard and soft caps; costs are settled from the provider's own response, so spend is exact. When a department reaches its hard cap the key returns 402 — the database refuses to write a negative balance, so an overrun is structurally impossible.
- Per-department teams with independent hard and soft budgets
- Costs settled from the provider response — exact, not estimated
- Soft-cap alerts at 70 / 90 / 100% via Slack or webhook
- Per-key spend breakdown for clean department chargeback
Institution
Annual budget, approved once
One number from the spring — defended automatically all year
Department — research computing
Soft cap at 90%
Slack alert fired · grant-funded experiment stays inside its allocation
Department — computer science
Hard cap set
Overrun structurally blocked · 402, never a negative balance
Team RBAC across faculty and staff
Department leads manage their own keys and budgets; central IT keeps oversight. Four roles, RLS-enforced at the database.
Content guardrails, consistently applied
PII redaction and prompt-injection detection run inline on every request — the same safety policy for every course and lab.
Predictable cost, term after term
Transparent 4% / 2% / 0% platform fee by tier — no per-feature pricing, no surprise inference markup at term end.
What we can state plainly about student data.
- Student data is protected by PII-redaction guardrails and a configurable data policy — choose zero-content, metadata-only, or PII-redacted logging per institution.
- FERPA is a shared responsibility. Nemo Router provides the technical safeguards; raise FERPA requirements with sales early so we can walk through the data-handling controls before you go live.
- SOC 2 Type II is in progress (target Q3 2026); GDPR-compliant with a published DPA. We will not claim a certification we do not hold.
Procuring for a campus or district? sales@nemorouter.ai will walk through the data-handling controls and a budget plan with your team.
Education questions, answered
How do we stop one department from overrunning the AI budget?
Give each department its own team with a hard budget. The moment spend would breach the cap, the key returns 402 — there is no partial debit and the balance cannot go negative. Soft caps fire Slack or webhook alerts at 70%, 90%, and 100% so a department lead sees the trend before the line item is gone.
Can department leads manage their own keys without central IT?
Yes. The org → team → member hierarchy with four roles (Owner, Admin, Member, Viewer) lets a department lead create and manage keys, budgets, and guardrails for their own team while central IT keeps institution-level oversight. Roles are enforced by Postgres Row-Level Security, so a department cannot see or change another department’s resources.
How is student data protected?
PII-redaction guardrails strip identifiers inline before a request reaches a model provider, and a configurable data policy lets the institution choose whether request content is logged at all (zero-content, metadata-only, or PII-redacted). For institutions handling education records, raise FERPA requirements with sales early so we can walk through the data-handling controls.
Is the cost predictable across an academic year?
Costs are settled from the provider-reported response, so spend is exact rather than estimated, and the platform fee is a transparent 4% / 2% / 0% by tier with no per-feature pricing. Combined with per-department hard caps, an institution can hold AI spend to an approved annual budget.
Give every department AI inside one budget.
We will walk your institution through per-department budgets, role-based access, content guardrails, and a cost plan that holds for the academic year.
Per-department budgets · team RBAC · content guardrails on every plan · transparent platform-fee pricing