The short answer is it depends. By default QuotaGuard Static allows you to route outbound traffic from your app via a Static IP, for example to access a database behind a firewall.
If you want to route inbound traffic via a static IP to your application then you need to do a bit more configuration and it comes with some caveats.
#1 - Creating a DNS record to point to a Heroku application
If you are doing this to try and setup DNS rules for your Heroku app (for example pointing myapp.com to your Heroku app) you should do this via a CNAME, not via an A record on the IP address. Heroku have more details on their documentation pages. QuotaGuard Static is not required for this.
#2 - Clients of your website have strict internal firewall controls and can only access websites with a specific IP address
If you have clients that can only access specific sites on the internet and you need a static IP address that they can add to their firewall then you can use QuotaGuard Static. Simply follow the instructions here to get started: http://support.quotaguard.com/solution/articles/5000633969
Currently there are several key limitations with this service:
1. You cannot accept HTTPS traffic unless you provide us with your SSL key and certificate. You will also need to set up your own DNS A Record pointing to the Static IP address so that your SSL certificate is being used on a valid domain.
*This is no longer the case, QuotaGuard Shield now allows you to handle your SSL key and certificates yourselves without giving them to a third party. For more information about QuotaGuard Shield, email us at Support.
2. You cannot just enter in the Static IP address. Multiple accounts may be sharing the same IP address so without using a hostname in your URL we are unable to determine which account to route traffic to.