FixedmarkVercel Static IPs vs Fixedmark: Cost, Limits, Regions
Vercel Static IPs give a Pro or Enterprise project a static IP pair per configured region, shared with a small group of other customers, for $100 per project per month plus Private Data Transfer. No client code changes are needed. Fixedmark is planned as a proxy you call from your function code: one dedicated IP pair from $29/mo that any number of projects, and other platforms, can share. Fixedmark is in early access.
Fixedmark vs Vercel Static IPs at a glance
Fixedmark values are planned launch features and pricing. Vercel Static IPs values are taken from published vendor pages and attributed below. Checked October 2026.
| Fixedmark (planned) | Vercel Static IPs (published) | |
|---|---|---|
| Price | Pro $29/mo per account, dedicated pair | $100 per project per month |
| Data charges | Bandwidth included in plan (200 GB on Pro) | Private Data Transfer at regional rates, $0.15 to $0.31/GB |
| Plan requirement | Any Fixedmark plan, including Free | Vercel Pro or Enterprise |
| IP type | Dedicated pair from Pro | Shared across a small group of customers, with subnet-level isolation. Dedicated Secure Compute is Enterprise only. |
| Regions | One region on Pro, two on Business. Mumbai, Singapore, Frankfurt, New York, Virginia at launch. | A pair per configured region, up to 3 regions per project |
| Code changes | Route outbound calls through the proxy URL | None. All function egress uses the static IPs. |
| Coverage | Node.js runtime functions. Edge runtime fetch has no proxy option. | Vercel Functions, and builds if you opt in. Not Routing Middleware. |
| Direction | Outbound. Inbound on the roadmap. | Outbound only |
| Works off Vercel | Same IPs from Railway, Supabase, GitHub Actions, or a laptop | Vercel only |
| Databases | SOCKS5 for drivers that support it | All TCP egress from functions |
What $100 per project means in practice
Vercel bills Static IPs per project. A team with a production app, a staging app, and a background-jobs project that all call the same allowlisted API pays $300/mo before data transfer. Static IPs apply to every environment in a project, so you cannot turn them on for production only. With Fixedmark, all three projects set the same FIXEDMARK_PROXY_URL environment variable and share one planned $29 dedicated pair.
Per Vercel's docs, the addresses are shared across a small group of customers in the same region, with subnet-level isolation. Dedicated egress through Secure Compute is an Enterprise feature with custom pricing.
Where Vercel's native option wins
Vercel Static IPs need no client code. Every outbound connection from the function uses the static IPs, including database drivers and SDKs that ignore proxy settings. You can also route build traffic through them. With a proxy, you choose which calls go through it, and libraries that cannot take a proxy agent need a workaround. The Edge runtime's fetch has no proxy option, so allowlisted calls must run in Node.js runtime functions.
Selective routing is cheaper
Because a proxy routes only the calls you send through it, traffic to Stripe, your CDN, or OpenAI stays on Vercel's normal egress and does not count against your plan. With Vercel Static IPs, all function egress counts as Private Data Transfer. See the Vercel integration guide for undici setup.
When to choose Vercel Static IPs instead
Use Vercel's native option if:
- You need a static IP today. Fixedmark is in early access.
- You have one project and $100/mo is acceptable, and you want zero code changes.
- Your traffic goes through SDKs or drivers that cannot use a proxy or SOCKS5.
- Your builds also need the static IP.
- You want one bill and one vendor for everything on Vercel.
- You are on Enterprise and need Secure Compute's dedicated network isolation.
When Fixedmark fits better
A proxy URL is the better fit when:
- Several projects, or several platforms, must present the same IPs.
- You are on Vercel Hobby or want a dedicated pair without Enterprise.
- You need egress from Mumbai or Singapore without a per-project fee.
- You want per-connection logs for the calls a partner rejects.
Sources
Checked October 2026. Confirm current details on the vendor's site before you decide. Prices and limits change.
Related guides
- IntegrationVercelFixed egress IPs for Vercel Functions without the $100 per project add-on.
- Use caseMongoDB AtlasReplace 0.0.0.0/0 in your Atlas IP access list with two dedicated IPs, using the Node driver's SOCKS5 support.
- Use casePartner API allowlistingGive Salesforce, SOAP vendors, and payment gateways one dedicated IP pair to allowlist, wherever your code runs.
- ComparisonAWS NAT GatewayThe real monthly cost of a highly available AWS NAT Gateway, and when a static IP proxy is simpler.
- ToolWhat's my IP?Check which IP a destination sees from your app.
Frequently asked questions
How much do Vercel Static IPs cost?
$100 per project per month on Pro or Enterprise, plus Private Data Transfer at regional rates, which Vercel lists from $0.15 to $0.31 per GB. Check Vercel's pricing docs for current rates.
Are Vercel Static IPs dedicated to my team?
No. Vercel says they are shared across a small group of customers in the same region, with subnet-level isolation. Dedicated egress through Secure Compute is available on Enterprise.
Can I get a static IP on Vercel Hobby?
Not natively. Static IPs require Pro or Enterprise. On Hobby, route the calls that need a fixed IP through a proxy from a Node.js runtime function.
Do I need to change my code to use Fixedmark on Vercel?
Yes, a few lines. Create an undici ProxyAgent from FIXEDMARK_PROXY_URL and pass it as the dispatcher on the fetch calls that need a static IP.
Make it fixed.
Fixedmark is in early access. Join the list to get dedicated static IPs when your region opens.