A guest post by Rasheed Behrooznia, EVP & GM for Campus ID and Commerce, Illumia
At most campuses, the hardware landscape didn’t arrive by design. A residence hall installed one manufacturer’s readers five years ago. Dining chose a different system when they upgraded two years before that. The library and the recreation center each made their own decisions based on their own requirements and timelines. Nobody coordinated, because nobody needed to. Each choice was reasonable in context.
The result is a federated infrastructure that represents the real operating environment for a mobile credential platform: different hardware, different protocols, different vintages, managed by different departments. Not a clean architecture diagram, but an accumulated set of decisions that the platform has to work within from day one.
How well a platform handles the complexity of the federated infrastructure is one of the more consequential things to understand before selecting a platform and partner. After all, for most institutions, what is being deployed isn’t in a lab or a pilot; it’s a mission-critical operating layer supporting safety, access, and daily campus life.
This is also where a platform’s track record matters: whether it has demonstrated the ability to deliver mobile credentials successfully at scale, year after year, across diverse campus environments, without degradation in reliability, security, or user experience.
What Some Flexibility Arguments Don’t Say Up Front
Vendor flexibility and credential portability have become prominent themes in mobile credential conversations, and for good reason. Institutions making significant infrastructure commitments want to understand their options, and the questions being asked about encryption key ownership, open standards, and switching costs are legitimate ones.
What’s asked less often is how those approaches have performed operationally, whether they have been deployed repeatedly at institutional scale, across multiple campuses and years, while maintaining high levels of client satisfaction, student adoption, and information security. What’s also worth examining more carefully is the infrastructure assumption embedded in some of those flexibility arguments. Certain approaches to vendor independence work most cleanly in a standardized hardware environment, one where every reader, every access point, and every transaction terminal operates on a common protocol. On a campus built the way most campuses are built, reaching that baseline is a significant capital project.
That cost doesn’t always appear in conversations about flexibility. The portability being offered is real, but the conditions required to access it deserve the same scrutiny as the portability itself. An institution that understands what standardization would actually require, in budget, in timeline, in cross-departmental coordination, is in a better position to evaluate what it’s being offered.
What It Means for a Platform to Meet Your Campus Where It Is
A credentialing platform that operates across heterogeneous hardware without requiring a retrofit to change what mobile credentials can deliver, and how quickly. In practice, that means working across the reality most campuses face today: a mix of security technologies, access control systems, and hardware readers that have been layered in over time, often from different vendors and rarely designed to work together from the start. The strength of the platform, and its partners, is in how well it can bridge that complexity without forcing institutions to standardize first.
When a student’s credential works at the residence hall door, the dining terminal, the library turnstile, and the recreation center access point (even when those environments are running on different access control systems, payment platforms, or generations of hardware), the credential is genuinely useful across campus life. It’s that ability to work across systems that weren’t originally built to connect that makes the experience feel seamless to the student.
When it works only in environments that have been standardized to accommodate it, the experience is partial and the path to expanding it runs through a capital conversation that most institutions aren’t positioned to have quickly. The students who encounter the gaps don’t experience a deployment limitation. They experience a credential that doesn’t work where they need it, which quickly erodes user satisfaction and confidence in the system as a whole.
For IT leaders evaluating platforms, the practical question is whether compatibility extends across the full range of environments students actually move through; not just the environments that have been recently renovated or that happen to match the vendor’s preferred hardware ecosystem. And just as importantly, whether the platform’s partner ecosystem is equipped to integrate across that diversity from day one.
The Platform Question Worth Asking Directly
One evaluation question that tends to get less attention than it deserves: when was the platform’s underlying architecture last reconsidered from the ground up, rather than updated incrementally?
A platform that has been patched and extended over many years carries the design assumptions of the era in which it was originally built: assumptions about how campus systems integrate, how credentials are managed, how access control and transaction systems communicate. Those assumptions don’t disappear with updates. They shape what the platform can and can’t do, and how much effort it takes to make it do new things.
For institutions planning deployments that need to serve them over the next several years, across a campus environment that will continue to change, understanding when a platform’s foundation was last meaningfully reconsidered is a reasonable part of due diligence. Vendors willing to answer that question substantively, with specifics about architecture decisions and the reasoning behind them, are giving institutions something useful to evaluate.
A More Complete Definition of Flexibility
The goal behind vendor flexibility arguments is a reasonable one: institutional control, options, and the ability to adapt over time. Those things matter, and evaluating for them is appropriate.
A more complete version of that goal recognizes that selecting a mobile credential platform is ultimately a decision about partnership. Institutions benefit from working with partners who have demonstrated, over multiple years and deployments, the ability to deliver successfully at scale, maintain high levels of client and user satisfaction, and uphold enterprise-grade information security standards as campus environments evolve.
That evaluation must account for operating across the campus that already exists, with its accumulated hardware decisions, its federated departments, and its integrations built over years, rather than a standardized environment that would need to be created before flexibility becomes accessible.
Campuses are complex by design and by history. The mobile credential platforms that deliver genuine long-term value are the ones built, and proven, to meet that complexity, not to require institutions to resolve it first.
