Projects

Where it has gone, and where it stands

Four engagements, described at the resolution we are allowed to describe them. Counterparties are not named. Each one says what the situation was, what exists as a result, and where it stands — including the parts that are not ours to decide.

One demonstration completed
A drone running neuromorphic inference on board, in the one domain where a dependence on the cloud is a vulnerability rather than a limitation.
One paid engagement in testing
A global automaker has our hardware inside its own evaluation process. The production decision is theirs, on their timeline.
Nothing weighted, nothing projected
Engagements are listed by status, not by hoped-for value. With one paid engagement in progress, a weighted pipeline would be an assertion, not a measurement.

Defence · autonomous aerial systems

Completed

The situation: A drone whose inference has to happen on board. Bandwidth is narrow, latency is long, and the link may be jammed or gone, so a dependence on the cloud is not a limitation. It is a vulnerability.
What exists: A neuromorphic-powered drone demonstration, completed for a defence counterparty.
Where it stands: A demonstration, not a paid engagement, and presented as such. What it establishes is field performance in the one domain where on-board inference is mandatory, and readiness for that specific integration. Detail is subject to the counterparty’s consent and to export classification.

One pass, and what it sends home

Flagged on board, and sent as a conclusionScanned, and not worth sending

Automotive

In testing

The situation: Perception inside a sealed enclosure with fixed thermal headroom and a hard real-time control loop. The customer runs its own evaluation, on its own timeline.
What exists: A paid engineering engagement with a global automaker. Our hardware is inside their evaluation programme now.
Where it stands: The first phase is a qualification entry point, not a commercial contract, and its significance is who chose to run it: an engineering counterparty capable of rigorous evaluation put our hardware into its own process. The production decision is theirs to make.

One control period, with the deadline in it

The inference, finishing inside the loopSense, actuate, and the deadline

Cybersecurity

Pre-commercial

The situation: Systems in which every transmission is an attack surface, and where the requirement has moved from securing the link to eliminating it.
What exists: A hardware-based security product built on the same substrate as the inference engine. Security here is a property of the architecture, not a layer added to it afterwards.
Where it stands: Close to commercialisation, and a distinct commercial track alongside inference.

Two devices, one key, nothing transmitted

The same state, reached at both endsWhat crosses: the settings, not the secret

Humanoid robotics · autonomous vehicles · protective equipment · edge compute

In discussion

The situation: Four sectors with one shape: a control loop, or a classification, that has to close on the device inside a power envelope conventional silicon cannot meet.
What exists: Co-development and licensing conversations, structured as a first phase of engineering work that converts into field-limited licensing.
Where it stands: Counterparties are not named at this stage. We do not present a weighted pipeline: with one paid engagement in progress and the rest earlier, a weighting would be an assertion rather than a measurement.

One engine, four envelopes

The same engine, unchangedFour hosts, four power budgets

What converts a conversation

The same artefact, every time

A customer-relevant inference workload, executed on custom arrays optimised with tailored memristors for partner solutions at the target power envelope, witnessed by the counterparty. That is what moves a discussion to co-development, and co-development to a licence. It is the milestone the whole programme is built around, and the reason the array architecture is described on the Technology page as the commercial proof point rather than as a single off-the-shelf product.

See what exists today

Have a workload like these? Start with an evaluation.

Every engagement on this page began the same way: a workload, a power envelope and a deadline, profiled against the calibrated device simulator before anyone committed to anything.

Request an evaluation How the technology works

Engagements by status

Have a workload like these? Start with an evaluation.