Set up Warpgate as a single entry point so your team accesses all internal servers through one audited, authenticated gateway instead of direct SSH
Record all SSH sessions to your production servers so you have a full playback log for compliance or security incident review
Replace a VPN for internal tool access by routing HTTPS and database traffic through Warpgate with two-factor authentication and per-user target permissions
Requires a Linux server, DNS and firewall must route SSH and HTTPS traffic through the gateway binary.
Warpgate is a self-hosted security gateway that sits between your users and the internal servers or services they need to access. Rather than giving people direct access to servers, you route connections through Warpgate, which authenticates each user, enforces which resources they are allowed to reach, and records everything that happens during the session. It supports several types of connections: SSH (the standard way to access a remote server's command line), HTTPS (regular web traffic), Kubernetes cluster management, MySQL databases, and PostgreSQL databases. Users connect using the same standard tools they already have, with no extra software required on their side. Warpgate intercepts the connection, checks who the user is, and then passes the traffic through to the intended target. Built-in features include two-factor authentication using time-based codes (TOTP) and single sign-on support through OpenID Connect, which lets you integrate with identity providers your organization already uses. Sessions are recorded and can be played back later through a built-in web admin interface. The admin interface is also where you manage user accounts, define which servers and services are available as targets, and assign which users can reach which targets. All of this runs as a single binary with no external dependencies. It is written in Rust and stores its data in an SQLite database by default. The project describes itself as production-ready and is fully open source. The README includes a comparison table showing how Warpgate differs from a traditional SSH jump host, a VPN, and Teleport. The key distinctions are that it requires no custom client software, records sessions at the command level rather than just logging connections, and keeps data fully on your own infrastructure.
← warp-tech on gitmyhub — every repo by this author, as a profile.
Verify against the repo before relying on details.