From the Campus Operations edition of October 9, 2026
ibl.ai case study: Marshall University takes full source code of ibl.ai agent platform as a 'sovereign' sandbox to measure usage and ROI, announced at EDUCAUSE 2026
Marshall University / ibl.ai (vendor case study) · Public university / agentic AI platform for administrative and student services · United States (West Virginia)
- Publisher
- ibl.ai
- Original publication
- October 8, 2026
- Source retrieved
- 2026-10-10
- Event date
- 2026-10-08
What happened
Per the vendor, Marshall receives the full ibl.ai codebase (agent framework, APIs, LTI integrations, documentation) and runs it on infrastructure it controls; Marshall IT governs access, security and model choice, and no outside party trains on institutional data. The deployment begins with a portfolio of agents across admissions, transcript evaluation, financial aid guidance, advising, tutoring and IT support, which Marshall will evaluate and prioritize. CIO Jodie Penrod, speaking at EDUCAUSE 2026, framed it as a sandbox to measure usage and return on investment before deciding how to proceed. Pricing is usage-based, not per seat, and the platform is model-agnostic.
Why it matters
Campus-operations signal on architecture and procurement: an institution choosing self-hosted, source-owned agent infrastructure with usage-based pricing and ROI measurement, contrasting with per-seat enterprise licenses under renewal pressure elsewhere.
Evidence and measured results
Opened the ibl.ai case-study page dated Oct. 8, 2026, which quotes Penrod's EDUCAUSE remarks and states it draws on the Oct. 8 press release (EIN Presswire version returned HTTP 403 to direct retrieval).
Limitations and uncertainty
Vendor marketing; no deployment, usage or ROI results. Code-ownership and no-training claims are vendor statements. Which agents go live is undecided.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-09; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- A campus wants to test AI agents across services while controlling data, models and cost before committing to per-seat licenses.
- Stakeholders
- CIO
- Information security officer
- Financial aid and admissions directors
- Procurement / general counsel
- Discovery questions
- Which agents will be prioritized and by what criteria?
- What hosting and staffing does source ownership require?
- How will usage and cost per agent be reported?
- What happens to support if the vendor relationship ends?
- Value hypothesis
- Interpretation: a usage-priced, self-hosted sandbox could inform buy-or-build decisions; no ROI is evidenced.
- Potential engagement
- A bounded platform-evaluation: TCO comparison with per-seat options and a two-agent pilot with cost and accuracy measures.
- Unsupported claims
- No usage, accuracy or ROI results.
- Code ownership and no-training claims are vendor statements.
- Agent effectiveness in campus systems is untested.
Pre-sales engineering
Role takeaway
- Fit
- Institutions with platform engineering capacity seeking model-agnostic, self-hosted agents.
- Architecture and integration
- Self-hosted agent framework with APIs, LTI to the LMS, model routing across providers and institutional interaction logs.
- Prerequisites
- Hosting infrastructure and platform team
- Integration access to SIS/ITSM
- Model provider contracts
- Security review
- Constraints
- Institution bears operations and patching
- Usage costs vary with model pricing
- FERPA obligations for student-data agents
- Security
- Apply institutional identity, logging and vulnerability management to the self-hosted stack; verify model-provider data terms.
- Proof of value
- Pilot IT-support agent and measure resolution accuracy
- Report cost per interaction by model
- Track platform maintenance hours
Delivery
Role takeaway
- Work
- Select initial agents, integrate with campus systems, and stand up usage/ROI reporting.
- Dependencies
- ibl.ai engineers
- Campus systems owners
- Model providers
- Ownership
- Marshall IT under the CIO, with service owners per agent.
- Skills and adoption
- IT staff need platform-operations skills; service owners need training to evaluate agents.
- Governance checkpoints
- Security review before each agent goes live
- Owner and baseline defined per agent
- ROI review before expansion
- Acceptance criteria
- Proposed: each live agent has a documented baseline and target
- Proposed: cost per interaction reported monthly
- Proposed: no unresolved high-severity findings in platform security review
- Risks
- Platform operations under-resourced
- Agent sprawl
- Unproven vendor claims
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Self-hosted agent platform with LTI integrations and model-agnostic routing; Marshall carries hosting, patching and integration work.
Governance
Who approves, reviews and stays accountable for outcomes?
Institutional logs of every interaction enable usage and cost review; agent prioritization and evaluation criteria are not yet published.
Security and privacy
What data, permissions and controls need testing?
On-premises/controlled hosting keeps data under institutional control, but shifts security responsibility to Marshall IT.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Penrod framed access for faculty, staff and students; the IT team takes on platform operations.
Procurement
What should contracts, pricing and exit terms secure?
Usage-based pricing and code transfer are alternatives to per-seat enterprise licenses; contracts must define support after code transfer.
Operating model
Which teams own the service once it runs?
Positions IT as an internal AI platform provider rather than a license manager.
Publication history
- 2026-10-09Campus Operations · Issue 325 resources
Stable resource ID: marshall-ibl-sovereign-ai-sandbox-educause-20261008