If you're planning a migration, the good news is that your QuotaGuard static IPs are not tied to Heroku

Heroku is entering Sustaining Engineering mode.
As such, many customers are planning a migration off Heroku. The good news is that your QuotaGuard static IPs are not tied to Heroku. Your IPs, your credentials, and your proxy URL all stay exactly the same on whatever platform you move to. Your firewall allowlists, database security groups, and partner API restrictions don't change.
Since the Salesforce announcement, the most common question I've gotten from customers is some version of: can we keep our static IPs when we move, and what does the process actually look like? I put this page together to answer that directly.
I've been running QuotaGuard as a Heroku add-on partner since 2013. We handled hundreds of migrations when Heroku removed free dynos in 2022. The process is well tested.
On February 6, 2026, Salesforce announced that Heroku is transitioning to a sustaining engineering model. Existing apps keep running. Billing is unchanged for credit card customers. Existing enterprise contracts will be honored and can renew.
What's different: no new enterprise contracts for new customers, no new features, and engineering investment is moving toward Salesforce AI initiatives.
For most teams, there's no immediate crisis. But if you're planning to migrate, or evaluating whether to start, now is a reasonable time to understand what happens to your static IPs.
This is the thing most teams don't realize until they're mid-migration.
QuotaGuard runs on AWS infrastructure, independent of Heroku. Your static IP addresses are assigned to your QuotaGuard account, not to your Heroku dyno. When you provision QuotaGuard through the Heroku marketplace, Heroku is just the billing layer. The IPs live with us.
That means every firewall rule you've configured, every database allowlist entry, every IP-restricted webhook receiver, every partner API with an IP restriction — none of that needs to change when you move your app. You update your proxy configuration on the new platform, and your external integrations never notice you moved.
This is true whether you're moving to Fly.io, Render, Railway, Kubernetes, AWS Lambda, or a bare EC2 instance. QuotaGuard works the same way on all of them.
The process is straightforward. We coordinate the account swap on our side first, so your IPs and credentials are ready before you touch anything in Heroku.
Step 1. Sign up directly at quotaguard.com.
Choose the same plan and service type you have on Heroku. If you have multiple apps using different IPs, you'll need one subscription per app. Plan pricing starts at $19/month for Starter, $49 for Production, $89 for Business, and $219 for Enterprise with dedicated IPs.
Step 2. Email us at support@quotaguard.com.
Let us know you've signed up and you're migrating off Heroku. We'll swap your new direct subscription with your existing Heroku subscription on our side. You keep the same static IPs, the same credentials, and the same proxy URL. Nothing changes in your code or your firewall rules.
We typically turn this around the same day. If you want us available when you make the final switch, we can schedule a time.
Step 3. Save your connection URL before removing the add-on.
This is the step people miss. When you remove the QuotaGuard add-on from Heroku, Heroku automatically deletes the QUOTAGUARDSTATIC_URL or QUOTAGUARDSHIELD_URL config variable. Save it before you remove the add-on.
QG_URL=`heroku config:get -a APPNAME QUOTAGUARDSTATIC_URL`
echo $QG_URL
Step 4. Verify the swap is complete.
Log into the QuotaGuard dashboard from your Heroku app's Resources tab. Confirm the connection URL in the dashboard does not match the config variable you saved. That confirms the swap is done on our side.
Step 5. Remove the add-on from Heroku.
heroku addons:destroy -a APPNAME quotaguardstatic
Step 6. Set the config variable on your new platform.
On your new platform, set the QUOTAGUARDSTATIC_URL environment variable to the URL you saved in Step 3. The format and credentials are identical. Your app connects to the same proxy, with the same IPs, as before.
Platform-specific instructions for setting environment variables are in each integration guide below.
For teams with compliance requirements, QuotaGuard supports:
If your compliance team needs documentation before migration, mention it in your support email and we'll sort it out.
If your team has AWS committed spend, you can purchase QuotaGuard through the AWS Marketplace and apply it toward your committed spend agreement. That means no new vendor approval process, no separate invoice, and the spend counts toward AWS budget you've already committed.
We have two listings on AWS Marketplace, one for QuotaGuard Static and one for QuotaGuard Shield. The swap process works the same way. Email support@quotaguard.com, let us know you're migrating from Heroku to AWS Marketplace, and we'll handle the swap on our side. Your IPs and credentials stay the same.
Moving to one of these platforms? Each guide includes full setup instructions for QuotaGuard on the new platform.
Modern PaaS — closest to the Heroku experience
Containers and orchestration
Serverless
AI and automation workflows
Cloud providers
Email us at support@quotaguard.com and let us know you're planning to migrate off Heroku. We respond within 24 hours, usually much faster. Tell us how many apps you're moving and we'll take it from there.
If you have compliance requirements or are migrating a large number of apps and want to talk through the plan first, say so in your email and we'll set up a call.
Email support@quotaguard.com We respond same dayFor 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.