Neon

QuotaGuard routes your application's Neon Postgres traffic through the two fixed IPv4 addresses assigned to its subscription. Add both addresses under Neon IP Allow and preserve the exact Neon endpoint hostname so the database proxy can route the connection correctly. QuotaGuard has provided static-IP proxy service since 2013.

• Two-Minute Setup: Configure the application path using the existing QuotaGuard Neon technical guide, add both dashboard IPs under Project Dashboard, Settings, Network security, IP Allow, and verify the proxied connection before tightening access.
• Neon Scale Support: Neon currently provides IP Allow on the Scale plan. Rules cover every branch by default, with an option to restrict them to protected branches only.
• Endpoint-Aware Routing: The transparent tunnel preserves the original Neon hostname and TLS identity, including the endpoint identifier Neon uses to select the correct compute.
• Pooled and Direct Connections: Use the same stable pair for pooled endpoints serving serverless and web workloads or direct endpoints serving migrations, exports, replication, and session-level tasks.
• Production-Grade Reliability: Each subscription receives two load-balanced static IPs with health checks and automated failover. Add both to Neon so either approved route can reach the project.
• Shield for Regulated Database Data: QuotaGuard Shield encrypts the customer-to-proxy hop while preserving the PostgreSQL TLS session to Neon without decrypting its payload. Use it when QuotaGuard's regulated-data position or an internal control requires that additional protected hop; it does not make the workload compliant by itself.

Neon feature note: Neon's current documentation says the Data API cannot be enabled on a project that uses IP Allow or Private Networking. This integration covers PostgreSQL connections to Neon endpoints.