01APEX Rocket Systems
Engineered to ascend.
From propulsion hardware toward validated rocket systems.
- Thrust class
- 5 kN class
- Engine cycle
- Gas-generator
- Propulsion
- Liquid
- Hardware status
- Built
Fig. 06Fig. 07APEX propulsion development hardware.APEX propulsion development hardware.
Source: apexrocketsystems.com
02What APEX has built
Built at APEX
5 kN-Class Liquid Engine Demonstrator
Gas-generator-cycle liquid propulsion demonstrator developed as part of APEX Rocket Systems’ propulsion-development program.
- Thrust class
- 5 kN class
- Cycle
- Gas-generator cycle
- Type
- Liquid propulsion
Source: apexrocketsystems.com — Home
Performance figures and test results are shown here only when APEX confirms them. Engine test evidence: owner confirmation required.
Hardware record
9 photographs supplied by APEX · Select to enlarge
03Why an engine is only the beginning
Building an engine is the beginning.
Progressing toward a credible launch system requires coordinated development across propulsion, structures, avionics, embedded systems, software, sensors, manufacturing, quality, testing, ground systems and specialist engineering.
- Propulsion
- Structures
- Avionics
- Embedded systems
- Software
- Sensors
- Manufacturing
- Quality
- Testing
- Ground systems
- Specialist engineering
The engine is where APEX started. Each discipline above is a system of its own, with interfaces to the others.
04Complete rocket system
The rocket as a system of systems
Eighteen domains, each with its own purpose, interfaces and evidence. Select any domain to see what it connects to and who can contribute.
Vehicle hardware
Electronics & embedded
Flight & communications
Ground segment
Assurance & digital engineering
APEX Rocket Systems
Rocket System & Propulsion Program OwnerSpecialist ecosystem partners contribute capabilities. APEX retains system intent and engineering authority.
Solid amber: what APEX holds. Dashed outer ring: where partners contribute.
05Core engineering philosophy
Engineer , then Build , then Prove , then Improve
Confidence is earned in a fixed order. What is learned in each pass becomes the next baseline.
- 01
Engineer
Decide what must be true.
- Requirements
- Architecture
- Interfaces
- Analysis
- Simulation
- 02
Build
Make it, and record what was made.
- Detailed design
- Manufacturing
- Assembly
- Firmware
- Software
- Instrumentation
- 03
Prove
Show it with evidence.
- Inspection
- Component testing
- Subsystem testing
- Engine testing
- HIL
- Integrated testing
- 04
Improve
Learn, and change the baseline.
- Compare
- Investigate
- Update model
- Update hardware
- Retest
06Physical + digital validation
Digital Twin + physical testing
A Digital Twin increases the value of physical testing by helping engineers predict expected behaviour, compare measured results, investigate deviations and improve the next engineering baseline.
Physical
- Hardware built to a recorded configuration
- Instrumented, calibrated and time-synchronised
- Tested to a written objective
- Measured data, events and anomalies recorded
Fig. 03 — APEX propulsion development hardware: close-up of cabling and fluid fittings.
Digital
Show values as a table
| Time | Predicted | Measured |
|---|---|---|
| 0.00 | 0.00 | 0.00 |
| 0.10 | 0.51 | 0.44 |
| 0.20 | 0.76 | 0.73 |
| 0.30 | 0.88 | 0.85 |
| 0.40 | 0.94 | 0.94 |
| 0.50 | 0.97 | 1.07 |
| 0.60 | 0.99 | 1.01 |
| 0.70 | 0.99 | 1.00 |
| 0.80 | 1.00 | 0.99 |
| 0.90 | 1.00 | 0.99 |
| 1.00 | 1.00 | 1.01 |
- Prediction made before the test
- Compared with measurements on the same configuration
- Deviations investigated, not averaged away
- Model or hardware updated, then retested
The Digital Twin never replaces physical testing. It makes each test more informative and each decision better evidenced.
07Development & validation loop
DesignSimulateBuildInstrumentTestCorrelateImprove
Every pass through the loop leaves evidence: a prediction, a measurement, a comparison and a decision. Confidence grows one loop at a time.
Requirements become an architecture and a configuration-controlled design.
- Back to Design
The closed loop in detail
- Requirements
- Design
- Digital model
- Predict
- Build hardware
- Instrument
- Physical test
- Measure
- Compare
- Engineering review
- Model update / hardware update
- Retest
08Engineering ecosystem
No rocket company builds everything alone.
APEX keeps the rocket. Specialist partners contribute capabilities. Digital engineering connects the evidence; physical testing builds the confidence.
09Roadmap
Evidence first. Dates when confirmed.
Each item carries its status and what it rests on. No date appears until APEX confirms it.
- 5 kN-class gas-generator-cycle liquid-engine demonstrator builtDate: owner confirmation required
- Demonstrator in use as the propulsion development platformDate: owner confirmation required
- Manufacturing-led hardware iteration with conventional processesDate: owner confirmation required
- Refinement of engine performance and engine control systemsDate: owner confirmation required
- Integration of active throttle controlDate: owner confirmation required
- Small- and medium-lift launch-vehicle developmentDate: owner confirmation required
- Instrumentation and test-data baseline for engine testingDate: owner confirmation required
- Hardware-in-the-loop bench for engine control firmwareDate: owner confirmation required
- Configuration-aware engine Digital Twin and test correlationDate: owner confirmation required
- + 4 more
10Founders
Building APEX
Arcchit Gopaal
Founder · APEX Rocket Systems
11Collaboration
Build with APEX.
For engineering organisations, manufacturers, test laboratories, researchers, investors and engineers who want to help turn propulsion hardware into a validated rocket system.