Static Inbound & Outbound IPs for Vercel

QuotaGuard gives your Vercel functions two fixed IP addresses that the databases and APIs you call will accept, on every plan tier and across every project you run.

Vercel assigns outbound IPs from shared, rotating ranges, so a destination that allowlists by IP rejects your traffic. You add the two QuotaGuard IPs to that allowlist once, and they hold through every deploy, in both directions.

Static covers most outbound calls. Shield adds SSL passthrough for data a security review will not let a proxy decrypt.

Diagram showing Vercel connecting data inputs to a shield symbol with a lock, representing data security.

How This Compares to Vercel's Native Static IPs

One QuotaGuard plan gives every Vercel project a fixed network identity, in both directions, and the same pair works on any other platform you run. That is the gap Vercel's own Static IPs feature leaves open.

Vercel's Static IPs are a real feature, and for a single Pro project with only outbound calls they may be all you need. The limits show up once you look at plan tier, project count, direction, and what they bill for transfer..

Note: QuotaGuard is designed for connecting Vercel infrastructure to IP-restricted B2B resources like SQL databases, internal APIs, and secure gateways. This solution is not intended for web scraping consumer sites (e.g., social media or ticketing platforms) that block cloud infrastructure.

Wire It Into Next.js the Way the Runtime Actually Behaves

One environment variable routes your outbound calls through your static IPs. Getting the client right is the rest of the job, because Next.js's default fetch does not behave the way most proxy guides assume.

The variable goes in your Vercel Project Settings and reaches your functions as an encrypted value. What you do with it depends on which HTTP client your code uses and which runtime the function runs on.

One Variable in Project Settings

Add your QuotaGuard connection URL as the QUOTAGUARDSTATIC_URL environment variable in Vercel Project Settings, scoped per environment so Preview and Production can route differently.

It is encrypted at rest, exposed only during build and function execution, and never lives in your source.

Native fetch Needs a Dispatcher, Not Just the Variable

In the Node runtime, Next.js uses the built-in fetch, which runs on Undici and ignores the HTTPS_PROXY variable. Setting the env var alone leaves your traffic on a rotating IP.

Route it by setting an Undici ProxyAgent as the global dispatcher with setGlobalDispatcher, or by enabling NODE_USE_ENV_PROXY on Node 24 and later. The axios and node-fetch libraries instead take an https-proxy-agent. The Edge runtime is more restricted, so route proxied calls from standard Node functions.

Build Steps, Server Actions, and API Routes

The same variable routes outbound calls during the build, which is what database migrations and Static Site Generation need so a firewalled backend does not reject Vercel's build servers.

Server-side calls in your /api routes and Server Actions proxy the same way, so the requests that touch protected resources all leave from your fixed pair.

Diagram showing Vercel project settings linked to Preview and Production with QuotaGuard Static IP routing.

FAQs

Technical answers for routing Vercel Serverless Functions through a dedicated static IP.

Vercel already has Static IPs. Why use QuotaGuard?

Vercel's native Static IPs are a Pro-and-Enterprise feature, enabled per project, on a shared pool of outbound-only addresses, with regional data-transfer fees on the traffic.

QuotaGuard is one flat plan whose two IPs serve all your projects and any other platform you run, with bandwidth bundled and no per-GB overage.

It also adds the two things the native feature does not: a fixed inbound IP for partners and webhooks, and raw-TCP database tunneling.

For a single Pro project with only outbound calls, Vercel's feature may be enough; past that, the proxy is usually cheaper and does more.

Does this work with Next.js native fetch?

Not from the environment variable alone.

In the Node runtime, Next.js uses the built-in fetch, which runs on Undici and ignores HTTPS_PROXY, so a request still leaves from a rotating IP until you wire the proxy in.

Set an Undici ProxyAgent as the global dispatcher with setGlobalDispatcher, or enable NODE_USE_ENV_PROXY on Node 24 and later; if you use axios or node-fetch instead, pass an https-proxy-agent.

The Edge runtime is more restricted, so route proxied calls from standard Node functions.

Why can't I just allowlist Vercel's IP ranges?

Whitelisting Vercel's dynamic ranges opens your firewall to every other customer's traffic on the same infrastructure, which defeats the point of an allowlist.

Your two QuotaGuard IPs belong to your subscription, so the destination can trust your traffic alone.

Because these are cloud IPs, this is for professional B2B allowlisting, not for reaching consumer sites that block cloud ASNs.

How do I verify my function is using the static IP?

From a temporary server-side route, make a request through the proxy to https://ip.quotaguard.com.

It returns the IP the destination sees, which should match one of the two addresses in your QuotaGuard dashboard.

Call it more than once and you will see both, because the pair is load-balanced, so add both to the destination allowlist.

Can I use the static IP during Vercel build steps?

Yes.

With the connection URL set as a project environment variable, build-time outbound calls route through your static IP just like runtime calls.

This matters for database migrations and for Static Site Generation that pulls from a firewalled backend during the build, which would otherwise reject Vercel's build servers.

How do I avoid function timeouts when proxying?

Routing through a proxy adds a small amount of latency, so raise the maxDuration in your vercel.json or route config enough to cover the full round trip of the database or API call.

A function that returns a 504 timeout under a proxy is almost always one whose duration cap was left at the default, not a proxy fault.

Should I use QuotaGuard Static or Shield on Vercel?

Static satisfies the allowlist and is enough for most Vercel apps. Use Shield when the data is regulated under HIPAA, PCI-DSS, or SOC 2, or when a security policy requires that no proxy can decrypt the traffic.

Shield uses SSL passthrough, so it routes the encrypted session without ever holding a key to read it. The allowlist sees a static IP on either product, so the choice is about the data, not connectivity.

What about inbound traffic, and can I get a dedicated IP?

QuotaGuard's outbound proxy covers your functions calling out, and inbound covers a partner or webhook sender reaching your app at a fixed address, which Vercel's outbound-only feature cannot do.

Dedicated IPs are included on QuotaGuard Enterprise, $219 per month for Static and $269 per month for Shield on direct billing, while Starter, Production, and Business share static IPs across customers.

Still have questions?

We don’t outsource Support to non-Engineers.

Reach out directly to the Engineers who built Shield to discuss your specific architecture, integration challenges, or compliance constraints here 👇

🚀 Ready to Get Started? Choose Your QuotaGuard Path

QuotaGuard STATIC

Why: You need a rock-solid, fixed IP for general API access, AI workflows, or standard third-party integrations.
Best For: Developers, startups, and general application connectivity.
Key Feature: SOCKS5 support for secure database access.
Sign Up for QG Static for Vercel

QuotaGuard SHIELD

Why: You handle HIPAA, PCI, or sensitive PII data and require End-to-End Encryption (E2EE) for full compliance.
Best For: Regulated industries, financial services, and healthcare.
Key Feature: SSL Passthrough and key isolation.
Sign Up for QG Shield for Vercel

Trusted by Engineering Teams Everywhere

What our customers say

Customer experiences, in their own words. Swipe or scroll to read more.

We've been using QuotaGuard Static for nearly six years to provide static IP addresses to our clients so they are able to whitelist our network traffic.

Read full testimonial

We've been using QuotaGuard Static for nearly six years to provide static IP addresses to our clients so they are able to whitelist our network traffic.

The service has been hassle free, has never "not worked" or had any downtime to my knowledge. The only time we've reached out to support was during a migration from one cloud provider to another to ensure that we wouldn't cause interruptions in the service ourselves. The service we received at that time was prompt and professional.

Zach ColonVP of Engineering at ItsaCheckmate.comSubmitted Oct 20, 2023

The app's backend runs on serverless functions, and the railway data provider I was using only accepted requests from a fixed IP address. QuotaGuard gave me exactly that, and my passengers' PNR status checks kept working.

Read full testimonial

I used QuotaGuard Static IPs for ClearBerth, my train app for Indian Railways passengers. The app's backend runs on serverless functions, and the railway data provider I was using only accepted requests from a fixed IP address. QuotaGuard gave me exactly that, and my passengers' PNR status checks kept working.

It helped me because I could keep building the app without worrying about how to get a static IP. For a solo developer that is a real relief.

The best thing about QuotaGuard is the owner himself. Michael is kind, thoughtful and genuinely warm. When I wrote to say thank you, he replied personally, said it made his Sunday morning, and offered a returning customer discount for any future project. You do not often get that from a service company. I would happily use QuotaGuard again and I recommend it to any developer who needs a static IP.

Aditya Bhattacharya, ClearBerth

Aditya BhattacharyaFounder of ClearBerth appSubmitted Oct 18, 2026

QuotaGuard provided a static IP address via a SOCKS5 proxy. Setting up the proxy and using it from my server was very straightforward.

Read full testimonial

I have a web app running in Heroku, and that server occasionally needs to FTP files from another host. That host required requests to come from a whitelisted IP address. QuotaGuard provided a static IP address via a SOCKS5 proxy. Setting up the proxy and using it from my server was very straightforward.

Stephen BeitzelCTO, Narrative TechnologiesSubmitted Mar 28, 2024

I use QuotaGuard to connect with various APIs that require IP whitelisting and run web automations that require a country-specific IP. The stability and reliability of the service have been nothing short of exceptional.

Read full testimonial

I use QuotaGuard to connect with various APIs that require IP whitelisting and run web automations that require a country-specific IP. The stability and reliability of the service have been nothing short of exceptional. It simply works as expected and whenever I’ve had any questions Michael and the team are always very quick to respond to emails. I would recommend them without a doubt.

Jose VilchesCEO at SIM StoreSubmitted Oct 29, 2023

QuotaGuard has been a reliable partner for us for many years. Their service has consistently been solid, and when we ran into a more unusual use case, their team understood the situation quickly and worked closely with us to resolve the issues.

Read full testimonial

QuotaGuard has been a reliable partner for us for many years. Their service has consistently been solid, and when we ran into a more unusual use case, their team understood the situation quickly and worked closely with us to resolve the issues. That level of responsiveness and support has made a real difference for us.

Anton Litvinenkoco-founder @ Import2Submitted Aug 11, 2026

QG helped us prove our pipeline and workflow with users and in the end, we would have stayed but we use AWS for all our production so we had to switch. Sorry to go but loved every minute of it!

Read full testimonial

QUOTAGUARD FTW! We used qg for spooling up a prototype that needed access to MongoDB through Heroku without having to use 0.0.0.0 in mdb whitelist. Big nono for privacy and security. QG helped as we were able to add it as a resource in Heroku and test our prototype. As the platform matured, more test users came on board and our bandwidth scaled to a point where we were no longer a prototype so we moved over to AWS which is where our production apps live. The team at QG is beyond awesome. I sent an email and I think within 24hrs or less we had solved the issues with Tim and Michael. The fact they didn't pester after signup was refreshing as well. They are Dev dev's who get it. QG helped us prove our pipeline and workflow with users and in the end, we would have stayed but we use AWS for all our production so we had to switch. Sorry to go but loved every minute of it!

Greg LuttonCEO Exsurgo TechnologiesSubmitted Jun 1, 2026

Even though the issue was bank related, Michael and Randall provided exceptional support and helped me troubleshoot the issue.

Read full testimonial

I've had a issue tunneling requests to my bank's VPOS through QuotaGuard.

Even though the issue was bank related, Michael and Randall provided exceptional support and helped me troubleshoot the issue.

5 stars service, highly recommended!

Ozgur S.FounderSubmitted Jul 21, 2026

The product works great - but where they really shine is the exceptional customer service.

Read full testimonial

I needed to configure a static IP address for my app running on Heroku, so I could connect to an external database in a more secure manner. A colleague recommended Quotaguard as an option.

The product works great - but where they really shine is the exceptional customer service. One of my background workers was sneakily polling, which didnt show on the logs, and the Quotaguard support team showed patience and knowledge helping me get to the root of the problem. Fantastic team.

AlexSubmitted Aug 1, 2024

QuotaGuard is an excellent company to work with, they really helped me out on my API issue. Appreciate them as a partner.

Read full testimonial

QuotaGuard is an excellent company to work with, they really helped me out on my API issue. Appreciate them as a partner.

John William MeyerCEO, Jump FinanceSubmitted Sep 30, 2026

Solid service. :) Does what's on the tin.

Read full testimonial

Solid service. :) Does what's on the tin. They know what they're doing, and I mean that in two ways: (1) their execution of their value offering is *solid*, and (2) they appear undistracted by things that *aren't* what they're doing. A "small, sharp tools", you know?

IsaacLightwardSubmitted Jan 25, 2024

Reliability Engineered for the Modern Cloud

For over a decade, QuotaGuard has provided reliable, high-performance static IP and proxy solutions for cloud environments like Heroku, Kubernetes, and AWS.

Get the fixed identity and security your application needs today.