Getting Started with WireGress

From zero to stable outbound traffic — and optional inbound access — in under 15 minutes.

WireGress gives you an automated, dedicated egress gateway with your own stable public IP — no infrastructure to manage, no shared resources.

Step 1

Create Your Account & Get Provisioned

Once approved (automated fraud check — most accounts approved in minutes):

Your dedicated gateway (or pair in HA plan) is automatically provisioned in Texas, New York data center (or both based on your plan).
You receive a stable egress IP from our clean APYL Inc ARIN block (since 2010).
High availability with BGP failover is available on Custom deployments.

✓ Outcome

You now have predictable outbound identity.

Step 2

Add Access for a Team Member or System

Go to your dashboard and select "Add New Peer".
Create a separate peer for a team member, server, application, device, or CI/CD pipeline. WireGress automatically generates the WireGuard keys and configuration.
Download the configuration and share it securely with its intended user—or install it directly on the corresponding system.

Note: Each peer is independently controlled. Removing one team member or system does not affect the others.

✓ Outcome

Your team member or system is securely connected and uses your dedicated static public IP.

Step 3

Allow-list Your Stable IP

Your dashboard shows your dedicated egress IP prominently. Share it with:

Vendor API portals
Partner firewall teams
Internal security policies
CI/CD configurations

✓ Outcome

No more updating allow-lists when cloud IPs rotate.

Step 4 · Core Plus

Configure Inbound Access

On a Core Plus plan, forward approved inbound traffic through your dedicated public IP to connected peers:

Select the peer you want to reach and add an inbound forwarding rule in the dashboard.
Map a port on your dedicated public IP to the peer's IP and port (TCP or UDP) — for example, public port 8443 → peer port 443.
Restrict the rule to approved source addresses where supported, then test from an authorized external connection.

Note: Inbound access applies only to mappings you configure. A public IP alone does not expose your peers — keep authentication and device firewall rules in place.

✓ Outcome

Approved services behind your peers are reachable through your dedicated public IP — even behind CGNAT.

Step 5

Monitor & Manage

Real-time bandwidth and peer usage in the dashboard.
Add, pause, or revoke access for individual team members and systems without reconfiguring the gateway.
Everything is fully automated after initial setup.

✓ Outcome

Complete visibility and control with zero ongoing maintenance.

Ready to Get Started?

Create Your Gateway →

Questions?

View Full Technical Setup Guide →
or reply to the confirmation email after signup.

Pro Tips

Most customers are live within 30 minutes of approval.
All gateways are fully isolated — your traffic is private.