00
Sector dossier · DEF
Government teams use RhodeCode for audit, sovereignty, and air-gap deployment.
Classified and export-controlled development on networks with no outbound connectivity of any kind — where an unexpected outbound connection is not a privacy concern but a security incident.
Profile
Typical deployment
Regulation
ITAR · EAR · NIST 800-171
Repositories
400–3,000
Binding constraint
No outbound connection, ever
VCS mix
All three, often per-programme
01
Constraints
The constraint you arrived with is not unique to you
Which controls each sector treats as a hard requirement, which are common, and which rarely apply. Your row is highlighted.
hard requirement common not typical
| Sector | Air-gapped | Export control | Path-level access | Signed approvals | IT/OT or zone split | Long audit retention |
|---|---|---|---|---|---|---|
| FINFinancial services | Air-gapped: not typical | Export control: hard requirement | Path-level access: hard requirement | Signed approvals: hard requirement | IT/OT or zone split: not typical | Long audit retention: hard requirement |
| DEFDefence & government | Air-gapped: hard requirement | Export control: hard requirement | Path-level access: hard requirement | Signed approvals: common | IT/OT or zone split: hard requirement | Long audit retention: hard requirement |
| AUTAutomotive & embedded | Air-gapped: not typical | Export control: common | Path-level access: hard requirement | Signed approvals: hard requirement | IT/OT or zone split: hard requirement | Long audit retention: common |
| MEDHealthcare & life sciences | Air-gapped: not typical | Export control: not typical | Path-level access: hard requirement | Signed approvals: hard requirement | IT/OT or zone split: not typical | Long audit retention: hard requirement |
| SCIResearch & national labs | Air-gapped: hard requirement | Export control: common | Path-level access: common | Signed approvals: common | IT/OT or zone split: not typical | Long audit retention: common |
| AERAerospace & space | Air-gapped: hard requirement | Export control: hard requirement | Path-level access: hard requirement | Signed approvals: hard requirement | IT/OT or zone split: hard requirement | Long audit retention: common |
| ENREnergy & utilities | Air-gapped: hard requirement | Export control: hard requirement | Path-level access: common | Signed approvals: common | IT/OT or zone split: hard requirement | Long audit retention: common |
| TELTelecom | Air-gapped: not typical | Export control: common | Path-level access: hard requirement | Signed approvals: common | IT/OT or zone split: common | Long audit retention: hard requirement |
| SEMSemiconductor & IP | Air-gapped: hard requirement | Export control: hard requirement | Path-level access: hard requirement | Signed approvals: common | IT/OT or zone split: hard requirement | Long audit retention: hard requirement |
| GAMGames & interactive | Air-gapped: not typical | Export control: not typical | Path-level access: hard requirement | Signed approvals: common | IT/OT or zone split: not typical | Long audit retention: common |
01a
Needs
What the platform has to do here
Four requirements this reader cannot compromise on, and the shape of answer that fails them.
01
Fully offline installation and upgrade from a signed bundle
02
No telemetry, and no connection to RhodeCode by design
03
Deployment on hardware you physically control, in your facility
04
Nationality and IP-scoped access for export-controlled repositories
Where the usual answer fails
Every managed platform requires egress for licensing or telemetry. An air-gapped install is not a configuration option there; it is outside the product.
02
Cases
How that works in practice
02.1
Fine-grained permissions and IP restrictions
Restrict access to sensitive repositories with per-repository, per-branch and per-team controls. IP allowlists scope auth tokens to the networks they should be used from, so a leaked token is not enough on its own.
02.2
On-prem and air-gapped deployment
RhodeCode installs on infrastructure you control — your data centre, your cloud tenancy, or a fully air-gapped network with no outbound calls. There is no required cloud component.
02.3
Audit trail and change traceability
Every push, review and permission change writes to a tamper-evident audit log. Code review attaches each change to the person who authored it and the reviewer who approved it.
03
Next
Tell us the constraint, not the feature list
Deployments in this shape usually turn on one binding constraint. Describe yours and we will say plainly whether RhodeCode answers it — including when it does not.