Strategic Flow — Neon Changelog 64 Teardown

Source: neon.com/docs/changelog

Type: Product Changelog / Developer Update

Date: 5 June 2026

Changelog 64 — June 5

Docs · Changelog

Changelog

Changelog 64 — June 5

2026-06-05

Backend for apps and agents: coming soon

As announced last week, three new services are coming to Neon.

Storage: S3-compatible object storage that branches with your database. Every branch gets its own isolated storage state, so files and data stay in sync across dev, staging, and production.

Compute: Serverless functions that run alongside your Postgres database. Deploy code, trigger jobs asynchronously, and manage everything through the same CLI and API you already use.

AI Gateway: Route, log, and rate-limit LLM calls to OpenAI, Anthropic, or Gemini through a single proxy built into your Neon project. Streaming responses and per-request logging included. No extra infrastructure required.

Postgres 18 for newly created Neon projects

Postgres 18 is now the default for newly created Neon projects. Neon continues to support Postgres 14, 15, 16, and 17.

5x more network transfer on all paid plans

We've increased the public network transfer (egress) allowance on all paid plans from 100 GB to 500 GB per month. The new allowance takes effect automatically with no changes required on your end.

Faster Text-to-SQL in the SQL Editor

Text-to-SQL suggestions in the Neon SQL Editor are now significantly faster. You'll notice quicker responses when asking the AI to generate queries from natural language.

Link, branch, and query from the Neon CLI

Neon CLI v2.22.2 is a major CLI update that brings Vercel-style project linking, branch checkout, a top-level psql command, and full Data API management to the terminal.

neon link neon checkout <branch> neon psql production -- -c "SELECT version()"

Manually pay an invoice

Organization admins and personal account owners can now pay an outstanding invoice immediately from the Neon Console, without waiting for the automatic charge on the first of the month.

Expanded infrastructure capacity in AWS Europe (Frankfurt)

We've expanded infrastructure capacity in the AWS Europe (Frankfurt) region with new NAT gateway IP addresses and new VPC endpoint service addresses for Private Networking.

⚠ Title is a filing label — "Changelog 64 — June 5" is an internal version number. A developer scanning their inbox or feed has no reason to open this. The consequence of 5x more egress or AI Gateway shipping is never named in the subject.

⚠ Feature-First Bias throughout — every section leads with what the feature is, not what it changes for the developer. "AI Gateway: Route, log, and rate-limit LLM calls" describes the mechanism. The reader's actual gain (single proxy, no extra infra, per-request logging) is buried in the body.

⚠ No hierarchy between updates — Postgres 18 as default, 5x egress, AI Gateway, and CLI v2.22.2 are presented as equal-weight items. The most significant news (AI Gateway, full backend stack) competes visually with billing admin and infrastructure IPs.

⚠ Consequence buried in the 5x egress update — "The new allowance takes effect automatically with no changes required on your end" is the most actionable sentence in the whole update. It arrives as a subordinate clause after the spec number.

⚠ CLI update opens with version number — "Neon CLI v2.22.2 is a major CLI update" starts with internal versioning. The reader question is: what can I do now that I couldn't before? That answer is delayed by two sentences.

⚠ No CTA connected to the biggest news — the AI Gateway and backend stack announcement has no path to sign up for early access in the changelog body. The link exists in the docs but not surfaced as a visible action.

Changelog · June 2026

Changelog 64 · June 5, 2026

Your Neon project just became
a complete backend.

AI Gateway, Object Storage, and Serverless Compute are joining Postgres, Auth, and Data API on the Neon platform. Plus: 5x more egress on every paid plan, Postgres 18 as the new default, and a CLI update that finally lets you work the way you actually think.

more network transfer on all paid plans — automatic, no action needed

new services joining the platform: Storage, Compute, AI Gateway

PG18

now the default for every new Neon project created

The biggest news

One project. One CLI. One bill. No extra infrastructure.

Three new services are coming to Neon — and they all branch with your database the same way Postgres does. Storage keeps files and data in sync across every branch. Compute runs serverless functions alongside your database through the same CLI you already use. AI Gateway routes, logs, and rate-limits LLM calls to OpenAI, Anthropic, or Gemini through a single proxy built into your project. Streaming and per-request logging included. No extra infrastructure.

Effective immediately — paid plans

500 GB egress. Was 100 GB. No changes needed on your end.

The public network transfer allowance on all paid plans increased from 100 GB to 500 GB per month. It takes effect automatically and will appear on your June invoice. If you were watching egress limits, stop watching.

New default

Postgres 18 ships on every new project.

New Neon projects now default to Postgres 18. Existing projects on 14, 15, 16, or 17 are unaffected — and you can still select those versions when creating a new project if your stack requires it.

CLI v2.22.2

Link once. Branch anywhere. Query without flags.

The CLI now works the way your project actually works. neon link binds a directory to your project. neon checkout pins a branch so you stop typing --branch on every command. neon psql is now a top-level command. Run any of these from a subdirectory — the CLI walks up to find the .neon file automatically.

neon link neon checkout staging neon psql -- -c "SELECT version()"

SQL Editor

Text-to-SQL is now faster. Noticeably.

AI query suggestions in the SQL Editor respond significantly faster. Same feature, less waiting. If you haven't tried it yet: describe what you want in plain language, get a query back in seconds.

❌ Before

Title: Changelog 64 — June 5

Internal version number as headline. No developer reading their feed knows whether to open this. The most significant news in the update — AI Gateway, 5x egress, Postgres 18 default — is invisible until after the click.

✅ After

Title: Your Neon project just became a complete backend.

Reader's situation as headline. The developer who uses Neon understands immediately this is about what their project can do now — not what version number shipped.

The 6 upgrades — and why they work

1 · Title rebuilt from version number to reader consequence

The original is an internal reference: "Changelog 64 — June 5." The rebuild names what changed for the developer: "Your Neon project just became a complete backend." Any Neon user who has been managing separate infra for storage, compute, or AI routing understands immediately this changelog is about them.

2 · Hierarchy created between major and minor updates

The original presents AI Gateway, 5x egress, manual invoice payment, and Frankfurt NAT gateway IPs as equal-weight items. The rebuild surfaces the three things that change what a developer can build (AI Gateway, Storage, Compute) as the lead section, with egress and CLI following in consequence order. Infrastructure IPs do not appear in the changelog body — they belong in documentation, not in the reader's attention window.

3 · Egress update consequence moved to the lead

The original's most actionable sentence — "takes effect automatically with no changes required on your end" — arrives after the spec number and the billing note. The rebuild opens the egress section with it: "500 GB egress. Was 100 GB. No changes needed on your end." The developer who was watching egress limits gets the relevant signal in the first line, not the third.

4 · CLI update rebuilt around capability, not version number

The original opens: "Neon CLI v2.22.2 is a major CLI update." The rebuild opens: "Link once. Branch anywhere. Query without flags." Both describe the same update. One describes the product's internal versioning. The other describes what the developer can stop doing: typing --branch on every command, re-entering project context when moving between directories, remembering to add .neon to .gitignore manually.

5 · AI Gateway positioned as architecture shift, not feature addition

The original lists AI Gateway as one of three bullet points under "Backend for apps and agents: coming soon." The rebuild names the consequence: one project, one CLI, one bill, no extra infrastructure. The developer question — do I need to manage a separate proxy for my LLM calls? — is answered in the section title before the body explains how.

6 · Early access CTA surfaced above the fold

The original links to early access inside a doc page that most developers reading a changelog email will never reach. The rebuild makes "Sign up for early access" the primary CTA immediately below the stat cards — adjacent to the news that creates the motivation to click it.

This is the Strategic Flow method

Version number replaced with reader consequence. Hierarchy imposed on flat feature lists. Egress gain named before the spec. CLI update opened with capability, not version. CTA placed where the motivation to click exists. Score: 3/10 → 9/10. Visit strategicflow.tech to audit your last changelog.