Last week, we introduced app.build, our open-source reference implementation for building AI-powered applications on top of Neon. Unlike LLMs that generate isolated snippets, app.build uses agent architecture to turn prompts into fully deployed, production-ready applications — complete with frontend, backend, and a Neon Postgres database.
This week, in addition to installing app.build using npx, you can now install it using Homebrew.
📌 We also fixed an issue where newly built apps could flicker between the “Under Construction” page and the actual app. Apps now load consistently.
Neon MCP homepage & streamable HTTP support
Neon MCP Server now has a homepage — We’ve launched a new homepage for the Neon MCP Server at mcp.neon.tech, making it easier to understand what the MCP Server does and what tools it supports.
Streamable HTTP support — The Neon MCP Server now supports streamable HTTP as an alternative to Server-Sent Events (SSE) for streaming responses. This makes it easier to consume streamed data in environments where SSE is not ideal — such as CLI tools, backend services, or AI agents.
Fixes & improvements
Neon Console
We updated the Instant point-in-time restore time selector component on the Backup & Restore page. The new selector makes it a little easier to select the restore point time and date.
Fixed an issue in the console that prevented shared projects from being displayed.
app.build
We're very happy to join the codegen community with app.build, our open-source reference implementation for building codegen products on top of Neon. app.build is an agent that converts AI-generated code snippets into complete, deployed applications. While LLMs handle isolated coding problems well, app.build uses agent architecture to create production-ready apps.
Why we built this:
Beyond code snippets - Transforms prompts into complete, deployed applications with frontend, backend, and database
Community-driven development - Open source for developers to bring their own models and run locally
True agent architecture - Iterates on code, runs tests, and responds to feedback until everything works
Instant deployment - Ships working apps with real infrastructure
Getting started:
npx @app.build/cli
With this single command, you can create and deploy a complete application with its own GitHub repository.
How it works:
The agent decomposes app creation into validated tasks, running checks at each step to ensure everything works. This divide-and-conquer approach enables reliable generation of complex applications beyond simple code snippets.
Join us:GitHub - Built in the open for developers exploring AI-powered development.
Neon Launchpad
Introducing Neon Launchpad at neon.new, which enables instant Postgres database provisioning without any configuration or account creation. This feature allows you to get a fully functional database in seconds and demonstrates Neon's claimable database capabilities in action. You can build similar experiences to Neon Launchpad in your own application using the APIs documented in the integration guide.
Key features include:
Zero-configuration setup - No account required to get started
Multiple access methods - Browser interface, CLI tools, and development integrations
Claimable databases - Keep your database by claiming it with a Neon account within 72 hours
Getting started
Get started immediately by visiting neon.new in your browser, running npx neondb from the command line, or integrating automatic database provisioning into Vite projects with @neondatabase/vite-plugin-postgres.
Netlify DB: One-click Postgres powered by Neon
We're excited to announce that Neon is now powering Netlify DB, a new service that lets you provision production-ready Postgres databases directly from your Netlify project. Built on top of Neon Launchpad, Netlify DB makes it possible to spin up a fully configured Neon database with just one click in the Netlify Dashboard or a single CLI command (netlify init db).
Netlify DB is designed to be the perfect database for AI-native development, offering:
Instant provisioning with no external signup required
Automatic environment variable configuration
Zero-config setup with your deployed functions
The ability to claim your database and link it to your Neon account when you're ready
This integration is part of Netlify's Agent Week initiative, making it easier for both developers and AI agents to build applications with a production-ready database. Learn more in the Netlify DB documentation.
Add domains to Neon Auth
You can now whitelist redirect URIs for your deployed app directly in Neon Auth, without needing to create a Stack Auth account or transfer your project. This makes it easier to manage your app's authentication settings and simplifies your workflow.
Fixes & improvements
Neon Console
We updated the warning message to clarify that changing compute size settings will definitely interrupt database connections, rather than just possibly doing so. We want to make that clear so you know exactly what to expect.
Every new user now starts with their own free organization, simplifying our object hierarchy and improving development velocity.
Neon serverless driver
The Neon serverless driver was updated to version 1.0.1. This release includes package updates and addresses a few other issues:
The package now prints a security warning to the console when a connection is made in a web browser. This behavior can be suppressed with a new configuration option: disableWarningInBrowsers.
escapeIdentifier is now re-exported from pg, resolving #154.
Fixes a module resolution issue in the Deno/JSR version of the driver by correcting the @types/pg version reference, resolving #112.
Neon API
We've added new API endpoints to help you manage your Neon Auth domains: list domains, add a domain, and delete a domain. These endpoints make it easy to manage your redirect URIs programmatically.
Neon CLI
Version 2.10.0: prompts for organization selection if needed, with an option to save as default.
Fixes
Fixed an issue with IPv6 validation, ensuring that compressed IPv6 formats are properly validated. This improves stability and correctness for users relying on IPv6 functionality.
Enable Neon Auth in Vercel
You can now enable Neon Auth directly from the Neon Postgres Integration on Vercel. Enable it when creating a database, or later by going to the Storage tab in Vercel, selecting your database, and updating the Settings.
Neon Auth makes it easy to add authentication to your app. User data is stored in your Neon Postgres database, so you can query it like any other table — and join it with your app data.
Learn more in the Neon Auth guide.
Backup & Restore enhancements
The Backup & Restore page (available in Early Access) includes two updates:
The Instant point-in-time restore selector now defaults to the current time, making it easier to restore to the present or a recent point in time.
You can now edit the snapshot name — an improvement based on feedback from our Early Access users.
New guides
We've published new guides to help you get the most out of your Postgres database:
The list_projects and create_project MCP tools now return Neon organization details.
Neon API
Updated the Create branch API description to make it clear that the API creates a branch without a compute endpoint by default. To create a branch with a compute endpoint, the endpoint object must be added to the request body.
Expanded the General Error description in our API specification to clarify when it’s safe to retry a failed request based on the HTTP method and response.
Neon Postgres Integration on Vercel
When you connect a Vercel project to a Neon database, the integration now sets a NEON_PROJECT_ID environment variable in Vercel. This variable will support a new SaaS starter kit, which we'll introduce soon!
Usage notification emails
We've updated usage notification emails to include the account or org name they apply to. Helpful if you're part of more than one org — you'll know exactly where the alert is coming from.
Fixes
Fixed an issue that prevented creating more than one read replica on the Free plan, which supports up to three read replicas.
Fixed an issue with a pgrag extension function. A query using the rag_bge_small_en_v15.embedding_for_passage function failed to complete.
Fixed an issue where reaching the max_client_conn limit in PgBouncer could cause the connection info cache to be invalidated. This led to repeated attempts to wake the compute.
Removed a redundant Close button from the Connect to your database modal.
