Dev.to (3M+ users) runs on Neon. They left Heroku in search of a better developer experience and lower costs

Changelog

The latest product updates from Neon

RSS feed

[Feature A title]

[Description of Feature A]

[Feature B title]

[Description of Feature B]

Fixes & improvements
  • Neon Console

    • [Improvement 1]
    • [Improvement 2]
  • Neon API

    [API improvements]

  • Neon CLI

    [CLI improvements]

  • Neon Launchpad

    Introduced database seeding functionality in Neon Launchpad, allowing developers to automatically populate databases with SQL scripts during initialization. This feature streamlines the development workflow by enabling instant database setup with sample data. The seeding capability is also available through the Vite plugin integration, making it accessible in TanStack Router applications and other Vite-based projects (PR pending).

    For more details, see:

  • Drizzle Studio update

    • Drizzle Studio, which powers the Tables page in the Neon Console, has been updated to a new version. For details about the latest updates, see the Neon Drizzle Studio Changelog.

OpenTelemetry integration

Neon now supports OpenTelemetry! You can send metrics and Postgres logs from Neon to any OpenTelemetry-compatible backend. You can enable the integration from the Integrations page in the Neon Console. For setup instructions, refer to our OpenTelemetry docs, with example configuration for New Relic.

OpenTelemetry integration card

Data API now available in beta for all Neon users

The Neon Data API is now in open beta for all users. Instantly turn your Neon Postgres database into a REST API. No backend required. Query tables, views, and functions right from your client app using standard HTTP verbs (GET, POST, PATCH, DELETE), powered by PostgREST.

Data API enabled view

We've improved our onboarding to make it easier to get Neon Auth and RLS set up as needed to safely use the Data API in your app.

data api configuration card

Learn more in our getting started guide. Or try this tutorial walkthrough of our demo note-taking app.

Check out the live demo to see it in action.

show demo view of notes app

API key-based authentication for the Neon MCP Server

The Neon MCP Server now supports API key-based authentication for remote access, in addition to OAuth. This allows for simpler authentication using your Neon API key (personal or organization) for programmatic access.

{
  "mcpServers": {
    "Neon": {
      "url": "https://mcp.neon.tech/mcp",
      "headers": {
        "Authorization": "Bearer <$NEON_API_KEY>"
      }
    }
  }
}

For Neon MCP Server setup instructions, see our guide.

Fixes & improvements
  • Neon Datadog integration

  • Neon Console

    • To improve ease-of-use, we've added a time selection option to date-time selectors in the Neon Console.
  • Drizzle Studio update

    • Drizzle Studio, which powers the Tables page in the Neon Console, has been updated to version 1.0.22. For details about the latest updates, see the Neon Drizzle Studio Changelog.

app.build — now available via Homebrew

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.

brew app.build install

📌 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. To use streamable HTTP, make sure to use the latest remote MCP server, and specify the https://mcp.neon.tech/mcp endpoint.

    {
      "mcpServers": {
        "sentry": {
          "command": "npx",
          "args": ["-y", "mcp-remote@latest", "https://mcp.neon.tech/mcp"]
        }
      }
    }
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.
Was this page helpful?

Subscribe to our changelog.
No spam, guaranteed.