Enference
Automated test range for uncrewed systems

Test the aircraft before it exists.

Enference turns a datasheet and a CAD file into simulation campaigns — contested environments, photoreal replay, manual flight and training data — with no services engineers in the loop.

  • 01Intake
  • 02Simulation
  • 03Contested environments
  • 04Photoreal replay
  • 05Manual flight
  • 06Synthetic data
How it works

Four steps from documents to evidence. One human touch.

The parameter sheet is the contract. Everything downstream — every scenario, every replay, every dataset — traces back to a value you approved and a document it came from.

01
Upload
Datasheet PDFs and the CAD file. The model reads what a manufacturer actually publishes — tables, footnotes, mixed units — and the mesh yields mass properties and frontal area.
02
Confirm
Every extracted value arrives with its verbatim source quote and page. Missing data becomes an open question, never a silent guess. You approve once; the sheet freezes.
03
Run
Scenario matrices across wind, payload, temperature, density altitude, terrain and threats. Hundreds of runs in minutes on a laptop; thousands on a render farm.
04
Deliver
A report with go/no-go envelopes and the limiting factor named. Any run replayable in photoreal terrain. Labelled datasets and operator demonstrations, packaged.
Numbers from the range

Honest numbers, or none.

Every figure below comes from the platform's own engineering runs against a reference airframe. Results are unvalidated design-iteration estimates — we say so on every report.

+1.7%
Simulated vs claimed hover endurance
reference airframe, zero wind
36
Scenarios simulated in seconds
wind × payload × temperature
100%
Parameters with a source quote
or an open question — never a guess
0
Services engineers in the loop
the whole point
Deployment

Runs where the data has to stay.

Controlled technical data never leaves your estate. The whole pipeline — physics, rendering, reports — is built to deploy as a single-tenant installation: your cloud tenancy today, a packaged on-premises installer in development.

Enclave-ready
Single-tenant by design. No multi-tenant upload, no shared queue, no telemetry leaving the site.
Clean dependency chain
Permissive licences only in product code; every borrowed component recorded and auditable.
Generic threat models
Contested-environment presets are parameterised capability classes. Your real threat data stays inside your enclave.

Now onboarding design partners in the United Kingdom.

A small number of uncrewed-systems teams get the platform early and shape what it becomes.

Apply for access