Why We Built WireGress
Managing SSH and VPN access sounds simple until you have multiple engineers, contractors, CI/CD systems, and production servers.
We wanted a solution that would:
- give every engineer their own WireGuard peer
- allow applications and CI pipelines to have separate identities
- provide a static IP for firewall whitelisting
- make revoking access a one-click operation
- avoid managing traditional VPN appliances
The result is WireGress.
Instead of sharing VPN credentials, every user and application receives its own isolated WireGuard configuration.
If someone leaves the team, their access can be revoked without affecting anyone else.
Under the hood
WireGress is built around:
- WireGuard
- Docker
- Ruby on Rails
- MySQL
- Redis
- Cloudflare
- REST APIs
…
Typical use cases
- SSH access to production
- Database administration
- CI/CD deployments
- IP allowlisting
- Remote development
- Vendor access
What’s next
We’re actively using WireGress ourselves while operating JodoHost infrastructure and our SaaS products.