GitLab for a regulated bank, installed with no internet
Amir Salmani,
- no internet access at all
- cold standby, by the bank's rules
- failover nobody notices
The business
A regulated bank’s developers needed a proper code host. The bank’s network has no route to the internet, and its rules don’t allow live replication between its two zones.
The easy answer is to ask for an exception. The useful answer is a design that fits the rules as they are.
The product
- One address for git. It keeps working when the bank switches servers.
- A second server holding last night’s copy.
- A procedure for the switch that the bank’s own team runs.
The tech
GitLab was carried in and loaded offline. TLS comes from the bank’s own certificate authority.
The standby is cold: a backup every night, with a snapshot of the configuration, restored onto the second server. That’s what the rules permit, so the work went into making that restore boring.
The detail that matters: the switch is a DNS change, and the standby carries the same SSH host keys as the primary. Without that, every developer’s git client would refuse to connect and warn of an attack. With it, nobody notices.
It was still running in September 2026.