Legio vs Omnigo: Which campus safety platform is right for your department?

Most campus public safety departments have a presence problem. Officers spend somewhere between a third and half of every shift on documentation — reports filed, classifications applied, notifications logged, records updated. That's a third to a half of the shift not visible on campus. Not at the parking lot at midnight. Not at the residential quad at shift change. Not in the building where the next thing is about to happen.

The software your department runs either makes that worse or makes it better. Most platforms make it worse. They were built to digitize the paperwork, not to absorb it.

Two products show up on most evaluation lists right now. Omnigo — an established incumbent in the campus safety space, assembled over the past decade by The Riverside Company through a sequence of acquisitions. And Legio — a newer platform built specifically for higher education campus public safety, designed around a single premise: the system should do the administrative work, not generate more of it.

So which one fits your department?

Legio is the better fit for departments that want their officers spending less time on documentation and more time on presence. The platform handles classification, routing, and compliance reporting automatically. The Annual Security Report builds continuously through the year rather than being assembled in late summer. Implementation is free and typically scoped in weeks.

Omnigo is the better fit for departments that have spent years building deep Report Exec configurations and prioritize continuity with the workflows their staff already know.

The two products differ on architecture, on how compliance is handled, on what each platform asks of officers in the field, on the company behind the product, and on what an implementation actually costs. Here's the side-by-side, based on product research, public user reviews, and the operational reality of running a campus public safety department in 2026.

TL;DR

Overview

Legio

Legio is a campus safety operations platform built specifically for higher education public safety departments. The platform exists to do one thing: reduce the administrative burden that's currently eating into officer time.

Officers don't sit in front of forms. They capture what happened. The system handles the rest — classification, routing, notification, compliance, reporting. An incident captured in the field is classified against Clery categories at the moment of creation. Geography logic runs automatically. The Annual Security Report builds continuously through the year from operational data, not from a spreadsheet exercise in September.

Legio comes as one system, not a catalog. The modules — Incident Management, Guard Tour, Dispatch, Regulatory Compliance, Emergencies, Parking, Lost and Found, Policy Management, Asset Management — all run on the same operational record. No double entry. No reconciliation between modules at year-end. No add-ons licensed separately.

The company is independent and founder-led. The team's pedigree includes building and running a global leader in security software for nearly a decade — meaning the founders have already done the work of taking a security platform from early stage to enterprise scale, and Legio is the product of what they learned doing it.

Legio currently runs a design partner program for institutions willing to engage early. Partners get direct access to the founding team and influence over product architecture — not feature requests routed through a CSM queue.

Omnigo

Omnigo is one of the more established names in campus safety software. The company describes itself as serving around 2,000 customers across 20 countries, with roughly 800 of those in higher education. Other verticals include healthcare, law enforcement, gaming, hospitality, corporate security, courts, and K-12.

The product surface is wide. It is also accumulated.

Omnigo's core product, Report Exec, traces back to Competitive Edge Software, founded in 1995 by Sean Mars, a former Oak Creek police officer. The Riverside Company, a private equity firm, acquired the platform in October 2016 and rebranded it as Omnigo through the 2017 merger with Information Technologies, Inc. Since then, Riverside has bolted on five more companies: iView Systems out of Toronto in 2017 (visitor management, gaming surveillance), 360° Stay Safe out of Minneapolis in 2018 (training), QueTel out of Chantilly, Virginia in 2020 (evidence management), and Incident Response Technologies — makers of Rhodium — out of Greenwood Village, Colorado in 2021 (incident command).

Each was a real product solving a real problem at a real company. They have since been folded under one brand. The current module catalog runs to nearly forty.

There's a pattern here worth knowing. Private equity roll-ups in mature software categories tend to follow a predictable arc: aggressive acquisition in the early years, integration spend through the middle years, and then a gradual reduction in R&D investment as the platform enters its harvest phase. Omnigo is now nine years into Riverside ownership, with the last acquisition four years behind it. The trajectory of platforms in this part of their lifecycle is well-documented across the SaaS industry, and customers planning a decade-long buying decision should factor it in.

Feature-by-feature comparison

Architecture: built as one, or assembled into one

This is the most consequential difference between the two products, and it's the one most easily missed in a demo.

Omnigo's architecture is the architecture of a roll-up. Six product lines — Report Exec, ITI, iView, 360° Stay Safe, QueTel, Rhodium — built by different teams in different cities for different markets, brought together under a single brand. The integration is real at the marketing layer. At the deployment layer, customers tell a more complicated story.

A Software Advice reviewer described the friction directly: "Everything extra to do within iPass is either an extra module or doesn't seem to work properly." Another flagged the data side: "Our data cannot be exported out of the software." Neither complaint is unusual for a private-equity roll-up — the strategy works by extending product surface through acquisition, integrating under one brand, and shipping the SKU. Customers experience a wider catalog with more seams.

Legio is built as one platform. One operational record. One database. The Incident Management module, the Guard Tour module, the Clery Compliance module, the Lost and Found module — none of them is a separate product wrapped in a shared login. They are facets of the same underlying system, designed together, on a technology stack that didn't exist when Omnigo's core code was written.

That last point matters more than it sounds. A platform built in 2026 carries none of the architectural baggage of a platform built in 2005 and patched forward for twenty years. The development paradigms are different. The data model is different. The way the system handles real-time operations, mobile capture, cross-module workflow, and automated classification is different — not because of feature work, but because the underlying technology has changed.

For a department signing a five-to-ten-year contract, this is the future-proofing question. Buying into a roll-up in its late-cycle harvest phase is a different decision than buying into a platform whose R&D investment is still front-loaded.

Incident capture and the cost of horizontal configuration

Officers report. Supervisors review. Reports get filed. Both platforms do this. The difference is in what officers have to click through to get there.

Omnigo's Report Exec is highly configurable. That sounds like a feature. In practice, it's the consequence of selling the same product to gaming surveillance teams, hospital security, municipal law enforcement, K-12 schools, and college campuses. A product trying to serve all of those buyers has to be infinitely configurable on top of a rigid underlying architecture. The architecture was set in 2005. Everything since has been a configuration layer.

The cost shows up in two places. The first is money. Configuration work in Omnigo deployments is non-trivial — incident types, picklists, workflow rules, role permissions, and module integrations all have to be built out for each department. The second is usability. Officers in a configured Report Exec deployment click. A lot. The rigidity beneath the configuration means that flexibility at the form level translates into form depth at the field level. More fields, more pages, more clicks per incident.

This is not a bug. It's the trade-off Omnigo made by selling horizontally to every vertical. A product trying to be everything to everyone ends up being a configuration framework, not a product.

Legio is built specifically for higher education campus public safety. The incident taxonomy is campus-specific. The classification logic is campus-specific. The geography model is campus-specific. There is no configuration layer trying to bridge a casino floor and a residential quad. Officers see the form that matches the incident in front of them. The system has already made most of the decisions Omnigo asks the officer to make manually.

What the system does versus what the officer does

Most incident management platforms are forms. The officer's job is to fill them in. Type the make. Type the model. Type the plate. Select the violation. Select the location. Select the supervisor. Save.

Legio is built on a different assumption. The officer captures evidence. The system does the work.

Take a parking violation. On a typical platform, an officer pulls out a phone, opens the app, navigates to the citation form, types the plate number, types the make, types the model, picks the violation code from a dropdown, picks the location from a list, and saves. Six fields minimum. Two of which the officer is re-typing from information they're staring at on the windshield.

In Legio, the officer takes a picture of the car. The system reads the plate, identifies the make and model, and tags the location. The officer documents the infraction. That's it.

That's one example. The pattern runs through the platform. Where another system asks for a form, Legio looks for evidence — a photo, a video clip, a location ping, a body camera capture, an existing record — and parses what the system can parse on its own. The officer's job is to capture what happened and document the call they made about it. The administrative tail is the platform's job.

By contrast, the Omnigo Mobile companion app follows the legacy pattern. It's a mobile front-end to the desktop forms. App Store reviews describe reliability issues — one user wrote that the app had been broken on newer iPhones for three months without a fix, "causing all types of parking issues let alone the loss of revenue in violations." Whatever the reliability state at any given moment, the design assumption is the same as it was in 2005: the officer fills in the form.

Clery Act and regulatory compliance

This is where the architectural difference becomes operational.

Omnigo's Clery Reporting is a workflow within Report Exec. The product line is bundled into the Report Exec for Education offering — it isn't licensed as a separate add-on, though it does function as a separate area of the suite from where incidents are captured. The marketing line on Omnigo's Clery page is accurate as far as it goes: "Compiling the data takes seconds — not hours." That's true once the data is in the right state.

The work the sentence skips is the classification work. Applying Clery categories to incidents that were originally logged under operational categories. Reconciling geography. Resolving the gap between the field officer's incident type and the Clery taxonomy. In most departments running Omnigo, this work happens at year-end. Pulled together in late summer for the October 1 deadline. Handed to a Clery coordinator who reconciles, classifies, signs off, and hopes the audit trail will hold up under review.

Legio's Regulatory Compliance is built into the incident workflow. Every event is classified at the point of capture. Geography-aware logic handles the on-campus, residential, non-campus, and public property determinations automatically. Timely Warning trigger logic runs as part of the incident routing — not as a separate decision the supervisor has to remember to make at three in the morning.

The Annual Security Report builds continuously. By October 1, the data is already there. The Clery coordinator reviews, verifies, and submits. No reconciliation phase. No fall scramble.

Guard tour, dispatch, and patrol operations

Most platforms approach guard tour as a checkpoint problem. The officer walks to a fixed location, scans a tag or hits a button, and the platform logs it. This is the model from a generation ago, when patrol meant a fixed route through a fixed set of locations.

Campus patrol in 2026 doesn't look like that. Coverage is the question, not checkpoints. Where are officers spending time? What zones are getting attention? What zones are getting missed? Where is the next incident most likely to come from, and is anyone close to it?

Legio's Guard Tour module is built around coverage, not checkpoints. The platform tracks where officers are, where they've been, and where the gaps are — in real time, on the same operational record that powers Incident Management and Dispatch. When something happens during patrol, the incident record is created with patrol context already attached. There is no separate report to cross-reference later.

Omnigo offers Guard Tour as one of its acquired product lines. The capture works. The reporting works. The integration with the rest of the platform — particularly with the incident record — depends on how the deployment was configured.

Dispatch follows the same logic on both sides. In Legio, officers dispatched, response times tracked, outcomes logged — all tied to the operational record. In Omnigo, dispatch is a separately-licensed module that integrates with Report Exec to the degree your deployment was configured to integrate it.

Records, reporting, and getting data out of the system

Beyond Clery, every department produces a steady stream of reporting. The Daily Crime Log. Monthly briefings to leadership. Ad-hoc records requests from general counsel. Statistics for the chief's board update. The occasional FOIA response.

Omnigo offers reporting tools across its modules. Departments with strong technical staff get a lot out of them. Departments without, less. The "our data cannot be exported out of the software" complaint from a Software Advice reviewer is worth taking seriously — not as a universal experience, but as a recurring concern when departments need data out of the system in a hurry.

Legio approaches reporting from two angles. The first is a structured reporting engine — the kind of thing every platform offers, but built against a single operational record rather than across federated module databases. The Daily Crime Log generates from incident data without a separate workflow. Monthly summaries pull from the same source.

The second is natural language. For ad-hoc requests — the question a chief gets at 4pm on a Thursday from the general counsel's office that needs an answer by Friday morning — Legio supports natural language queries against the operational record. The chief types the question. The system returns the data. No SQL. No ticket to IT. No three-hour configuration session in the reporting module.

This is one of the practical benefits of having been built in 2026 rather than 2005. The technology to do this at production quality wasn't available when Omnigo's core was designed.

The company behind the product

A software decision is also a vendor decision.

Omnigo has been owned by The Riverside Company since October 2016. Riverside is a global private equity firm with a long-running mid-market portfolio. Under Riverside's ownership, Omnigo's acquisition cadence ran steadily from 2017 to 2021, then went quiet. The company has roughly 134 employees per PitchBook, has the resources to maintain the platform, and is profitable.

The standard PE-ownership trade-offs apply. Glassdoor employee ratings sit at 2.6 out of 5, with recurring themes around turnover and management changes in current and former employee reviews. Kevin Lafeber is the current CEO, joining after a stint as a strategic advisor.

Legio is independent and founder-led. The founding team's pedigree includes building and running a global leader in security software for nearly a decade — taking a security platform from early stage to enterprise scale, with the operational and product lessons that come from doing that work. Legio is the platform built on top of those lessons.

For departments that need the comfort of a PE-backed incumbent with a long track record, Omnigo is the more familiar choice. For departments that want to work with founders who have already built a category-defining security platform and are now doing it again — with the architecture and technology choices that benefit from hindsight — Legio offers something Omnigo structurally cannot.

Implementation: configuration cost versus free deployment

Omnigo implementations are typically multi-month engagements. The marketing positions this as configuration depth — a feature. In practice, the cost is real and it cuts two ways.

The first cost is monetary. Configuration time is paid time. Whether the configuration work is done by Omnigo's services team or by department staff, the hours add up. For a typical campus deployment, the implementation engagement runs through a budget cycle.

The second cost is operational. The configurability isn't free at the user level either. Every configuration choice made during implementation produces a downstream click for an officer or a step for a Clery coordinator. The flexibility is real. The cost of that flexibility is rigidity beneath the surface and complexity above it. Configuration on a 2005-era core is still working with a 2005-era core.

Legio takes the opposite approach. Implementation is free. The incident taxonomy is built into the product. The Clery classification logic is built into the product. The geography model is built into the product. Implementation work focuses on the variables that actually vary department to department — campus geography, role hierarchy, notification rules, integrations with adjacent systems. Most deployments are scoped in weeks.

This is what a platform designed for one vertical, on current-era technology, makes possible. There's no horizontal configuration framework to wire up because the platform isn't trying to be everything to everyone.

Pricing

Neither company publishes pricing publicly. The structures are different.

Omnigo is module-licensed. Departments typically license Report Exec as the core, then add modules — Clery is bundled in the Education offering, but Dispatch, Visitor Management, Evidence, Mobile, Guard Tour, and others are licensed separately. The base reflects deployment size. Modules add to the total. Implementation is quoted separately and is not trivial. Multi-year commitments are standard. Costs compound over time as the suite expands.

Legio prices on a single subscription. The full module catalog is included — Incident Management, Guard Tour, Dispatch, Regulatory Compliance, Emergencies, Parking, Lost and Found, Policy Management, Asset Management. No per-module licensing. No tiered access to features. Implementation is free.

The "free implementation" line is worth pausing on. In a category where deployment engagements routinely run six figures, removing that cost is not a marketing tactic. It is a function of the architecture. A single platform designed for one vertical doesn't require the implementation depth a configurable horizontal suite requires. Legio doesn't charge for it because Legio doesn't need to.

Pros and cons

Which platform should you choose?

Why Legio is the stronger choice for most campus departments in 2026

The buying decision in 2026 comes down to a different question than it did in 2016.

Ten years ago, the question was whether your records were digital. Most weren't. The category that became Omnigo existed to solve that problem, and it solved it. Twenty years later, that problem is solved everywhere. Every department's records are digital.

The question now is different. The records are digital. The compliance burden has hardened. The officer headcount hasn't grown. The thing that has to change is the amount of officer time the platform absorbs versus the amount of officer time the platform consumes. The platform has to do more of the work, or the work doesn't get done.

That's the architecture Legio is built around. Compliance as an output of operations. Field capture as evidence, not as forms. Reporting as a question you can ask, not a workflow you have to configure. Implementation as something that happens in weeks, at no cost, because the platform was built to deploy that way.

For most campus public safety departments in 2026, that's the right architecture.