Give your Scalingo apps a dedicated static outbound IP address in the European Union. Whitelist once. Integrate with confidence. Keep your apps running.
# Set proxy env var on your Scalingo app
$ scalingo env-set HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
# Restart the app to apply
$ scalingo restart
# All outbound requests now use
# a single static EU IP address
$ scalingo logs
[outgoing] GET api.partner.com - 200 OKWhen running apps on Scalingo, managing outbound IP addresses is harder than it should be
Payment providers, banking APIs, CRMs, and B2B partner services all require IP whitelisting. Your Scalingo apps need a consistent outbound IP to reach them.
Scalingo routes requests through shared infrastructure. Outbound IPs change with container restarts, scaling events, and region changes. API providers reject unknown source IPs.
When Scalingo rotates IPs, your API calls fail silently. Integrations break. Webhook deliveries get blocked. Manual IP whitelist updates across multiple providers are error-prone.
Scalingo is French, hosted in EU data centers. European businesses need outbound proxy infrastructure that aligns with the same regulatory requirements.
"Provide the IP address that will access our API."
You need a stable, predictable answer for your Scalingo apps.
Scalingo App
HTTPS Proxy
(Static EU IP)
External API
The external API sees one fixed EU IP address — every request from your Scalingo app.
Building SaaS products on Scalingo that integrate with external APIs requiring IP whitelisting
Running on Scalingo for EU data residency, needing static IPs for partner integrations
Managing Scalingo deployments and ensuring reliable outbound connectivity for all environments
Running regulated applications on Scalingo that need clear outbound IP audit trails
Your Scalingo app runs in containers. 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.
Set the HTTPS_PROXY environment variable on your Scalingo app using the CLI or the web dashboard. This works with all Scalingo-supported runtimes and buildpacks.
# Option 1: Using the Scalingo CLI
$ scalingo --app my-app env-set \
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
# Option 2: Using the Scalingo Dashboard
# Go to Environment > Add variable
# Name: HTTPS_PROXY
# Value: https://user:pass@eu-01.outboundgateway.com:8443
# Restart to apply
$ scalingo --app my-app restart📖 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 PaaS and your proxy are both EU-based, compliance is simpler.
Your proxy infrastructure is hosted entirely in the European Union — same jurisdiction as Scalingo's French data centers.
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.
Node.js, Python, Ruby, Go, PHP, Java, Scala. Same static IP across all your apps.
Set HTTPS_PROXY via Scalingo CLI or dashboard. One command, done.
No code modifications. Standard environment variable. Works with every Scalingo buildpack.
TLS passthrough means we can't see your traffic. Your API keys stay secure.
Retry logic and error handling. Session management included. Built for 24/7 workloads.
Stop updating IP whitelists when Scalingo changes infrastructure. Start using a dedicated, EU-based static IP for all your apps 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 Scalingo apps.
Contact Our Founders →