Static IP for Scaleway — EU & GDPR-Based

Static IP for Scaleway — Hosted in the EU

Give your Scaleway applications a dedicated static outbound IP address located in the European Union. Whitelist once. Stay compliant. Keep your infrastructure simple.

api_whitelist.py

import os

import requests

# Load from environment variables

PROXY_HOST = os.environ.get("PROXY_HOST")

PROXY_PORT = os.environ.get("PROXY_PORT", "8443")

PROXY_USER = os.environ.get("PROXY_USER")

PROXY_PASS = os.environ.get("PROXY_PASS")

# Construct proxy URL

proxy_url = f"https://{PROXY_USER}:{PROXY_PASS}@{PROXY_HOST}:{PROXY_PORT}"

proxies = {'https': proxy_url}

# Make request through proxy

response = requests.get('https://api.partner-service.com/secure-endpoint', proxies=proxies)

The Problem

When running workloads on Scaleway, managing outbound IP addresses is harder than it should be

External APIs Require IP Allowlisting

Payment providers, banking APIs, enterprise SaaS systems, and B2B partner APIs all require IP whitelisting for security.

Infrastructure Changes Affect IP Consistency

Scaleway instances scale up and down. Outbound IPs change with infrastructure. API providers reject unknown source IPs.

Managing NAT Adds Operational Complexity

Custom networking, VPC routing adjustments, and cloud-specific workarounds add unnecessary complexity to your infrastructure.

EU Companies Need GDPR-Aligned Infrastructure

European businesses need infrastructure that aligns with GDPR expectations and keeps data within EU jurisdictions.

When a Partner Asks

"Provide the IP address that will access our API."

You need a stable, predictable answer.

The Solution

Use a Dedicated HTTPS Proxy with Static EU-Based IP

Scaleway Application

HTTPS Proxy

(Static EU IP)

External API

The external API sees one fixed EU IP address — every time.

No complex networking changes
No VPC routing adjustments
No cloud-specific workarounds

Why Scaleway Users Choose This

Dedicated static outbound IP
Infrastructure located in the EU
GDPR-conscious setup
Simple application-level integration
No cloud lock-in
Works with VMs and Kubernetes

Designed For

EU Startups

Fast-growing European companies needing reliable API access with compliance

Fintech & Regulated Industries

Financial services requiring EU-hosted infrastructure for regulatory compliance

B2B SaaS Platforms

Business software integrating with enterprise APIs that require IP whitelisting

Enterprise API Integrations

Large organizations with complex API partnerships requiring static outbound IPs

How It Works

Your application runs on Scaleway. 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.

Basic Setup

Configure your Scaleway application with environment variables. This works with any Python-based application.

import os
import requests

# Environment variables (load from .env or secrets manager)
PROXY_HOST = "eu-01.outboundgateway.com"
PROXY_PORT = "8443"
PROXY_USER = os.environ["PROXY_USER"]
PROXY_PASS = os.environ["PROXY_PASS"]

# Configure proxy
proxy_url = f"https://{PROXY_USER}:{PROXY_PASS}@{PROXY_HOST}:{PROXY_PORT}"
proxies = {'https': proxy_url}

# Your Scaleway application makes API calls
response = requests.get('https://api.example.com/endpoint', proxies=proxies)
print(response.json())

📖 Complete Documentation: For detailed examples, error handling, and advanced configurations, see our Python SSL Proxy Guide.

Built for European Businesses

When your partners care about where traffic originates, location matters.

EU-Hosted Infrastructure

Your proxy infrastructure is hosted entirely in the European Union, ensuring data remains within EU jurisdictions.

GDPR-Conscious Environments

Designed for GDPR-conscious environments with data handling practices that align with European privacy regulations.

No US-Based Routing

Traffic is routed entirely within EU infrastructure. No detours through US-based servers that could complicate compliance.

Clear Outbound Identity for Compliance

One static IP address provides clear outbound identity for compliance audits and partner requirements.

Why HTTPS Proxy vs Cloud Networking Changes?

Approach Complexity Cloud Lock-in Time to Setup
Scaleway Public IPs High Scaleway-only Hours
Custom NAT Gateway Very High Scaleway-only Days
Manual Firewall Rules Medium Scaleway-only Ongoing
HTTPS Static Proxy Low Cloud-agnostic Minutes

Your HTTPS proxy:

  • Works across Scaleway, AWS, local dev
  • Requires only environment variable configuration
  • Scales with your workloads

Why Developers Choose OutboundGateway for API Whitelisting

Static IP Guaranteed

One fixed IP for all API requests. Whitelist once, use forever.

Works Everywhere

Scaleway instances, local dev, CI/CD. Same static IP across all environments.

Simple Configuration

Set HTTPS_PROXY environment variable.

No Infrastructure Changes

No NAT gateway configuration. No routing table changes. No VPC modifications.

HTTPS-Only Security

End-to-end TLS encryption. Your API keys stay secure.

Production-Ready

Retry logic and error handling. Session management included.

Get Your Static EU IP for Scaleway

Stop managing cloud networking just to satisfy API allowlists. Start using a dedicated, EU-based static IP today.

€29/month starter plan • 7-day refund policy • Direct founder support

Still Deciding?

We're happy to help you determine if OutboundGateway is the right fit for your EU infrastructure needs.

Contact Our Founders →