One window on the whole ground segment.
JiLux is an operations cockpit that sits on top of the mission control systems you already run. It reads, never writes, and brings the state of every environment, spacecraft and service into a single view, across segregated networks.
How it works
Collect read-only. Push out. See everything.
Operations teams check a dozen tools on every shift, often on networks that accept no inbound connection. JiLux collects from them without touching them, and gives everyone the same picture.
Adapters probe, read-only
Small adapters run next to your systems and read their state: live values, limits, command history, automation, archives, host health. Queries and file reads only.
Snapshots move one way
Collectors push signed snapshots out of the operational zone. Nothing on the office side ever opens a connection back in, so JiLux fits behind a one-way gateway.
One shared view
A web cockpit with status dashboard, live views, tools and shift handover. A hundred viewers cost the operational systems the same as one.
Principles
Built the way operations people think.
Every JiLux instance follows the same rules. A deployment can tighten them, never relax them.
Read-only by design
No telecommands, no writes, no restarts, no privilege escalation on operational systems.
Push-only across zones
Data flows from the higher security class to the lower one. On-demand refreshes are requests the collector polls, never remote execution.
Provenance on every number
Each snapshot states its source, time and coverage. "No data" and "zero" are never shown as the same thing.
Mission-agnostic core
Topology, thresholds, known noise, local names and runbooks live in a mission pack. The core stays the same for everyone.
Nothing to install
Collectors read your systems remotely, through SSH, SQL or their own APIs. The systems you operate stay exactly as they are.
Your data, your policy
No credentials in code, deployment on your own premises, and no AI model at runtime unless you choose to add one.
Positioning
Next to your M&C, never in place of it.
Mission control systems command the spacecraft. JiLux shows the whole ground segment around them.
| Mission control system | JiLux | |
|---|---|---|
| Role | Controls the spacecraft | Shows the whole ground segment |
| Telecommands | Yes | Never |
| Access to operations | Read-write | Read-only, push across zones |
| Data model | Mission database, TM/TC | Topology, checks, snapshots |
| Users | Spacecraft controllers | Ops and maintenance engineers, shift leads, managers |
Use cases
One core, the whole mission lifecycle.
Only the mission pack and the adapter mix change from one operator to the next.
- Routine operationsHealth of every environment and spacecraft, live views, shift handover.
- LEOP and commissioningPass-by-pass status, time correlation, first-acquisition checks.
- AIT and EGSE campaignsCheckout system and test-bench health, test logs.
- ConstellationsFleet matrix per satellite, outliers, ground-station load.
- Ground-station networksPass plan, link status, data gaps per station.
- NewSpace operatorsA single-zone cockpit on top of open-source mission control.
JiLux is in development.
Early access is by invitation while the core and the first adapters take shape.