Legio Raises $5M to Modernize Campus Safety Operations

Legio, a Toronto-based company building an AI-native safety and security operations platform for higher education, has raised $5M in Seed funding. The financing gives Legio more room to develop a system designed around campus public safety work rather than adapting generic enterprise software to a highly specific operating environment.

The company is led by founders Darren Hill, CEO; Joe Crampton, CPO; and Mike Wertman, CTO. Legio has not publicly disclosed the Seed round's lead investor, full syndicate, valuation, or detailed use of proceeds. What is visible is the operating thesis: campus safety teams should spend less time carrying the paperwork generated by incidents and more time on presence, judgment, and response.

That thesis matters because campus safety is not one workflow. It is incident capture, patrol coverage, dispatch, investigations, notifications, parking, policy, asset management, emergency coordination, and regulatory reporting happening across the same physical environment. When those functions live in separate tools, people become the integration layer. The software records the work, but the department still has to reconcile it.

What Legio Is Building

Legio is developing a single operational system for campus public safety. Its platform connects guided incident intake with classification, routing, notifications, dispatch, guard tours, investigations, regulatory compliance, and asset management. Each function is tied to the same operational record, reducing repeated entry and giving leaders a clearer view of what happened, who responded, and what obligations remain.

The company's higher education platform is built around campus-specific conditions. These include changing student populations, complicated geography, mixed sworn and non-sworn teams, residence halls, parking operations, patrol zones, and coordination with local law enforcement. Legio is not trying to make a generic security suite look more academic. It is treating higher education as the product architecture.

That approach is particularly important for Clery Act workflows. Legio says incident data can be classified when it enters the system, with Annual Security Report information built continuously from operational records. The goal is to make compliance a product of daily work rather than a separate reconstruction exercise near the reporting deadline.

Why the $5M Seed Round Matters

Seed capital is most useful when it buys a company the chance to turn a specific insight into repeatable product behavior. Legio's insight is that campus safety software should absorb administrative work without trying to automate the human judgment at the center of safety operations. That is a narrower and more credible promise than claiming AI will run the department.

The distinction is easy to miss. Many legacy systems digitized forms and made records searchable, which was real progress. They did not necessarily remove the classification, routing, notification, reconciliation, and reporting work surrounding those forms. Legio is betting that AI can handle more of that administrative sequence while officers remain accountable for what happened and how they respond.

The company is still in active development. Its website is recruiting a limited group of design partners, and current hiring materials show Legio adding a founding engineer in Toronto. Those signals suggest the immediate job is product validation: working with departments, translating edge cases into architecture, and proving the platform can operate inside environments where reliability and auditability matter more than a polished demo.

The Vertical Software Advantage

Legio sits inside a broader return to vertical software. Horizontal platforms sell flexibility across industries. That flexibility often arrives as configuration work for the customer. Vertical platforms can make stronger product decisions because they understand the terminology, obligations, data relationships, and failure modes of one market.

Campus public safety is a strong test of that model. A university has the operating complexity of a small city, but its population turns over constantly and its departments carry specific reporting duties. The buyer does not need another isolated incident log. The buyer needs an operational spine that connects what officers see in the field with what supervisors, legal teams, leadership, and regulators need later.

Legio's product scope reflects that need. Incident management connects to dispatch. Patrol data connects to coverage. Investigations connect back to the original event. Compliance reporting builds from the same record instead of depending on another export and another round of manual review. The value is not a longer feature list. It is fewer breaks between the features.

What to Watch Next

The $5M Seed round gives Legio a credible opening, not a finished case. The important proof points will be design-partner conversion, production deployments, implementation time, reliability, and whether the platform measurably reduces administrative work without weakening control or auditability. The company has not yet published customer counts or independent performance metrics, so those outcomes should matter more than broad AI claims.

The leadership team has chosen a market where product mistakes are expensive and generic software is easy to spot. Darren Hill, Joe Crampton, and Mike Wertman now have capital to show that domain knowledge can become better operating infrastructure. If Legio succeeds, the meaningful result will not be that campus safety teams use more AI. It will be that the technology fades into the workflow while the people responsible for safety get more time to remain present.