Self-hosted

Your codenever leavesyour infrastructure.

Run Jericho entirely inside your own network. Local inference, local verification, local test execution — no outbound calls in this mode.

Request accessHosted vs self-hosted

Audience

Who it's for

01/regulated industries

Regulated industries
Finance, healthcare, and other teams bound by data-residency and compliance requirements.

02/government

Government
Public-sector environments where source code cannot leave controlled networks.

03/air-gapped

Air-gapped environments
Networks with no outbound internet access, where every dependency runs locally.

Deployment scope

What's included

Everything required to run Jericho on infrastructure you own — no cloud dependency in self-hosted mode.

01/local stack

Full local stack
Retrieval, verification, and test execution all run on hardware you control.

02/no egress

No external API calls
In self-hosted mode, nothing about your code or traces leaves your network.

03/per deployment

Unlimited developers
Licensed per deployment, not per seat. Onboard the whole org.

Deployment model

Hosted vs self-hosted — the honest version

Both are legitimate. Hosted optimizes for speed and simplicity; self-hosted optimizes for control and isolation. Pick based on your constraints, not marketing.

network: cloudinference → third-party APIs · store=false

Hosted

Uses cloud inference APIs for the fastest setup and lowest maintenance. Your code and traces are sent to those APIs to produce a fix — nothing is stored after the request completes.

network: localinference → on-prem · egress=none

Self-hosted

Fully local and air-gappable. More setup to stand up, but no code or trace leaves your infrastructure. The right choice when residency and isolation matter.

Keep your code in-house.

Request access to discuss a self-hosted or air-gapped Jericho deployment.

Request access