Give your GitLab CI/CD pipelines a dedicated static outbound IP address in the European Union. Whitelist your APIs once. Deploy with confidence. Keep your pipelines running.
# GitLab CI/CD variables
variables:
HTTPS_PROXY: "https://user:pass@eu-01.outboundgateway.com:8443"
# Your pipeline job
deploy:
script:
- curl https://api.partner-service.com/deploy
When running CI/CD pipelines in GitLab, managing outbound IP addresses is harder than it should be
Deployment targets, staging servers, CRMs, ERPs, and B2B partner APIs all require IP whitelisting for security. GitLab pipelines need consistent outbound IPs.
GitLab shared runners rotate IPs across jobs. Outbound IPs change with every pipeline run. API providers reject unknown source IPs. Your deployments fail.
When GitLab runner IPs change, your pipelines fail. Deployments get rejected. Webhook deliveries fail. Manual IP whitelist updates are error-prone and slow.
European businesses need infrastructure that aligns with GDPR expectations. CI/CD workloads must respect data residency requirements.
"Provide the IP address that will access our API."
You need a stable, predictable answer for your GitLab CI/CD pipelines.
GitLab CI Pipeline
HTTPS Proxy
(Static EU IP)
External API
The external API sees one fixed EU IP address — every pipeline run.
Building CI/CD pipelines with deployments to secure environments requiring IP whitelisting
Managing GitLab infrastructure and ensuring pipeline reliability across environments
Connecting GitLab pipelines to deployment targets, APIs, and partner services securely
Deploying to partner environments and integrating with external APIs through automated pipelines
Your GitLab CI/CD pipelines run on shared or private runners. 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.
Add the HTTPS_PROXY variable to your .gitlab-ci.yml or configure it in Settings → CI/CD → Variables. This works with all HTTP clients, all languages, and all runner types.
# .gitlab-ci.yml
variables:
HTTPS_PROXY: "https://username:password@eu-01.outboundgateway.com:8443"
# Your pipeline job
deploy:
stage: deploy
script:
- curl -X POST https://api.partner-service.com/deploy📖 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.
GitLab SaaS, self-hosted, shared runners, private runners. Same static IP across all environments.
Set HTTPS_PROXY environment variable.
No custom runner images. No VPC modifications. Pure CI/CD variable configuration.
End-to-end TLS encryption. Your API keys stay secure.
Retry logic and error handling. Session management included.
Stop updating IP whitelists when GitLab runners change. Start using a dedicated, EU-based static IP for all your pipelines 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 GitLab CI/CD pipelines.
Contact Our Founders →