Steriod turns plain-language specifications into certifiable, executable Axiom programs — for verification, anomaly detection, root-cause analysis, control, and onboard intelligence.
Today's tools force a choice: ad-hoc, expert-locked, or non-certifiable. None gives you all three.
Engineers re-write Python or MATLAB for every task — verification, anomaly detection, post-pass analysis. Not reusable, not reviewable.
Requirements live in Word and Excel. There is no automated path from a written requirement to a running test or controller.
When telemetry shows an anomaly, engineers grep logs and chase down root cause by hand. Expensive expertise, slow turnaround.
Certification depends on artefacts an external auditor can read and sign. Custom scripts and proprietary models do not qualify.
A domain-specific language for temporal behavioural rules over data streams. Operators describe what the system shall do — Steriod generates a reviewable Axiom program that machines execute.
Engineers and auditors can read a rule with no tool support — it's plain text.
Generated from natural-language specs, requirements, or learned from telemetry.
Plain-text artefact regulators can review, version, and sign off on.
suite is $"EPS Power Health"
expect signal battery_voltage as float
rule $"battery voltage in range" is
expect battery_voltage >= 12.0 and battery_voltage <= 16.8
rule $"low soc triggers low power" is
when battery_soc < 20 then eps_mode = 2 within 5 seconds
No install required. Write Axiom rules, define scripted test scenarios, compile and run them live — then inspect signal timelines and pass/fail results side by side. The fastest way to understand what Axiom can do.
Author .axiom suites with temporal rules and scripted let/wait/expect test sequences — syntax-highlighted in the editor.
The Axiom compiler and runtime run entirely in WebAssembly — no server round-trip, no account needed.
See pass/fail per test, signal values plotted over time, and rule evaluation results — all in one view.
From a written specification to live, certifiable system behaviour — in minutes.
Plain-language description of what the system shall do, an ECSS clause, or telemetry pattern.
Drafts an Axiom program — explains every rule in plain English for human review.
Engineer edits and approves. Auditor signs the .axiom file as a certifiable artefact.
Executes the rules against live or recorded data streams. Same engine, every use case.
Pass/fail timeline, anomaly flags, control directives, traceable evidence for V&V.
Automated V&V and anomaly detection are available today. Root-cause analysis and diagnostics expand on the same data, the same rules, and the same engine — so your investment compounds as you add capabilities.
Continuous verification of system behaviour, with real-time flagging of deviations on telemetry streams. One unified rule layer replaces ad-hoc Python and disconnected alarm thresholds.
Once Axiom is running in your pipeline, the same engine and data unlock: