No vendor cloud. No telemetry. No remote control. No mandatory online licensing. Signed offline updates. A deployed JC!IJB! system never has to connect to us — for anything.
Switch the options below to see which connections a deployment would have. This illustrates the architecture; it contacts no appliance.
| What leaves the appliance? | Answer | Detail |
|---|---|---|
| Vendor telemetry | None | There is no telemetry channel to JC!IJB!. Not for analytics, health, licensing or support. |
| Licence or activation checks | None | No online licence verification and no activation server. |
| Remote commands or kill switch | None | JC!IJB! cannot reach a deployed appliance. There is no management path from the vendor. |
| Software updates | Inbound only, offline | Signed bundles carried in by the customer on removable media, local upload or the customer's own repository. |
| Customer-selected external intelligence feeds | Optional, direct | Requested by the appliance directly from the provider the customer chose — never routed through vendor servers. Off in air-gapped mode. |
| Customer exports | Locally initiated | Evidence bundles and reports leave only when the customer exports them, to a destination the customer chooses. |
| Public-website contact | Voluntary, separate | A message sent through this website is correspondence with JC!IJB!. It has no connection to any appliance. |
A defence that depends on its vendor's servers inherits their outages, their jurisdiction, their staff and their compromise. A vendor that can switch a system off can be made to. JC!IJB! removes the path instead of promising not to use it.
No central vendor server does not mean impossible to compromise. A sovereign system is defended by its own hardening, isolation, integrity checks, external assessment and the customer's operations — described plainly on the security page.
Each protected server or site keeps its own history. Correlation happens inside the customer's domain, on the customer's side, by reading those histories over channels the customer initiates and pins.
Releases are signed bundles with published checksums. An ordinary browser may download them from this website; the appliance itself never contacts it and verifies the signature before anything is installed. How verification works.
Tell us what you need to protect. A briefing is an engineering conversation; it never needs your credentials, network inventories or logs.