Partnership vision Robot integrations are proposed development work.

More autonomy in the air. More clarity on the ground.

When AI helps plan a flight, the operator should be able to understand the mission, approve its boundaries, and intervene. We want to build independent oversight for civilian drones with the teams that fly them.

Explore a pilot Invite us to your site

For civilian drone makers, inspection teams, and fleet operators.

AI-generated concept of a civilian inspection drone at a coastal wind farm with a ground operator — AI-generated concept art made with fal.ai. Proposed use case, not a product demonstration.

Give each mission an accountable human owner.

Inspection, surveying, and infrastructure teams need to explain where a drone was allowed to go, what it was allowed to record, and how a human could intervene. Our vision is a shared evidence layer around the mission.

Follow the mission

Connect mission intent, operator approvals, changes to the plan, and flight-controller-reported outcomes in one understandable record.
Set boundaries before takeoff

Explore approved operating areas, mission duration, data collection permissions, and the people allowed to change a plan. Flight limits remain enforced by the aircraft’s own systems.
Make intervention explicit

Agree how a human requests hold, return, or landing through supported flight interfaces, and show whether the aircraft confirmed the requested state.

Human intervention, designed for the machine.

For a drone, “stop” needs a flight-safe meaning.

Cutting motor power in flight can create a new hazard. The operator and manufacturer must define the right response for the aircraft and conditions: hold, return, or controlled landing where appropriate. Onboard flight safety and lost-link behavior must continue if the observer or network is unavailable.

ClawMetry is not a safety-rated emergency-stop system. Robot support would need manufacturer integration and validation for the specific use case.

An open layer, built with robot makers.

Our proposal is a shared way to describe tasks, permissions, approvals, and outcomes across manufacturers. Operators could get an independent view while each robot keeps its own local control and safety systems.

Read the founding story and watch the vision video

Proposed responsibilities

People and operating rules

Intent, permissions, and approval

ClawMetry observation and governance

Activity evidence and authorized requests

Manufacturer’s robot controller

Motion, local safety, and confirmed state

Local emergency stops and safety systems stay independent of the observer and cloud.

Begin with one workflow.

Start with simulation, then a supervised civilian inspection scenario with the manufacturer and qualified operator. Observe one mission and its approvals before evaluating intervention requests and lost-link reporting.

Before we start

Does ClawMetry currently control drones or grant flight approval?

No. Drone integrations are proposed partnership work. Operators remain responsible for the permissions and operating requirements that apply to their flights. The pilot would use the manufacturer’s flight-control interfaces and local safety systems.

Why involve a third party?

Manufacturers know their machines best. Our thesis is that an open observation layer can help customers compare evidence, understand permissions, and keep a consistent operator experience across vendors. We want to test that value with partners, while keeping safety responsibilities explicit.

Let’s make safe AI together.

We would love to visit your test site and learn how your team plans, flies, and reviews missions. Together we can explore the evidence and controls that help customers adopt autonomous inspection.