accountability for operational AI and sensor data
The Record That Ends the Argument
An accountability layer for operational AI and sensor data. Forge shows operators, as it happens, what their systems saw, what their models produced and who signed for it, and keeps a record that holds up afterward. It runs beside the platforms you already use and never takes custody of the data itself.
Customer-hosted. Enquiry only. No specifications, pricing or demonstrations on this page. Architecture, customers and terms are discussed under NDA.
What the sensor saw

- When
- Which model
- What it produced
- Signed by
- Sealed
What it is
Forge gives the commander and the system a live view of whether a record, a model output or a decision trail is the one that left the source, unchanged. The same record can be checked later by someone who was not there. Accountability is the product. Detection is not.
The overlooked question
Models, Autonomy, Edge Compute. But Who Answers for Them?
Defence programmes invest heavily in algorithms and hardware. The record of what those systems actually saw and did, the thing a board of inquiry asks for first, receives far less attention.
Where it sits
Beside the Path. Never in It
Nothing waits on Forge. Your sensors, platform and operators run as they do today; Forge watches the flow and writes the record. A third party can check that record with no access to any of it.
Stays on Your Side
Forge runs inside your environment. Pioggia never receives, stores or processes your data.
Sits Beside What You Already Run
Forge accompanies your existing platforms. It does not replace them and it does not stand between your sensors and your operators.
Evidence, Not a Promise
Forge records the score your detector produced, and bounds it by what the chain of custody can actually support. It makes no accuracy claim of its own: your number is measured on your traffic, and a third party can recompute it without access to your systems, or to ours.
Mission-critical applications
Every Capability Is Bounded by What It Can Prove
For ISR, target recognition, navigation, threat detection and mission planning, the question after the fact is the same: show me what the system saw and what it did. Forge keeps that answer, live and later.
ISR
What the sensor saw, when, and that nobody changed it after
Target Recognition
Which model, which version, what it produced
Autonomous Navigation
The inputs a platform acted on, kept beside the platform
Threat Detection
A warning and its evidence, signed at the moment it was raised
Mission Planning
The decision trail an inquiry can walk without trusting anyone
Autonomous systems
Built for Systems That Act on Their Own
Drones, ground robots and AI agents now make decisions that no one watches as they happen. Forge keeps the record of each one: what the machine sensed, which model decided, what it did and on whose authority. The record is sealed where it happened and can be checked later by someone who was not there.

Unmanned Aircraft
What each aircraft sensed and decided is signed on board and sealed as it happens. When the link drops, the record keeps building, and it catches up when the link returns: nothing lost, nothing reordered.

Ground Robots
Decisions and commands are signed on the robot itself, with the model build that made them. The record can be checked, message by message, against the robot's own logs.

AI Agents
Every action an agent takes is sealed with the model that decided, the inputs it read and the authority it acted under, whether a person approved it or a policy allowed it.
Data handling
Data That Stays Where the Contract Says
Many contracts sort what a system captures into tiers: some data never leaves the site, some goes only to approved stores, some can be shared. Forge tags every record with its tier as it is sealed and records every request to move it, allowed or refused. You can show exactly what left, where it went and what was stopped.
What changes
The Same System, With a Record It Cannot Argue With
Forge does not touch what your platform does. It changes what you can prove about it afterward.
Without a record
- No proof of what the model was shown
- The operator's word against the vendor's
- Nothing to hand an inquiry but logs someone controls
- Signatures a future quantum computer could break
With Forge
- What was seen, produced and signed, kept beside every step
- Sealed in your environment, under your keys
- Checkable by a third party with no access to anyone
- Post-quantum NIST ML-DSA signatures by default
Forge Is
- Proof, not trust. A record nobody has to take on faith: not the operator's word, not the vendor's, not ours.
- Yours. It runs where your data lives and answers to you. We never see the payload and cannot be made to produce it.
- Built for the moment it matters. The after-action review, the board of inquiry, the ally who asks how you know.
Forge Is Not
- A detector. Bring the models you already trust. Forge makes them accountable; it does not compete with them.
- A cloud. Nothing operational leaves your environment. There is no hosted tier to sign up for.
- A black box. Anyone you hand a Forge record to can check it themselves, with no access to Forge, to us, or to your systems.
Founded
2024, Spain
Intellectual property
Patent pending, US and PCT
Deployment
Customer-hosted, no data leaves
Briefings
Under NDA, by qualified enquiry
Qualified Enquiry
If you operate defence or critical-infrastructure systems and need an accountability record that stays under your control, contact the programme office. Architecture, customers and commercial terms are discussed under NDA, not published here.