Your authority. Our hardware. Their campus.
SafeShield puts a docked aircraft and a set of commissioned observation positions at a school in your jurisdiction. Your agency operates it. When something triggers on that campus, your officers have eyes on the scene before the first unit arrives.
What the agency actually does
SafeShield does not hold flight authority and does not operate aircraft. Your agency does, under the authorization it already holds.
That is not a technicality we work around — it is the design. A launch at a school is a law enforcement deployment, flown under an agency's own operating authority and its own policy, with a trained operator supervising. We build the system, install it, maintain it, and route the video. The flight is yours.
What SafeShield provides
- Hardware and installation.
- Dock, aircraft, and the site survey that establishes commissioned observation positions. Installed on the school's property at the district's cost, not the agency's.
- Triggers.
- Detection running on the school's existing cameras and sensors, producing the events that generate a launch request. No new camera infrastructure required.
- Video routing.
- Streams to your dispatch and to responding units, alongside the school's designated recipient.
- Maintenance.
- Aircraft servicing, dock upkeep, and airframe replacement across the fleet lifecycle.
What the agency provides
- Operating authority.
- The waiver or certificate under which flights are conducted.
- Trained personnel.
- Consistent with your existing DFR staffing model. The system is autonomous once triggered, so this is supervision rather than piloting — a person able to take control, not a person flying every mission.
- Launch policy.
- Your protocol determines what events warrant a launch and who authorizes it. SafeShield generates a request; the decision remains yours.
If you don't have a DFR program yet
A number of agencies we talk to are considering a program but haven't stood one up. A school partnership is a reasonable first deployment: fixed sites, surveyed in advance, a bounded set of approved observation positions, and a flight profile confined to building exteriors, parking, and approach roads.
We can't obtain your authorization for you and won't claim otherwise. But we can be a concrete first use case, and the district often brings funding the agency does not have to find.
Integration
Video routes to dispatch and to responding units. CAD integration specifics depend on your system and are scoped during the briefing rather than promised in advance.
Every alert, acknowledgment, timestamp, escalation step, and launch request is written to an append-only log. That record is available to the agency and the district both, and it is what supports post-incident review.
Limits worth knowing up front
Aerial cameras are poor at identifying weapons from altitude.
Weapon triggers come from fixed cameras at ground level. We don't claim otherwise, and you shouldn't plan around aerial weapon identification.
Aircraft are not always available.
Weather and charging cycles reduce readiness. We publish actual availability rather than implying continuous coverage.
The system observes building exteriors.
It does not detect a threat from someone already inside a school and authorized to be there.
The aircraft does not intervene.
It observes and streams. Its output is information for your officers.
SafeShield is in development. We are looking for a district and agency pair to build the first deployment with, and the agency's operational input shapes the system rather than being accommodated after the fact. If a district in your jurisdiction has raised this with you, the schools page is what they will have read.
Request a briefing
We'll walk through the operating split, what the system does and doesn't do, and what a first deployment in your jurisdiction would involve.