Lock down AWS, GitHub and your databases to one IP
Allowlisting is one of the simplest and strongest controls you can add. It only works if your team has a stable address. MazeVPN gives everyone, and every pipeline, the same dedicated IP.
Sound familiar?
- SSH and admin ports open to the internet because home IPs keep changing.
- Security groups full of stale /32 entries nobody remembers adding.
- GitHub Enterprise IP allow lists that break whenever someone travels.
How to set it up
- 1
Order the Team plan
25 WireGuard device configs plus the app proxy, all on one dedicated IP.
- 2
Create a config for each person and pipeline
Teammates scan a QR code. CI jobs use the proxy credentials.
- 3
Replace your allowlist with one entry
For example, in AWS:
aws ec2 authorize-security-group-ingress \ --group-id sg-0abc123 --protocol tcp --port 22 \ --cidr 203.0.113.42/32
- 4
Revoke access instantly
When someone leaves, revoke their config. The allowlist never changes.
Do I need to route all traffic through the VPN?
No. You can use split tunnelling so only the allowlisted services go through your static IP.
What happens if the server goes down?
The Business plan gives you two IPs in two cities so you can allowlist both for failover.
More use cases
Static IP for Vercel, Replit & Lovable
Serverless platforms send requests from large, changing IP ranges. When your database, payment partner or internal API only accepts allowlisted IPs, route those calls through your own dedicated MazeVPN IP.
Static IP for n8n, Zapier-style automations & AI agents
Workflow tools and AI agents call dozens of APIs. When one of them requires an allowlisted IP, point that step at your MazeVPN proxy and keep everything else as it is.
Static IP for remote teams
Give your distributed team one trusted office IP, wherever they work. A flat monthly price, no per-seat fees, and a dedicated server that nobody else uses.
Stop getting blocked. Start getting allowlisted.
Your own static IP, live in minutes. Full refund within 3 days if it is not right for you.