Cincinnati Built Its Own AI Platform Instead of Just Turning On ChatGPT Edu for Everyone
AI & ML

Cincinnati Built Its Own AI Platform Instead of Just Turning On ChatGPT Edu for Everyone

The University of Cincinnati is rolling out persistent Projects and memory inside BearcatsGPT, a university-run AI platform it has expanded continuously for two years. Most peers buy a single vendor's AI suite instead of running their own.

PublishedNovember 20, 2026
Read time6 min read
Share

A feature set that mirrors a commercial AI assistant, built and run in-house

Bearcats ONEchat, Projects, and User Memory became available to every BearcatsGPT user during the week of November 16, 2026, and the feature set reads like it was lifted directly from a commercial consumer AI assistant: a default chat interface, persistent project workspaces, and memory that carries context across sessions. What makes this rollout notable is not the features themselves, which have become fairly standard across major AI products, but that a university built and now maintains them on its own platform rather than simply enabling an equivalent feature inside a vendor's existing product.

ONEchat specifically gives users a familiar chat interface with no setup required, while still preserving access to university-developed agents through a separate Explore Agents option for people who want something more specialized than a general-purpose chat window. Projects let a user upload a file once and have every conversation inside that project draw on it automatically, with saved instructions applying to future chats without needing to be repeated, which is the kind of persistent context that turns a one-off AI interaction into an ongoing working relationship with the tool.

Memory that users can actually see and control

User Memory saves details such as preferences, recurring tasks, and ongoing projects across separate chat sessions when memory generation is turned on, letting the system build up context about a specific user over time rather than starting from zero in every new conversation. Critically, the university gave users direct controls to review what has been saved, pause or resume memory generation, export the saved data, or clear it entirely, which is a meaningfully more transparent approach than a system that silently accumulates data about a user with no visible record of what it has stored.

That level of user control over memory matters specifically in a university setting, where the people interacting with the system include students who may be wary of an institutional AI tool quietly building a profile of their academic habits and struggles over time. Giving users an explicit, visible way to inspect and clear that profile addresses a real trust concern that a less transparent memory implementation would leave entirely unaddressed, and it is a detail other universities rolling out similar features should take seriously rather than treat as optional polish.

Two years of steady, incremental expansion rather than one big launch

BearcatsGPT did not appear fully formed this month; it has been built up in stages since a 2024 pilot built on OpenAI's technology, expanding to all faculty and staff in December 2025, to all students in February 2026, and adding Claude as an additional available model in July 2026 before this latest round of features. That incremental pattern, pilot, then staff, then students, then a second model provider, then richer features, suggests an institution deliberately building organizational and technical capacity over time rather than attempting a single comprehensive launch and hoping it held up under real use.

Cincinnati's own framing of itself as the first Ohio university to offer a branded AI platform is a meaningful claim specifically because of how much sustained effort that incremental rollout represents. Universities that watched Cincinnati's early 2024 pilot and chose to wait rather than commit early are now choosing between replicating two years of incremental platform development themselves or licensing a comparable experience from an outside vendor instead, and that choice looks meaningfully different today than it did when Cincinnati first started.

The build-versus-buy tradeoff this rollout actually represents

Most universities adopting campus-wide AI have gone the other direction, licensing a single vendor's existing product such as ChatGPT Edu or Claude for Education and deploying it campus-wide rather than building a comparable experience from scratch. That approach gets an institution to a working deployment faster and shifts the ongoing engineering burden onto the vendor, but it also means adopting whatever feature set, interface, and release cadence that vendor chooses to ship, rather than the fully custom experience Cincinnati has built for itself over two years of iteration.

Cincinnati's approach trades a faster initial deployment for long-term control over its own AI experience, including the ability to add Claude as a second model option in July 2026 without waiting on a single vendor's product roadmap, and the flexibility to build features like ONEchat's Explore Agents that are tailored specifically to how its own students and faculty actually work. That flexibility comes at the real cost of sustained internal engineering investment that most universities' IT departments are not resourced to sustain over multiple years, which is exactly why so few other institutions have taken the same path Cincinnati has.

Why this matters more broadly than one university's IT roadmap

Cincinnati's sustained, incremental build gives other universities and even K-12 districts a working reference point for what an institution-run AI platform actually requires over a multi-year timeline, rather than the more abstract vendor pitches most IT leaders are currently evaluating in procurement conversations. A platform that has survived two years of real use across faculty, staff, and students, through multiple expansions and a second model provider, has been tested in ways that a brand-new institutional AI deployment has not.

The detail that should draw the most attention from peer institutions is the explicit user controls built into User Memory, a feature far more likely to generate real concern from students, parents, and faculty governance bodies than the ONEchat interface itself, as more universities roll out AI tools that persist context across sessions. Any institution building or evaluating a similar memory feature should treat Cincinnati's transparency choices as close to a minimum baseline rather than an advanced, optional addition.

What this means for university and K-12 technology leaders evaluating their own path

Technology leaders at institutions still deciding between building an in-house AI platform and licensing an existing vendor product should treat Cincinnati's two-year timeline as a realistic baseline for what the build path actually costs in sustained engineering effort, not the compressed few-month rollout that a single flashy announcement might suggest. An institution unwilling or unable to commit resources at that multi-year scale is likely better served licensing an established vendor platform rather than attempting a partial, under-resourced version of what Cincinnati has built.

For institutions that do have that sustained capacity, Cincinnati's specific choices around user-visible memory controls and a tiered interface that serves both casual chat users and people who need specialized agents are worth studying directly as a design reference, rather than being reinvented independently from scratch. The more universities that adopt similarly transparent memory controls as a baseline expectation, the more pressure that puts on vendor platforms to match that same standard rather than treating user visibility into stored data as a differentiator reserved for premium tiers.

Tagged#news#edtech#education#learning#lms#ai-education#bearcatsgpt#university-of-cincinnati#ai-memory-controls#build-vs-buy-ai#campus-ai-platform#higher-ed-it-strategy