GitHub Docs

The last bastion.

Secure access / PAM for your internal SSH, HTTPS, MySQL and Postgres servers with SSO and RBAC.

No client apps needed.

No client

Warpgate directly exposes native SSH, HTTPS, MySQL and Postgres listeners.

Use it as a git proxy.
Connect your gRPC service through it.
Set it as your DATABASE_URL.

No jump hosts

Warpgate handles authentication, and then transparently forwards the connection to the target server, while making a live recording for auditing.

No paid plan

Warpgate is 100% open-source, free and will stay this way forever.

Warpgate is financed through support contracts, and custom-order feature development.

This allows it to escape the otherwise inevitable cycle of stagnation or VC enshittification.

Pro Support →

No SaaS bullshit

Warpgate is a single binary (or a Docker image) that you download and run locally on your own hardware.

How does all this work?

You download and run a single binary or a Docker container:

You add your services:

You add your users and decide who can access what: (OIDC SSO supported)

Your users get a specially formatted username to connect to targets:

$ ssh c.wilde:staging-env@warpgate.acme.inc

 Warpgate  Selected target: staging-env
 Warpgate  Host key (ssh-ed25519): AAAAC3[...]

 ✓ Warpgate connected

 root@staging-env ~ $

You get audit and observability:

And they get a web interface with instructions so you don't have to keep explaining it:

Sounds good?

Read the docs