How to Configure Neon Proxy

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up a neon proxy by turning on connection pooling in your project settings. Then you point your app or client tool to the pooled endpoint address. Most teams start by sharing one main database role across several apps and developers. When permissions are too broad, any user with that string can read or drop tables. How a native neon proxy works in practice Neon builds a connection pooler into every serverless Postgres project by default. This built-in neon proxy sits in front of your c

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

You set up a neon proxy by turning on connection pooling in your project settings. Then you point your app or client tool to the pooled endpoint address. Most teams start by sharing one main database role across several apps and developers. When permissions are too broad, any user with that string can read or drop tables.

How a native neon proxy works in practice

Neon builds a connection pooler into every serverless Postgres project by default. This built-in neon proxy sits in front of your compute node and manages traffic. Serverless apps often open hundreds of short database connections at the same time. Standard Postgres struggles when too many clients try to log in at once. The native pooler takes those incoming client requests and shares a smaller set of connections. Your team enables this feature by choosing the pooled connection string in the project dashboard. You can also create separate Postgres roles for each app or developer on your team. Each role gets specific read or write rules on schemas and tables inside the database. When a user logs in through the pooled endpoint, the database checks their role password. Then the compute node wakes up from idle mode and runs the SQL statements. This workflow keeps memory usage low and stops connection spikes from crashing your database.

Why you should separate app traffic from human queries

Web apps and engineers use a serverless database in very different ways. Your web app runs the same small queries thousands of times every single minute. It needs fast connection pooling so spikes in user traffic do not cause errors. Engineers and support staff log in to check data, fix bugs, or run migrations. They run manual queries that might scan whole tables or change production rows by mistake. If humans and apps share the same database role, your audit logs become messy. You cannot tell which team member ran a slow query or changed a customer record. Giving each engineer a personal database password takes a lot of time to manage. When someone leaves the team, you have to find and delete their old database accounts. Splitting automated app traffic from human logins is the first step toward safe database operations.

What native pooling solves and where gaps remain

The native pooler solves connection limits and helps serverless compute nodes scale up and down. Combined with standard Postgres roles, it decides who can log in to your database. Still, native pooling and static database roles leave an important operational gap open. Once a user logs in with a valid password, the pooler passes every query through. It does not check what individual SQL statements do while they run in flight. A developer with read access to a customer table can pull every row at once. Those query results often hold raw emails, phone numbers, card numbers, or national IDs. Native roles also cannot ask a team lead to approve a risky update statement first. Also, developers still keep static database passwords on their laptops in plain text files. If a laptop gets lost, someone could use that password to read production data.

Database Proxy (ProxySQL, PgBouncer) + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Run guardrails and masking on the Postgres connection

Role grants and firewall rules are needed setup. Setup alone cannot check single SQL statements or mask sensitive rows in a response. By design, hoop.dev sits inline in the Postgres protocol beside Postgres, RDS, or Aurora as a sidecar for your Postgres. On every production query from an engineer or AI agent, hoop.dev decides whether to pass, mask, block, or hold it for approval.

First, hoop.dev guardrails refuse disallowed drops or deletes before they run, and risky statements can pause for human review. Next, hoop.dev data masking rewrites sensitive fields in returned rows in memory. Furthermore, hoop.dev holds SOC 2 Type II and logs every statement and verdict per resource. Check out the project on GitHub.

Frequently asked questions

Does the built-in pooler hide sensitive data in query results?

No, the built-in pooler only manages connection counts and routes traffic to your database. To rewrite emails, phone numbers, or card numbers in results, you need runtime data masking.

How do we stop engineers from sharing the main database owner password?

Create separate database roles with limited read or write rules for daily engineering work. Better yet, connect your identity provider so users log in without storing database passwords locally.

Can we log every SQL query a developer runs on production?

Native poolers focus on routing traffic rather than keeping detailed user query logs by identity. You need a dedicated access tool to tie every single SQL statement to a person.

The query runs. The emails stay hidden.