00
Scenario
Teams that need full infrastructure control use RhodeCode for on-prem deployment, no telemetry, and full data residency.
When source code cannot live in a vendor cloud, RhodeCode runs entirely on hardware you operate — your data centre, your private cloud, or a fully air-gapped network.
Profile
Typical deployment
Deployment
Your hardware or private cloud
Telemetry
None collected
Binding constraint
The code does not leave
Licence
AGPLv3 (CE) · commercial (EE)
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
Installation and upgrade that work with no outbound network access
02
One authentication surface across every repository and protocol
03
Permissions with inheritance and an explicit deny that wins
04
Repository formats that stay standard on your own disks
Where the usual answer fails
A managed platform can offer a region, but not the absence of a vendor. Where the requirement is that nobody else holds the code, hosting is the wrong shape of answer.
02
Cases
How that works in practice
02.1
Unified repository management on your hardware
Manage Git, Mercurial and Subversion repositories from a single platform that lives entirely inside your perimeter, sharing workflow standards across every protocol.
02.2
Centralised user authentication
Plug into the identity system you already run — LDAP, Active Directory, SAML, OAuth, scoped auth tokens — or use the built-in user database. One authentication surface across every repository.
02.3
Fine-grained access controls
Per-repository, per-branch and per-team permissions with inheritance. IP allowlists scope access to networks you trust, and audit logs record every authentication, push and permission change.
02.4
No mandatory telemetry, no phone-home
Production installs run without outbound network access. Licence operations and updates have documented workflows for air-gapped environments, so sovereignty over the code stays with you.
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.