The logo is refreshed, but it’s still recognizably true to the elephant and N that we founded the company with. Did you know there has always been an elephant hiding in it? This update helps bring our visual identity into the Databricks universe. Since joining Databricks, we’ve g...

“We chose Neon as our backend because of scale, cost efficiency, and superior developer and user experience, all critical for Atoms’ multi tenant architecture. Each user app needs its own dedicated database, and Neon lets us spin up Postgres instances dynamically while only payin...

Neon is made by Postgres people. Since Neon became part of Databricks, we Postgres people also find ourselves part of a larger organisation of enterprise data people. This post is about what I’ve learned as a result. It aims to explain ‘data lakehouses’ and related enterprise dat...

You just opened a PR that adds a new user role to your app. Your staging database has the schema changes. Your preview deploy is live. But when QA tries to test it, they hit a wall the test users in your auth system still have the old roles. Someone needs to manually update them....

Looking back at 2025, AI changed coding for good. Early in the year, skepticism around AI assisted coding was still high and capabilities were limited. Now it’s clear that vibe coding has gone mainstream, and AI assisted coding is the future of software engineering. That said, we...

“Neon’s branching gave us the last missing piece in our RISE (Robust Isolated Staging Environment) true database isolation. The services that touched schema changes or write heavy paths could never share a database safely. Now every sandbox gets its own isolated Postgres DB whene...