What exactly is FORGE OS?
A bonded, encrypted software-defined router. It combines every available internet link at a site into one resilient, secure connection back to your network — deployed and run by the people already on site, not a visiting engineer.
Which links can it bond?
Any mix of Starlink / LEO, LTE / 5G, fiber or cable, and GEO satellite. You can add or drop carriers without redesigning the network — FORGE uses whatever is available at each site.
What happens when a link drops?
Nothing you'll notice. MPTCP bonds the links into one session, so traffic keeps flowing on the survivors — it degrades gracefully instead of dropping, and re-adds a link automatically when it returns.
Do we need a network engineer on site?
No. FORGE is built for a non-technical operator: plain-English status, one honest signal per site, and guided setup. If something is wrong, the operator can localize it and hand your NOC exactly what they need for a fast fix.
How secure is it?
Every tunnel is TLS 1.3, mutually authenticated, AES-256-GCM — enforced, never optional. Isolation is fail-closed (lose the tunnel and the site stops forwarding), an allowlist gates every transiting packet, and revocation is instant. A FIPS / STIG hardening path is on the roadmap.
How are sites deployed and enrolled?
Low-touch enrollment: a spoke powers up, authenticates to the HUB, and waits in the NOC's approval queue. An operator approves it once, and configuration arrives automatically — no manual tunnel setup or key handling in the field. Nothing joins your network without a human at the NOC saying yes.
What does the HUB manage centrally?
The FORGE HUB pushes enterprise services — NTP, DNS, authentication, syslog, and SNMP — down to every spoke automatically and keeps them in sync. Operators never hand-configure enterprise service connections.
How does it fit our NOC?
One HUB gives your NOC a single, honest view of every site — live throughput and per-site diagnostic bundles. Because status is truthful (amber for "up but not ready"), the NOC spends its time on real problems instead of chasing false greens.
What performance should we expect?
On our WAN-emulation rig, FORGE bonds real link mixes at roughly 78–87% of the links' combined ceiling with low added latency. Past ~500 ms of path skew (e.g. GEO), it correctly parks the slow link as hot standby rather than dragging the aggregate down.
Can we license or embed FORGE OS?
Yes — FORGE is available for OEM sub-licensing. Ship it inside your own hardware or managed service, under your brand. Talk to us about terms.
How do we get started?
Request a demo or book a pilot. Send us your sites, links, and constraints and we'll come back with a configuration and the expected impact — usually within a day.
Still have a question?
Send it over — or walk the live console and see the answers for yourself.