Give your serverless functions a dedicated static outbound IP address in the European Union. Whitelist your APIs once. Deploy anywhere. Keep your functions running.
// Serverless function environment variables
process.env.HTTPS_PROXY = 'https://username:password@eu-01.outboundgateway.com:8443';
// Your serverless function makes API calls
return await this.helpers.httpRequest({
method: 'GET',
url: 'https://api.partner-service.com/secure-endpoint',
});
When building serverless applications, managing outbound IP addresses is harder than it should be
Payment providers, banking APIs, CRMs, ERPs, and B2B partner APIs all require IP whitelisting for security. The client needed a static IP for security compliance — API calls had to come from a secured, static IP address within Europe.
Serverless platforms spin up containers on demand. Outbound IPs change with every deployment, region change, or scaling event. API providers reject unknown source IPs. Your functions break.
When serverless IPs change, your functions fail. Critical integrations stop working. Webhook deliveries fail. NAT gateway IPs are unpredictable and shared across customers.
European businesses need infrastructure that aligns with GDPR expectations. Serverless workloads must respect data residency requirements.
"Provide the IP address that will access our API."
You need a stable, predictable answer for your serverless functions.
Serverless Function
HTTPS Proxy
(Static EU IP)
External API
The external API sees one fixed EU IP address — every function invocation.
Building serverless applications with multiple API integrations requiring reliable access
Managing serverless infrastructure and ensuring function reliability across environments
Connecting serverless functions to SaaS platforms, CRMs, and enterprise systems
Automating business processes and integrating with partner APIs securely through serverless functions
Your serverless functions run in the cloud. Outbound HTTPS requests are routed through your dedicated proxy. All requests originate from a single static EU IP. You whitelist that IP once. That's it.
Configure your Lambda function with the HTTPS_PROXY environment variable. This works with all HTTP clients, all languages, and all serverless platforms.
// Lambda function environment variables
process.env.HTTPS_PROXY = 'https://username:password@eu-01.outboundgateway.com:8443';
// Your serverless function makes API calls
return await this.helpers.httpRequest({
method: 'GET',
url: 'https://api.partner-service.com/secure-endpoint',
});📖 Complete Documentation: For detailed examples, error handling, and advanced configurations, see our Python SSL Proxy Guide, Node.js Guide, and all other language guides.
When your partners care about where traffic originates, location matters.
Your proxy infrastructure is hosted entirely in the European Union, ensuring data remains within EU jurisdictions.
Designed for GDPR-conscious environments with data handling practices that align with European privacy regulations.
Traffic is routed entirely within EU infrastructure. No detours through US-based servers that could complicate compliance.
One static IP address provides clear outbound identity for compliance audits and partner requirements.
One fixed IP for all API requests. Whitelist once, use forever.
AWS Lambda, Cloud Functions, Azure. Same static IP across all platforms.
Set HTTPS_PROXY environment variable.
No NAT gateway configuration. No VPC modifications. Pure serverless.
End-to-end TLS encryption. Your API keys stay secure.
Retry logic and error handling. Session management included.
Stop dealing with ephemeral IPs and NAT gateway complexity. Start using a dedicated, EU-based static IP for all your serverless functions today.
€29/month starter plan • 7-day refund policy • Direct founder support
We're happy to help you determine if OutboundGateway is the right fit for your serverless applications.
Contact Our Founders →