FixedmarkStatic IP integrations for serverless and PaaS apps
Any platform that lets your code set an HTTP or SOCKS5 proxy can use a Fixedmark static IP. You store one proxy URL as an environment variable, pass it to your HTTP client, and partners allowlist two fixed IPv4 addresses. Each guide covers why the platform's IP changes, what its native option costs, the exact client code, how to verify the egress IP, and the errors you are likely to hit.
PaaS and containers
- RailwayA dedicated IP pair for Railway services when shared static IPs are not enough.
- RenderAllowlist two IPs that are yours instead of Render's shared regional ranges.
- Fly.ioFly.io's native egress IPs are cheap. Here is when a portable pair still helps.
- HerokuStatic outbound IPs for Common Runtime dynos, and a pair that moves with you.
- Google Cloud RunA fixed outbound IP for Cloud Run services and jobs without a VPC and Cloud NAT.
Serverless and edge functions
- VercelFixed egress IPs for Vercel Functions without the $100 per project add-on.
- Supabase Edge FunctionsFixed outbound IPs for Supabase and Lovable Edge Functions with Deno's proxy client.
- NetlifyA fixed source IP for Netlify Functions without an Enterprise contract.
- AWS LambdaA fixed IP for Lambda without VPC, subnets, and two NAT Gateways.
- Cloudflare WorkersWorkers cannot set a proxy on fetch. The relay pattern that works instead.
Automation and CI
Make it fixed.
Fixedmark is in early access. Join the list to get dedicated static IPs when your region opens.