Inbound & Outbound Static IPs for Gigalixir Applications
The native networking layer for Gigalixir that allows you to connect web services, background workers, and cron jobs to firewalled databases and secure APIs.
Shield your web services from inbound attacks and route outbound traffic through a dedicated, verifiable identity.
Enterprise Connectivity for PaaS
Gigalixir supports Elixir, Node, Python, Ruby, Go, and more, but its dynamic IP pools make it impossible to connect to strict corporate firewalls.
QuotaGuard acts as your application's permanent network identity, giving you a fixed entry point for secure database access and partner integrations. Built for stable infrastructure connectivity, not web scraping.
Fun fact: QuotaGuard and Gigalixir are operated by the same engineering team. We built QuotaGuard to solve the exact problems our Gigalixir customers kept asking about.
Production-Ready Reliability
Your app might be on Gigalixir, but your network needs are enterprise-grade.
Manage risk and reputation with dedicated infrastructure and region-locked sovereignty to ensure your services are compliant with local data residency laws anywhere in the world.
Dedicated Proxy Instances
Eliminate "noisy neighbor" risks for mission-critical services by moving to a dedicated instance.
This ensures your Gigalixir throughput is never impacted by other tenants and allows you to maintain a pristine IP reputation for sensitive API and database integrations.
Strict Data Residency (GDPR)
Ensure compliance with local data privacy laws by locking your Gigalixir traffic to specific regions.
Select EU-Only or US-Only infrastructure to guarantee that your traffic and metadata never cross sovereign borders, satisfying GDPR requirements.
"No Hard Stops" Reliability
We prioritize uptime over billing enforcement to protect your production logic.
Unlike providers that cut access when limits are reached, we continue processing your requests to keep your environment live while we contact you about plan adjustments.
Security & Compliance Without Compromise
Ensure true End-to-End Encryption (E2EE) with SSL Passthrough to protect your most sensitive application data.
We route your traffic without ever holding the decryption keys, making it the only technical path for Gigalixir apps in regulated industries to satisfy security audits.
FAQs
Technical Configuration and Setup for Gigalixir Apps
No.
Gigalixir offers Dedicated Ingress for inbound static IPs (useful for apex domains and webhook receivers), but there is no native solution for outbound static egress IPs.
This is why Gigalixir's official documentation recommends QuotaGuard for static egress.
The Dedicated Ingress feature requires a STANDARD tier app and is configured through Gigalixir support.
Use the Gigalixir CLI: gigalixir config:set QUOTAGUARDSTATIC_URL="your-proxy-url".
Alternatively, add it through the Gigalixir Console under your app's Configuration tab.
The variable is encrypted at rest and injected into your container at runtime.
Changes take effect on the next deploy or restart.
Yes.
QuotaGuard works with both FREE and STANDARD tier Gigalixir apps.
The proxy configuration is just an environment variable and HTTP client setting.
There are no platform-level restrictions.
However, note that FREE tier apps sleep after 30 minutes of inactivity, which will close proxy connections until the app wakes.
Yes. For database connections, use our SOCKS5 proxy with QGTunnel.
Download QGTunnel into your release, configure the tunnel in the QuotaGuard dashboard specifying your database host and port, then prefix your start command with bin/qgtunnel.
Your Ecto, Mongo, or other database driver connects normally while QGTunnel transparently routes traffic through the static IP.
Your proxy configuration is stored as an environment variable, so every new container Gigalixir spins up during a deploy immediately has access.
For Elixir hot upgrades, existing connections through the proxy remain stable.
For blue-green deploys, both old and new containers route through the same QuotaGuard IPs, so your allowlisted services see no change.
For releases, add the QGTunnel binary to your rel/overlays directory so it's included in the release tarball.
Update your Procfile to web: bin/qgtunnel bin/my_app start.
QGTunnel reads the QUOTAGUARDSTATIC_URL environment variable automatically.
For mix-based deploys (non-releases), place QGTunnel in your project root and adjust your Procfile accordingly.
Yes. QuotaGuard only proxies outbound traffic to external services.
Gigalixir's internal clustering (libcluster, distributed Erlang, Phoenix PubSub) happens over the internal network and is completely unaffected.
Your nodes communicate directly with each other while external API calls and database connections route through the static IP.
Still have questions?
We don’t outsource Support to non-Engineers.
Reach out directly to the Engineers who built Shield to discuss your specific architecture, integration challenges, or compliance constraints here 👇
🚀 Ready to Get Started? Choose Your QuotaGuard Path
QuotaGuard STATIC
QuotaGuard SHIELD
Trusted by Engineering Teams Everywhere
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.