Neon backend in Europe, new AI Gateway models, Neon in Grok Bot, and CLI updates

Neon backend in Europe, plus new AI Gateway models

The Neon backend is now available in AWS Europe (Frankfurt) (aws-eu-central-1), alongside AWS US East (Ohio) (aws-us-east-2). If you build in Europe, you can now run these services closer to your users and data.

The AI Gateway catalog also gains new models, callable through the same API and key as the rest of the catalog:

Fable 5.1
GLM 5.3 Flash
Grok 4.6
OpenAI GPT-6 Astra (landing soon)

Try the Neon backend, free during the beta

Object Storage, Functions, and AI Gateway are in beta in AWS US East (Ohio) and AWS Europe (Frankfurt), and branch with your Postgres database, so your whole stack forks together.

Get started

Neon is now available in Grok Bot

Neon is now available as a plugin in Grok Bot. Connect your Neon account once, then ask a Grok bot to work with your database:

Create a project and get a connection string for your app
Spin up an isolated branch before testing a migration
List projects and spot databases you no longer need
Run SQL against your database
Set up routines that summarize database usage

The plugin pairs Neon agent skills with the Neon MCP server, so Grok Bot has both the context and the authenticated tools to act on your account.

To install, open the Neon plugin in Grok Bot and authorize Neon in the browser. You can also open Grok Bot's Plugins directory and search for Neon, or ask Grok to connect the Neon plugin. Read more in the blog post.

Neon CLI updates

Two updates to the Neon CLI for setting up and connecting your projects:

A leaner neon init: it now does one focused job based on where you run it: in an empty directory it scaffolds a template and installs agent tooling (like neon bootstrap); in an existing app it installs a plugin (or skills and MCP), links your project, and writes a neon.ts config. Run it with npx, and pass -y and --agent for unattended runs:
Bash
```
npx neon@latest init
```
neon env pull writes Neon Function invocation URLs: each function's public URL is written to your local .env as NEON_FUNCTION_<SLUG>_BASE_URL, so your local app or frontend can call your deployed functions. See Environment variables.
Bash
```
neon env pull
```