Every campus public-safety director knows the same operating reality. The named incidents that drive board-level attention happen to people; the patterns that precede them happen on infrastructure — the parking garage at 11pm, the side approach to the residence hall, the route between the library and the satellite-lot, the stretch of campus periphery that connects the academic core to the off-campus housing belt. Cameras record. Officers patrol. The dispatch desk runs a tight book. None of it sees the casing, scoping, dwelling, and returning that precedes the named-incident events that follow.

This page is not about the consumer-facing radar product that students arm themselves. That product lives on /safety/campus-radar/. This page is about the institutional layer underneath — the infrastructure tier that the Dean of Students, the Title IX coordinator, the Director of Public Safety, the Director of Residence Life, and the Chief Risk Officer all hold a piece of, and that nobody currently has the sensing layer to address.

The structural gap at the institutional layer.

Campus public safety budgets sit in an awkward procurement middle. Too small for the enterprise-grade physical-security systems integrators (Hexagon, Anduril, Percepto) that built their portfolios around F500 critical-infrastructure customers. Too large to be served by the consumer-grade campus-safety app market that mostly addresses the student side of the equation. The capability gap is structural: the vendor field that has the right perception stack doesn’t have the right unit economics, and the vendor field that has the right unit economics doesn’t have the right perception stack.

The result is that the institutional buyer — the Dean of Public Safety, the Title IX office, the Director of Residence Life — has a documented risk-management obligation, a campus-board’s attention, and the legal exposure that comes with both, and nothing operationally between “more patrols” and “another camera.” Public safety is an information problem, and the information layer doesn’t exist at the institutional procurement tier.

What Edge Orbital is building.

Real-time situational awareness for the campus perimeter, designed against three architectural premises:

1 · Behavioral pattern detection, not bounding boxes. The detection layer recognizes casing, scoping, dwelling, returning — the activity sequence that precedes a named-incident event on the campus periphery, the same pattern shape that precedes a coordinated physical attack on a co-op substation or a copper-theft event at a rural distribution site. The discriminator is built to separate the routine maintenance crew from the third visit by the same vehicle in the same week, the late-shift custodian from the unfamiliar presence drifting against the residence-hall approach at 1am.

2 · Each site stands alone. The monitoring node runs full perception locally. No central-cloud dependency, no campus-IT-integration cost in the critical path, no assumption of perfect connectivity on the parts of campus where cellular dead-zones and dorm-basement environments matter most. Decentralized is an architectural property, not a marketing word.

3 · Institutional-budget pricing, public-safety-routed alerts. The system is sized to the campus public-safety operating budget, not to an F500-utility’s CapEx envelope. Alerts route to the dispatch desk, the campus public-safety officer, and (under documented escalation paths) the Title IX coordinator and Residence Life — not to a 24/7 SOC contract. The decision to deploy stays with the institution, the conditions stay observable to the people responsible for them. Capability before claim: we are pre-pilot and explicit about it.

The institutional layer, not the student layer.

A campus is two safety systems running in parallel. One is the student-arming system — the radar each individual student turns on for the walk between the library and the dorm, with their three closest people as the response layer. That system is real, it’s already shipping at Edge Orbital, and it lives at /safety/campus-radar/. The other is the institutional layer — the perimeter-sensing tier that the Director of Public Safety, the Dean of Students, and the Title IX office operate, with documented procedures and legal-exposure constraints that are different from the student-arming layer.

These two layers should be designed together, but they are separately procured and separately budgeted. Edge Orbital’s institutional offer is the perimeter-sensing layer — pre-incident detection across the parts of campus that drive the named-incident pattern, with alerts routed to the people who have authority and responsibility to respond at the institutional level. No surveillance of individual students. No facial-identification of identified students against an institutional registry. The system observes the perimeter; the perimeter is institutional infrastructure, not personally-identifiable data on students.

Why now.

• Title IX compliance landscape. The regulatory and procedural environment around campus-incident response has tightened materially. Documented program obligations now extend to risk-anticipation, not only post-incident response.
• Insurance carrier signals. Higher-education risk insurance is pricing institutional physical-security posture more aggressively. The CFO conversation is no longer hypothetical.
• Named-incident cycle. Each public named-incident drives a board-level review, a parent-association response, an enrollment-impact analysis. The cost of the perception gap is rising on every dimension institutions track.
• Vendor-field discontinuity. The consumer-grade campus-safety-app market is well-known to administrators and explicitly does not solve the institutional layer. The enterprise critical-infrastructure-security market is priced for a customer that isn’t a university. The capability gap at the institutional tier is recognized; the procurement option isn’t there yet.

Dual-use, by design.

The same perimeter-sensing architecture that detects a campus-incident precursor detects a copper-theft reconnaissance pattern at a co-op substation or a perimeter-intrusion event at a small-industrial site. The behavioral signature shape is shared; the architectural answer is shared. Dual-use, by design in the precise sense the term means in American Dynamism investing — civilian critical-infrastructure and technology-enabled public-safety capability built on the same perception stack, without re-engineering between use cases.

Who this is for.

• Directors of Public Safety at colleges and universities with documented incident-anticipation obligations and a campus perimeter the patrol-and-camera model wasn’t built to fully cover.
• Title IX coordinators and Dean of Students offices with documented program responsibilities for risk anticipation in addition to incident response.
• Chief Risk Officers and Vice Presidents of Operations at higher-education institutions with insurance carriers asking pointed questions about physical-security posture.
• Residence Life directors at large-residential institutions with perimeter-pattern exposure the consumer-app layer doesn’t address.

The perimeter is the recon window.

Edge Orbital is building real-time situational awareness for the campus perimeter at the institutional-buyer tier — technology-enabled public safety, designed against the vendor-field gap, dual-use by design.

The consumer-facing campus radar lives at /safety/campus-radar/. For institutional deployments, talk to us about a pilot.