Fortanix DSM Static IPs

QuotaGuard gives customer-controlled Fortanix Data Security Manager requests two fixed public IPv4 sources for trusted CIDR restrictions.

Add both subscription addresses as individual /32 CIDRs on the Fortanix application. Requests can keep an approved network origin even when the application's native cloud egress changes.

Fortanix treats application IP whitelisting as an additional authentication restriction, not a replacement for the app's credentials. See Fortanix DSM's application authentication documentation.

Fortanix DSM secure vault reached through two stable QuotaGuard network sources

Give a Fortanix Application Two Trusted CIDR Sources

QuotaGuard's two fixed IPv4 addresses fit Fortanix DSM's application-level CIDR control. Register both addresses so either load-balanced route can satisfy the application's source restriction.

The setting belongs to the individual application's Allowed IP-addresses field. This keeps the network rule attached to the Fortanix application identity that uses it.

Add Both Addresses as Individual CIDRs

Each QuotaGuard subscription receives two static public IPv4 addresses. Enter each address with a /32 prefix, then use Fortanix's ADD ANOTHER CIDR control for the second entry.

Configure the Application, Not the User

Fortanix documents this control for machine applications. Open the application's detailed view, edit Allowed IP-addresses, and select the option that restricts authentication to trusted IPv4 or IPv6 CIDRs.

Reject Unapproved Cloud Egress

Once the restriction is active, Fortanix allows the application to authenticate only when it comes from a listed source range. A request that bypasses QuotaGuard can therefore fail the source check even when it presents otherwise valid application credentials.

Two QuotaGuard source IPs approved in a Fortanix DSM application's Allowed IP-addresses field

Keep Source Restrictions Separate From Application Authentication

QuotaGuard supplies the stable source while Fortanix continues to authenticate and authorize the application. The two controls solve different parts of the request path.

Fortanix explicitly describes application IP whitelisting as an additional restriction and cautions against relying on an IP address as sufficient security by itself.

Preserve the Existing Authentication Method

Fortanix applications can use methods including an API key, certificate, trusted CA, Google service account, JSON Web Token, or AWS IAM. Routing through QuotaGuard does not replace the selected method or the Fortanix permissions attached to the application.

Keep TLS End to End

For HTTPS requests, QuotaGuard opens a tunnel and does not decrypt the application's TLS payload. Client certificates and private keys used for mutual TLS remain between the customer application and Fortanix DSM on both Static and Shield.

Choose Static or Shield by Data Policy

QuotaGuard Static is appropriate for non-regulated HTTPS traffic. Use Shield when the customer's policy requires the customer-to-proxy hop to be TLS-encrypted or when the workload carries regulated data. Neither product makes the complete Fortanix deployment compliant by itself.

Fortanix DSM trusted CIDR and application authentication layers after the QuotaGuard pair

Apply the Right Fortanix Network Control at the Right Scope

A stable QuotaGuard pair can support either a targeted application rule or a broader Fortanix DSM system IP Policy. The Fortanix administrator still decides which control and scope fit the deployment.

Keeping those controls distinct avoids treating an application allowlist as an account-wide rule or assuming a system policy changes every application's authentication method.

Use Allowed IP-addresses for One Application

The application setting narrows where that Fortanix application may authenticate from. It is the focused choice when one service, automation, or workload needs the QuotaGuard pair without changing network access for other principals.

Reserve System IP Policy for Broader Rules

Fortanix's system-level IP Policy can distinguish users from applications and can apply different API classes, including EKMS, KMIP, health, unauthenticated-user, and other APIs. That policy is configured under System Administration and is separate from the application's Allowed IP-addresses field.

Keep Both Sources Through Failover and Changes

QuotaGuard balances traffic across two static addresses and uses health checks with automated failover. Keep both addresses in the applicable Fortanix CIDR rule, including during client migrations, so either healthy route remains approved.

Separate Fortanix DSM application allowlisting and system IP Policy scopes using the QuotaGuard pair

FAQs

Common questions about Fortanix DSM static IPs and QuotaGuard.

Does Fortanix DSM require a static IP?

Only when the relevant Fortanix application or system IP Policy restricts requests by source CIDR. Fortanix says an application with IP whitelisting can authenticate only when it comes from an approved source, so changing cloud egress can be rejected even when the application presents valid credentials. QuotaGuard gives that customer-controlled request path two stable IPv4 sources to register.

Where do I configure IP whitelisting for a Fortanix application?

Open the application's detailed view and edit the Allowed IP-addresses field. Select the option to restrict authentication to trusted IPv4 or IPv6 CIDRs, enter the first CIDR, and use ADD ANOTHER CIDR for the second QuotaGuard address. If the IP Whitelisting setting is not visible, Fortanix instructs the user to contact the System Administrator.

Which QuotaGuard addresses should I add to Fortanix DSM?

Add both individual IPv4 addresses shown for the relevant QuotaGuard subscription. Represent each single address as a /32 CIDR because Fortanix accepts CIDR entries, and do not substitute the QuotaGuard proxy hostname. Both addresses must remain approved because QuotaGuard load balances and fails over across the pair.

Does the Fortanix source restriction replace an API key or certificate?

No. Fortanix describes application IP whitelisting as an additional restriction alongside application authentication methods. The application must still use its configured API key, certificate, trusted CA, Google service account, JSON Web Token, or AWS IAM method, and Fortanix authorization still determines what it may do.

What is the difference between application IP whitelisting and Fortanix system IP Policy?

Application IP whitelisting is configured on one application's Allowed IP-addresses field and limits where that application may authenticate from. System IP Policy is a broader DSM administration control that can distinguish user and application principals and can govern separate API classes. A Fortanix administrator should choose the intended scope rather than treating the two settings as interchangeable.

How long does the QuotaGuard side of setup take?

The network setup is limited to routing the customer-controlled HTTPS client through the subscription and adding both dashboard addresses to the Fortanix CIDR restriction. The actual time depends on whether that client already supports an authenticated HTTP proxy and whether the operator has permission to edit the Fortanix application. Confirm the egress address before enforcing the rule so an unapproved route does not lock out the application.

Should I use QuotaGuard Static or Shield for Fortanix DSM?

Use Static for non-regulated HTTPS traffic when a standard authenticated proxy meets the customer's network policy. Use Shield when the customer-to-proxy hop must also be TLS-encrypted or when the workload carries regulated data. In both products, the application's HTTPS session to Fortanix remains encrypted and QuotaGuard does not decrypt the payload.

Can I get dedicated IPs for Fortanix DSM?

Yes. Dedicated IPs and proxy resources are included on direct Enterprise plans, currently $219 per month for QuotaGuard Static and $269 per month for QuotaGuard Shield. Starter, Production, and Business use shared static IP pairs, but each subscription still receives its own two-address pair to place in the Fortanix CIDR rule.

How should I change the Fortanix allowlist later?

Add the replacement source before removing the old one, verify a harmless request through the new path, and retain both active QuotaGuard addresses. Fortanix supports multiple CIDRs through ADD ANOTHER CIDR, which permits an overlap during a controlled migration. Do not remove the prior source until the replacement route has been confirmed.

Does this integration control connections sent from Fortanix to my application?

No. This page covers outbound requests traveling from the customer's application through QuotaGuard to Fortanix DSM. Fortanix-originated callbacks or service connections travel in the opposite direction and require their own receiver and access-control design. Published Fortanix SaaS service IP ranges do not replace the application source CIDRs described 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

QuotaGuard SHIELD

Why: You handle PHI, payment card data, or sensitive PII and require TLS encryption on the customer-to-proxy hop while preserving your application’s HTTPS session to its destination.
Best For: Regulated industries, financial services, and healthcare.
Key Feature: TLS-encrypted proxy connection with the destination HTTPS session preserved.
Sign Up for QG Shield

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.