About Intella
Success stories
Mission assurance is proved once, before launch. Keeping it live afterwards is where the engineering actually gets tested: small margins, complex data, and decisions somebody has to defend later.
Ask for a demoThese are the programs where we built that.
Reliability and disposal readiness
Knowing how much life is left, before it matters
An operator responsible for safe mission endings needed a better answer than “we will know when something breaks”: how long critical components will really last, and whether a controlled disposal will still succeed when the time comes. Post-mission disposal attempts often fail on spacecraft that still had propellant, after failures that were individually survivable, while a reliability model frozen at Critical Design Review reported nominal status throughout.
Intella developed Hydra, a telemetry-driven reliability and disposal-readiness framework, under the ESA-RISE programme. Using data the mission already downlinks and no supplier failure data, it adjusts failure rates at unit level from stress factors derived from routine telemetry, combines units through the as-flown redundancy topology, and projects each indicator forward to the horizon against which disposal capability was originally qualified. Because in-orbit behavior is not stationary, the forecast is refitted on a rolling window, so it tracks the regime the satellite is in rather than one it has already left.
ISO 24113 admits condition monitoring and requires reassessment before any life extension, but prescribes no method. This is a method: aligned to ESA practice for in-orbit reliability updating, fully explainable down to the unit and stress factor driving each result, and auditable against the telemetry available on any given date. The tool produces the evidence, the operator makes the call.
The framework has been applied to multi-year flight data from three LEO satellites spanning the full mission lifecycle: one still operational, one retired after four years and now decaying toward re-entry, and one that has already re-entered. Actual stress levels frequently differed from design-review predictions, in both directions and by large factors.
Fleet monitoring
One team, a full LEO fleet
An operator was flying a LEO fleet with a lean team, monitoring each spacecraft through conventional tooling. Every additional spacecraft added shift work, and routine confirmation was consuming time that should have gone to engineering.
Mercury was deployed to monitor the fleet, keeping the operational case live: telemetry from across the fleet became qualified events with context attached, instead of parallel streams of alerts. Operators worked from one place.
This became the reference case for the pattern we now build for: monitoring effort that stops growing in step with the fleet.
Lean operations from day one
Building the ops model before the first launch
A commercial operator was preparing its first mission and made a deliberate choice: run lean from the start, rather than scale a team and retrofit tooling later. That meant encoding operational procedures into software before there was anything in orbit to operate.
Intella deployed Mercury alongside the mission’s ground segment, as the place where the operational case runs. Nominal checks, contingency triggers and diagnostic procedures were built as workflows on the operator’s own conops, so the procedures are documented and executable in the same place.
The team goes into operations with its operational knowledge already in the platform, not in the heads of the people who wrote it.
Mission control platform
Building the ops brain for a multi-mission fleet
An operator was preparing to scale from a single spacecraft type to a multi-mission fleet. Different vehicles, different operational modes, a growing team. The existing operations platform was not built for that.
Intella joined the program as a core development partner. We contributed to the platform’s foundational infrastructure, including telemetry, telecommand, authentication, notifications and cloud deployment, and embedded operational assurance natively into the new architecture rather than bolting it on later.
The result is a platform designed not just to manage satellites, but to scale how a team operates them. Early releases are in use by operators, with the roadmap extending to full multi-mission coverage.