No one goes through hell alone

We build the software operating layer for allied warfare

01 Product

Our product

Rugged tablet displaying the AGELAIOS tactical interface.

02 Design directions

We learnt from the field.

01

Dispersion buys survivability

A centralised command post is a target you can find, characterise and strike. The function spreads across dozens of mobile nodes: vehicles, drones, remote sensors and dismounted teams. Each node must stay autonomous, operable by a non-specialist, and rejoin the fleet as soon as the link returns.

02

The spectrum is contested at all times

In the Baltic, jamming and spoofing of satellite signals disrupt even civilian maritime and air traffic. On the front, reference reporting puts Ukrainian drone losses at roughly ten thousand per month, mostly from electronic warfare. A system that assumes the signal is available is not a combat system.

03

Degraded mode is the default mode

Equipment that refuses to start because a signature expired, a licence server is unreachable or an update was interrupted is abandoned. In July 2025, a global satellite outage denied Ukrainian units a link for about two and a half hours. Hardware must always boot, and degrade its posture explicitly rather than refuse service.

04

Tactical and industrial cycles diverge

A countermeasure now appears in two to three days, while re-qualification takes years. The most sought-after components need weeks of lead time and vanish from the market within a few years. Abstraction turns a target change into integration, not a full rewrite.

03 Blog

Newsroom

Engineering notes, field reports and publications.

View all articles
  • Lean production control: unready work is waste, constraints are lifted, only ready work enters the frontier, a promise is accepted not assigned, engineers keep requirements and stop-the-line, specs tests and documents stay on one fact.

    How lean production control keeps our engineers on engineering

    Methodology

    Penrose Tactical built a house production system so developers can multiply their actions without lowering the bar. Work is pulled only when it is ready. Promises replace tickets. Specs, tests and documents stay on the same fact.

  • A build pipeline producing the instance evidence kit, made of an SBOM, a test report, a signed provenance manifest and a requirement-mechanism-evidence matrix.

    Continuous accreditation through evidence produced by every build

    AGELAIOS

    Doctrine

    AGELAIOS produces an instance evidence kit with every release, including an SBOM, a dated test report, signed provenance and a requirement-mechanism-evidence matrix, so the accreditation file can move at the same pace as the software.

  • The five-stage life cycle of a Provider Pack, from manifest to activation, with the software fallback highlighted.

    How a Provider Pack puts silicon on AGELAIOS nodes without a custom integration

    AGELAIOS

    Ecosystem

    A Provider Pack lets a manufacturer expose silicon to AGELAIOS nodes as a signed capability, with a replayable witness session, fleet integrity controls and a mandatory software fallback that keeps the function available when hardware is not.

  • Diagram of two parallel build chains starting from the same revision, converging on a bit-for-bit comparison and producing the audit artifacts.

    The bit-for-bit software factory your auditors will love

    AGELAIOS

    Engineering

    AGELAIOS builds the same revision twice and compares the results byte for byte. See how reproducible images, signed provenance and continuously generated evidence make software assurance easier to demonstrate.

  • The eight-stage AGELAIOS module workflow, from project generation to installation on an emulated node, with the signing stage highlighted.

    Your first AGELAIOS module in one hour

    AGELAIOS

    Ecosystem

    A practical guide to the eight-step AGELAIOS module workflow, from a validated template to a signed package running on an emulated node, with clear choices for contracts and isolation.

  • AGELAIOS emission control model showing four operating states, token-based transmission budgets and planned communication windows.

    When every transmission can reveal your position

    AGELAIOS

    Doctrine

    AGELAIOS turns emission control into an enforceable platform capability with explicit operating states, per-bearer transmission budgets, planned windows and store-and-forward delivery.

  • AGELAIOS signature suites and a fleet progressing from classical to hybrid post-quantum protection one node at a time.

    A practical path to post-quantum fleet security one node at a time

    AGELAIOS

    Engineering

    AGELAIOS protects mesh confidentiality with hybrid X25519MLKEM768 key exchange and supports a controlled, verifiable migration of artifact signatures from Ed25519 to ML-DSA-65.

  • A failed module contained within successive isolation boundaries while the rest of the tactical node remains operational.

    One thousand crashes a night: how AGELAIOS tests failure containment

    AGELAIOS

    Engineering

    AGELAIOS turns anti-cascade behavior into measurable evidence through deterministic supervision, 1,000 nightly crash cycles, concurrent fault storms and a negative control.

  • Three layers of tactical software, with the open execution foundation beneath mission applications and programme integration highlighted as the shared layer.

    Why we open our software foundation

    AGELAIOS

    Doctrine

    Penrose Tactical will release the AGELAIOS Standard Edition under Apache 2.0 so partners can inspect, port and audit the tactical foundation before a programme starts. Operational secrets stay closed. Industrial delivery is what you buy.

04 What we already deliver

Results, not intentions.

2,800+ Automated and end-to-end test suites
235,022 lines of code, predominantly Rust, half of which are tests.
774 structural specifications framing the product.
429 pages of illustrated user documentation at ASD S1000D standard.
6–7 TRL maturity, demonstrated on emulators and commercial hardware.

AGELAIOS is designed as an auditable, specified and documented foundation, ready to embed quickly in any project or programme.

A reproducible build means a third party rebuilds the binary from source and obtains exactly the same result, fingerprint included. That is the reference method to verify that what runs is what was audited.

05 The ecosystem

Together we build the new battlefield standard

A standard is worth only as much as the players who use it. Here are all those we are building with.

06 Who we are

Six people, one shared vision.

Ruggedised hardware

We have designed munitions and computers for severe environments.

Programmes

We have run programmes inside the major prime contractors.

Public procurement

We know how to bid for French and European public contracts.

Generative AI

We command it everywhere it bites: from specification through to validation.

Penrose Tactical

We are a multinational defence company, present in Europe and Asia-Pacific and based in France. We come from the defence industry and we are returning to it to serve, on the timetable the situation sets.

07 Contact

Our team is ready. Put us to the test.