Remote site connectivity
Connect the systems your remote site depends on—industrial monitoring, video surveillance, access control, and disaster monitoring—over one consistent network identity.
Sites using Starlink, VSAT, cellular, or broadband may need both predictable outbound connectivity and controlled inbound access. WireGress provides a dedicated static outbound IP, with custom inbound configurations available for discussion.
Plans from $15/month.
Many remote-site links do not provide a stable public identity. Starlink and cellular carriers typically place subscribers behind carrier-grade NAT, VSAT and broadband services often assign changing addresses, and failover between links can change the site's outbound IP without warning.
WireGress gives the site a dedicated static public IP through a managed WireGuard gateway. Traffic routed through WireGress uses the same dedicated public IP across supported uplinks. Your site router manages uplink selection and failover; tunnel connectivity must recover after a connection change.
Use the site's existing remote-access or vendor-managed connectivity where it already meets your requirements. WireGress is a fit when you need an IP identity you control, independent of the local carrier.
Connect site applications to approved monitoring platforms and vendor services. Discuss custom inbound access to an engineering workstation or jump host for authorized diagnostics and maintenance.
Provide a consistent outbound IP for connections to compatible video management platforms. Where required, discuss custom inbound connectivity to an approved NVR or video management server for remote viewing and administration.
Video quality and the number of concurrent streams depend on the site's available bandwidth, latency, and recording configuration.
Support connections between site access-control servers and central management platforms for event reporting, credential synchronization, and administration.
Door operation and emergency egress should follow the system's local design and remain independent of remote connectivity where required.
Support outbound delivery of sensor readings, equipment status, and alerts to central monitoring platforms. Custom inbound connectivity can be considered for authorized diagnostics and maintenance.
Warning delivery, local alarms, backup communications, and operation during an internet outage require a separate resilience design. WireGress supplies connectivity; it does not guarantee emergency notification delivery.
Outbound — included
One dedicated public IP for approved outbound traffic, on every plan.
Custom inbound — by arrangement
Scoped to approved sources and permitted services. Discussed and configured per deployment.
A dedicated WireGress gateway is provisioned with a static public IP assigned to your site.
Configure a WireGuard peer on a supported site router or host. Route selected systems through it, or configure separate peers where appropriate.
Traffic routed through WireGress uses the same dedicated public IP across supported uplinks. Your site router manages uplink selection and failover; tunnel connectivity must recover after a connection change.
Add the IP to the access lists of your monitoring platforms, vendors, and central services.
Where inbound access is needed—to an NVR, jump host, or engineering workstation—contact us to discuss a custom configuration.
Important: A static IP controls who appears trusted at the network edge; it is not a substitute for authentication, TLS, or least-privilege access on the systems themselves. Keep the platform's own security controls in place end to end.
A practical fit for monitoring feeds, periodic reporting, and administrative access that can tolerate a gateway interruption.
Review the Core plan →Better suited to sites where the outbound identity must remain available through a WireGress gateway or facility failure.
Site systems should still use sensible timeouts, local buffering, and retry logic. Network failover cannot preserve every existing session.
Review the HA plan →Yes. The WireGuard tunnel is established outbound from the site, so the carrier link needs no public IP address or port forwarding. The stable public identity comes from the WireGress gateway, not from the local ISP.
No. WireGress is a connectivity layer that runs over your existing uplinks—Starlink, VSAT, cellular, or broadband. It does not replace the internet service at the site.
The dedicated static outbound IP is included in every plan. Inbound access—to an approved NVR, jump host, or engineering workstation—is a custom configuration scoped and arranged per deployment. Contact us to discuss your requirements.
No. HA protects the WireGress side—gateway and facility failures on our infrastructure. If the site's uplinks are down, connectivity is lost regardless. Site resilience requires redundant local uplinks designed separately.
Operated by APYL Inc.
ARIN Member since 2010 • AS53628 • 30+ years infrastructure experience • Operating production infrastructure for businesses worldwide
Tell us about the site, its uplinks, and the systems that need to reach it. We'll confirm whether WireGress is the right fit and what a custom inbound configuration would look like.