OutboundGateway is an outbound proxy service that provides static outbound IPs for applications, Kubernetes clusters, containers, and AI agents (including MCP servers). Its core positioning is: without terminating TLS or decrypting traffic, it gives outbound requests a stable, whitelistable EU IP identity.
Uses and main capabilities
- Static, whitelistable EU IPs: Each proxy includes a pair of stable, load-balanced EU IP addresses, providing applications with a consistent outbound identity, suitable for API allowlists, partner integrations, internal firewalls, and production SaaS workloads. The official emphasis is that it does not use rotating IPs or shared pools.
- End-to-end encryption (TLS passthrough): OutboundGateway operates as an HTTPS (CONNECT) proxy and uses SSL/TLS passthrough. Applications establish a direct encrypted TLS connection with the target server, and the proxy does not decrypt, inspect, or modify traffic.
- EU data residency and GDPR: The infrastructure is fully hosted in the EU, helping to meet EU data residency requirements and GDPR compliance obligations; at the infrastructure layer, personal data exposure is minimized, request payloads are not inspected, and decrypted personally identifiable information is not stored.
- Secure proxy authentication: Proxy authentication credentials and CONNECT requests are encrypted via HTTPS over TLS, avoiding plaintext credentials and credential leakage.
- High availability and reliability: Each proxy includes redundant EU IP pairs and supports automatic failover; when an IP becomes unavailable, traffic is transparently rerouted without configuration changes. Designed for production and long-running workloads, with a target availability of 99.5%.
How to use
- The official onboarding process is: create an account and start a free trial; obtain a dedicated, whitelistable static EU IP; point the application to the HTTPS proxy and deploy. The service supports HTTPS proxies only. The official dashboard is provided for configuring proxy settings, and documentation is provided for integration with applications.
Applicable scenarios
- AI coding agents: Provide static IPs for AI coding agents to avoid IP rotation or API blocking.
- Kubernetes static IPs: Provide static egress IPs for Kubernetes clusters, simplifying API whitelisting and eliminating IP rotation issues.
- Scaleway static IPs: Provide static outbound IPs for Scaleway instances, implemented through simple HTTPS proxy configurationIP whitelisting.
- Enterprise static IPs: Used for allowlists, server-to-server authentication, and EU egress when servers, applications, and API integrations require fixed outbound IPs.
- Runtime compatibility: Suitable for any application or runtime that supports HTTPS proxies, including AWS, Azure, Google Cloud, Heroku, virtual machines, containers, CI jobs, and background worker processes.
Limitations and notes
- HTTPS proxy only.
- The official source does not provide specific price amounts, only stating that it is divided by plan: plans for individuals and small projects include 10 GB of bandwidth, 20,000 requests per month, and basic analytics; plans for enterprises and teams include 50 GB of bandwidth and 100,000 requests per month; plans for high-traffic large organizations include 1,000,000 requests per month, dedicated IPs, and proxy resources, with email/phone support.
- Support methods: The official source states that all customers can receive support by email; high-traffic plans additionally provide email/phone support.
- A 7-day free trial is provided.
- The official source does not provide specific performance metrics, SLA details, or third-party review information beyond the above.
