Use cases
Static IP use cases: allowlists, brokers, and partner APIs
You need a static outbound IP when the system you call only accepts traffic from addresses it has allowlisted: a stock broker's order API under SEBI rules, a bank payout API, a MongoDB Atlas cluster, or a partner's firewall. Serverless and PaaS platforms rotate egress IPs, so Fixedmark routes those calls through a dedicated, fixed pair.
- Use case · Indian fintechBank and UPI APIsWhitelist one dedicated IP pair with your bank, UPI partner bank, or GSP, then deploy on Vercel or Railway without re-whitelisting.
- Use case · DatabasesMongoDB AtlasReplace 0.0.0.0/0 in your Atlas IP access list with two dedicated IPs, using the Node driver's SOCKS5 support.
- Use case · DatabasesPostgres and MySQLAllowlist two IPs on RDS, Cloud SQL, or a self-hosted database and connect through SOCKS5 or a local tunnel.
- Use case · IntegrationsPartner API allowlistingGive Salesforce, SOAP vendors, and payment gateways one dedicated IP pair to allowlist, wherever your code runs.
- Use case · AutomationAI agents and automationsGive n8n workflows, Lovable apps, and AI agent tool calls a fixed IP that allowlisted APIs accept.
- Use case · MigrationHeroku migrationMove off Heroku without breaking partner allowlists by running both IP sets in parallel during the switch.
- Use case · PaymentsPayment gateway APIsWhitelist one IP pair for RazorpayX and Cashfree payouts, or lock Stripe keys to it, then deploy anywhere.
- Use case · File transferSFTP allowlistingReach bank, payroll, and EDI SFTP servers that only accept allowlisted IPs, through SOCKS5 or a local tunnel.
Make it fixed.
Fixedmark is in early access. Join the list to get dedicated static IPs when your region opens.