Keeping critical systems connected when the network fails.

Every communications link fails in its own way: cellular congests, satellite drops, radio gets jammed, Wi-Fi saturates. Continuity treats all of a platform's links as one pool. It measures the live health of each -- latency, jitter, packet loss, throughput -- scores each on a single 0–100 scale weighted by what the traffic actually needs, and keeps the application on the best available path. When that path degrades it fails over automatically and records why; when the preferred link recovers, it returns. Hysteresis stops it from flapping on noise.

• Discover and classify every network interface on the node
• Measure live latency, jitter and packet loss per bearer
• Score each link 0–100, weighted by the traffic's priorities
• Fail over automatically when the active path degrades or drops
• Return to the preferred bearer once it recovers
• Record every decision, with its reason, on an event timeline

Radios, modems and links are commodities, and bonding and failover are well-trodden. The defensible layer is the policy that decides how to use them. A conventional selector optimises for connectivity -- lowest latency, highest throughput. Continuity's mission policy optimises for the mission, so the same network conditions can produce a different, better decision as the operation changes. That gap, mission-aware policy versus connectivity-only selection, is the moat.

Continuity's decision logic is demonstrated today. The next milestones are about proving it against real hardware, real links and a real operational use case. This is the stage where a design partner changes everything.

Longer-term roadmap, not claimed today: multipath across several bearers at once with critical-traffic replication, and predictive path management that moves before a link fails.

• Hardware-agnostic: it orchestrates the radios and modems a platform already has, rather than being one more box to buy
• Mission-aware: policy decides per traffic class -- command, voice, telemetry, bulk -- not just "is the link up"
• Edge-autonomous: every decision is made locally and keeps working with no cloud connection
• Explainable: each failover is logged with the reason behind it, not hidden in a black box
• Integrates, doesn't replace: designed to sit on existing communications hardware for fast deployment

Continuity is also the resilient-communications layer JEGASEC's other platforms can build on -- keeping a fleet or defence edge node connected across mixed bearers in the field.

• Not a radio, modem or antenna -- Continuity is software that sits above them
• Not an electronic-warfare, jamming or offensive capability of any kind
• Not a fielded, operational or certified system -- a research and demonstration build
• Performance figures quoted are engineering targets, not independently validated results
• Not funded, endorsed or operated by Defence or the ADF

JEGASEC is independent and not endorsed by, affiliated with, or representing the Australian Defence Force or the Australian Government.

Help validate Continuity in the field.

JEGASEC is seeking design partners operating mixed or unreliable communications environments, to validate Continuity against representative hardware and real operational constraints. Natural fits include defence industry, autonomous systems and robotics, emergency management, critical infrastructure, remote operations, maritime systems and field communications. None of these are current customers; we are looking for the first.