Auditable autonomy, by design.

Every Hivora system, on the ground or in the air, has one behaviour it will always execute: stop safely. A fault in the unit, a lost link to Hivora Hive, a person crossing its path or a single command from an operator all end the same way, with the unit in a known, stationary, safe state.

Safe-stop is not a feature layered on top of the mission. It is the state every mission returns to, and it is verified on your floor during integration before the system goes into production.

• Halts on fault, loss of link, proximity or operator command.
• Aerial units return to base or hold position inside the geofence.
• Validated on site as part of every integration.

Nothing in a Hivora deployment acts anonymously. Each unit and each device is a known identity in Veripass. Each mission is launched under an identified, authorized operator. Each door, floor, load or payment is executed only after that identity has been checked against the policy your organization defined.

Because authorization happens before the action, and not in a review afterwards, the question "who allowed this" always has an answer, and the answer was decided by you.

• Every unit and device holds its own identity in Veripass.
• Missions and commands are attributed to an authorized operator.
• Policy is decided once, in software, and enforced everywhere.

Every decision Hivora Hive takes, every command a device executes and every reading a sensor produces becomes an event in Vectry, with its actor, its cause and its time, written before the action is carried out. A safety incident, an audit or a customer question can be reconstructed step by step, not reassembled from logs.

Sommatic reads that same record to flag anomalies early: a route that deviates, a door that opens at an unusual hour, a fleet availability figure that starts to drift.

• Decisions written to Vectry before they are executed.
• Incidents and audits reconstructed step by step.
• Anomalies surfaced by Sommatic from the same record.

Telemetry, mission records and access events stay in the region you operate in. The control plane runs in the cloud or on your premises, as your policy requires, and Edge Gateways keep sites running locally when connectivity is lost.

What leaves your region is your decision, documented in the service agreement, not a default we chose for you.

• Records kept in your region.
• Cloud or on-premise control plane.
• Cross-border transfers only by written agreement.

If you believe you have found a security vulnerability in a Hivora system, device or service, write to [email protected]. Describe what you found, how to reproduce it and what you believe the impact is. We acknowledge every report, keep you informed while we work on it and credit you if you wish once it is resolved.

Please do not test against systems in production at customer sites, do not access data that is not yours and give us a reasonable window to fix the issue before disclosing it publicly.

• Reports: [email protected]
• Every report acknowledged and tracked to resolution.
• Good-faith research is welcome; production customer sites are out of scope.