서버리스 포스트그레스 speaks PostgreSQL
Connect 네온 to Excel, Sheets and AI
Neon serverless Postgres, direct or through the pooled endpoint. Paste the string Neon gave you.
One connection, every surface
Where your Neon data can go
Connect Neon once and the same read-only connection feeds all of these — no second setup, no second copy of the data. 9 of 11 have a step-by-step guide.
Neon to Excel
Microsoft Excel · Excel add-in
Pull live Neon results straight into a worksheet and refresh them on demand — desktop Excel, Excel Online, Microsoft 365.
Read the PostgreSQL guide
Neon to Google Sheets
Sheets add-on
Run a saved Neon query from the sidebar and drop the rows into the sheet. Shared collaborators can refresh it themselves.
Read the PostgreSQL guide
Neon MCP server
Claude, Cursor and MCP clients
Give an AI assistant read-only access to Neon with the schema it needs to write correct SQL — no credentials in the chat.
Read the PostgreSQL guide
Neon REST API
HTTP endpoint
Publish a Neon query as an authenticated JSON endpoint any application can call, with an OpenAPI 3.1 spec and ready-made Postman, Insomnia and Hoppscotch collections. No database port is opened.
Read the PostgreSQL guide
Neon to Airtable
Automation platform
Sync Neon rows into an Airtable base on a schedule, or fetch them inside an Airtable automation script.
Read the PostgreSQL guide
Neon to Baserow
Automation platform
Feed a Baserow table from Neon over the REST endpoint — self-hosted or Baserow cloud.
Read the PostgreSQL guide
Neon to SeaTable
Automation platform
Keep a SeaTable base current with Neon data without exporting a file or exposing the database.
Read the PostgreSQL guide
Neon to Smartsheet
Automation platform
Push Neon results into a Smartsheet grid so plans and reports read from the source system, not last week's export.
Read the PostgreSQL guide
Neon to Anvil
Anvil Works · App platform
Back an Anvil Python app with Neon through the REST endpoint instead of embedding database credentials in the app.
Read the PostgreSQL guide
Neon to Power BI
Power Query M
Paste the generated Power Query M into the Power BI Advanced Editor and the report reads live Neon results over HTTPS — no ODBC driver, no database port opened.
How Power BI works no Neon walkthrough written yet
Neon alerts and reports
Slack · Discord · Email · Webhook
Put a Neon query on a schedule and have the rows delivered to Slack, Discord, email or a signed webhook — or hold the message until a row count, threshold or percentage change crosses the line you set.
How alerts and reports work no Neon walkthrough written yet작동 방식
5 steps, no inbound firewall change
Install the Network Agent wherever suits you — a laptop, a VM, a container. Neon is a public endpoint, so the agent needs outbound HTTPS and nothing else: no inbound rule, no VPC peering, no IP allow-list.
Paste the URI from the Neon console. Host, port, database and role are read out of it, and the pooled and direct strings are both accepted.
Choose pooled or direct. Pooled is the default and the right answer for query traffic; direct is capped by the compute's max_connections.
Leave SSL on. The agent forces it for any .neon.tech host, so a string that lost its ?sslmode=require somewhere in the clipboard still connects encrypted.
Save. The schema is read through information_schema and pg_catalog, and from then on Excel, Sheets, an MCP client and the REST API all read that branch through the one connection.
Feature deep-dive
What Neon gives you
Shared by every database connector
True of every database connector
- 출국 전용 — the agent opens one encrypted connection out to Query Streams. No inbound port to forward, no VPN, no IP allowlist, nothing about your database exposed to the internet.
- Credentials stay put — the database username and password live on the machine you installed the agent on. Query Streams never receives them and cannot reach your database on its own.
- 읽기 전용, 강제 적용됨 — one statement at a time, SELECT and friends only. A write is rejected on your own machine before it is ever sent to the server, rather than relying on a permission somebody remembered to set.
- Deploy as many agents as you like — one per site, region or cloud. Every data source they can see arrives in a single dropdown, so nobody has to know which agent hosts what.
What you get once a query is saved
- Share the capability, not the SQL — a colleague or an outside partner can run your query and change its filters without ever seeing the statement behind it.
- Filters from either direction — declare them yourself as @variables, or let the connector spot the literal values already sitting in your WHERE clause and offer those as dropdowns.
- Read it from anywhere — Microsoft Excel, Google Sheets, Power BI, the REST API, AI assistants over MCP, the Query Builder and Nova all read the same saved query.
- Run several at once — five saved queries into five worksheet tabs, streamed concurrently, however large the results.
- Join it to anything else you have connected — another database, a business API, or a folder of files, in one read-only statement.
Cross-source SQL
Join Neon to the rest of your data
One statement can span Neon and your other connections at once. Each source runs only the part it can, streams the result back, and the join happens centrally — the sources never talk to each other and nothing is copied anywhere.
3 connections · 3 agents
One statement
-- nothing copied, nothing merged, nothing scheduled
선택 c.region, COUNT(*) AS orders, SUM(i.amount_due) AS invoiced
FROM neon.public.orders1 f
JOIN erp_sql.dbo.customers2 c ON c.id = f.customer_id
JOIN 청구.stripe.invoices3 i ON i.customer = c.stripe_id
그룹 기준 c.region
주문 기준 invoiced DESC;The three parts are connection, schema and table — and the connection name is whatever you called it. Illustrative columns; your tables will be your tables. Read-only applies to every piece: SELECT, WITH and EXPLAIN only, with a ceiling on how much any one source may hand over for a single query. 연합 쿼리의 작동 방식
Connection details
What Neon needs
- 포트
- 5432
- Driver
- Npgsql 9.0.3, carried by the agent — nothing to install at the Neon end
- TLS
- Required, and forced by the agent for every .neon.tech host
- 데이터베이스
- neondb, unless you renamed it
- 역할
- Any Neon role and its password from the console; a SELECT-only role is the right one
- Direct host
- ep-<name>-<id>.<region>.aws.neon.tech
- Pooled host
- ep-<name>-<id>-pooler.<region>.aws.neon.tech — same domain, same port
- Connect timeout
- 30 seconds, sized to cover a wake from scale-to-zero
Pooled or direct is the only real decision, and it is reversible. Neon's pooled endpoint is the same domain and port with -pooler added to the hostname, running PgBouncer in transaction mode for up to 10,000 client connections. The agent recognises that infix and adapts to it: it stops resetting the session on close and pins auto-prepare off, because Npgsql's auto-prepare uses named prepared statements and those do not survive the backend being reassigned between transactions. None of that is yours to configure — paste either string and the right behaviour follows.
A Neon compute suspends when it is idle, so the first query after a quiet spell pays a few seconds to wake it. The 30-second connect timeout is sized for that rather than for a fast failure, which is why a cold branch feels slow exactly once.
Grant the role SELECT and nothing more — Neon is ordinary Postgres, so GRANT SELECT ON ALL TABLES IN SCHEMA public plus ALTER DEFAULT PRIVILEGES covers tables added later. Independently of that grant, the agent refuses any statement that is not a read before it ever reaches Neon.
Every Neon branch has its own endpoint, so a branch is simply another connection. Point one data source at main and another at a dev branch and both sit in the same account, queryable side by side.
Vendor documentation: 네온닷컴
Same wire protocol
These connect the same way
They share every guide above; only the connection string differs.
FAQ
Questions about Neon
Which tools can read Neon data through Query Streams?
All of them, from one connection: Excel, Google Sheets, MCP, REST API, Airtable, Baserow, SeaTable, Smartsheet, Anvil, Power BI, scheduled alerts and reports. Connect the database once and every surface reads the same read-only connection — there is no per-tool setup and no second copy of the data.
Do I have to open a firewall port to my Neon database?
No. The Query Streams Network Agent runs inside your network and opens a single outbound encrypted connection. Nothing listens for inbound traffic, no VPN is required, and the database keeps its existing firewall rules.
Can Query Streams change data in Neon?
No. The agent enforces read-only at the point of execution — one statement at a time, SELECT and friends only. Credentials stay on the agent and are never sent to Query Streams.
What does Query Streams need to connect to Neon?
A reachable host, a role and its password — the agent carries the driver, so nothing is installed on the database. Port: 5432. Driver: Npgsql 9.0.3, carried by the agent — nothing to install at the Neon end. TLS: Required, and forced by the agent for every .neon.tech host. Database: neondb, unless you renamed it.
Can I join Neon to another database in the same query?
Yes — that is a federated query. One statement can reference Neon and your other connections at once, written as connection.schema.table. Each source runs only the part it can and streams the result back; the join happens centrally, so the sources never connect to each other and nothing is copied or scheduled. Read-only applies to every piece — SELECT, WITH and EXPLAIN only — and there is a ceiling on how much any one source may hand over for a single query. Federated queries are a plan feature; the federated queries page carries the current source and size limits.
Is connecting Neon different from connecting PostgreSQL?
Only the connection string. Neon speaks the PostgreSQL wire protocol, so filters, scheduling, sharing, the Excel and Google Sheets add-ons and the MCP server all behave identically. The Neon card pre-fills the host, port and SSL settings that provider expects.
Is there a Neon to Excel guide?
Yes — it is the PostgreSQL guide, and it is correct for Neon as written. Neon speaks the PostgreSQL wire protocol, so Neon to Excel, Neon to Google Sheets and every other destination follow the same steps. The only Neon-specific part is the connection string, and the Neon card fills that in for you.
Put Neon where the work happens
Install the agent, point it at your database, and pick a destination.
읽기 전용 출국 전용 Credentials stay on the agent
English 
Spanish 
German 
French 
Portuguese 
Japanese 
Korean 
Chinese 
Italian 
Dutch 
Indonesian 
Polish