Neon Postgres’ cover photo
Neon Postgres

Neon Postgres

Software Development

San Francisco, CA 18,075 followers

Ship faster with Postgres for modern engineering teams

About us

Helping developers ship and scale faster with Postgre via decoupled storage and compute, autoscaling, branching, and instant restores.

Website
https://neon.com
Industry
Software Development
Company size
51-200 employees
Headquarters
San Francisco, CA
Type
Privately Held
Founded
2021
Specialties
Postgres, Cloud, Serverless, Open Source, Partnering, PostgreSQL, and Databases

Locations

Employees at Neon Postgres

Updates

  • Neon Postgres reposted this

    Congrats to the Netlify team on today's GA launch of Netlify Database! With Netlify Database, every agent run gets its own Postgres branch off the latest production data, migrations are version-controlled files that run on preview first, and production is unreachable until you explicitly publish. Production is only modified when you go live. Nothing skips the queue. We’re excited to see more of the industry adopt branching. It’s not just a safety feature, it’s a better mental model for how databases fit into development.

    View organization page for Netlify

    36,195 followers

    Netlify Database is now generally available. Years ago, atomic deployments and Deploy Previews made safe experimentation standard for every developer. The "is prod down?" panic became a once-in-a-while thing instead of a daily one. Today, we're extending that same spirit to the database layer. Netlify Database is fully managed Postgres, built into the platform. Every agent run automatically gets its own database branch, based on the latest production data. Schema changes, test records, half-baked experiments, all contained. Production stays untouched until you choose to publish. This works for whoever is building. A designer prompting an app into existence gets the same safety net as a team of engineers running migrations through Drizzle. Same workflow, same guarantees, no extra setup. Try it with a prompt like "I want an app to manage my list of mythical creatures." The agent will spin up the schema, wire up the UI, and give you a preview running on a real Postgres branch in a couple of minutes. We built this because a database that only has one environment will break. That's a given on a team, and it turns out to be pretty common solo, too. Try it: https://lnkd.in/gvprMXb Full launch post here: https://lnkd.in/dZnPqvWB

    • Netlify-branded graphic with a teal background featuring layered database icons and connected nodes. Large headline reads “Netlify Database” with subheading “Ship data-driven apps without breaking flow.”
  • Congrats to the Netlify team on today's GA launch of Netlify Database! With Netlify Database, every agent run gets its own Postgres branch off the latest production data, migrations are version-controlled files that run on preview first, and production is unreachable until you explicitly publish. Production is only modified when you go live. Nothing skips the queue. We’re excited to see more of the industry adopt branching. It’s not just a safety feature, it’s a better mental model for how databases fit into development.

    View organization page for Netlify

    36,195 followers

    Netlify Database is now generally available. Years ago, atomic deployments and Deploy Previews made safe experimentation standard for every developer. The "is prod down?" panic became a once-in-a-while thing instead of a daily one. Today, we're extending that same spirit to the database layer. Netlify Database is fully managed Postgres, built into the platform. Every agent run automatically gets its own database branch, based on the latest production data. Schema changes, test records, half-baked experiments, all contained. Production stays untouched until you choose to publish. This works for whoever is building. A designer prompting an app into existence gets the same safety net as a team of engineers running migrations through Drizzle. Same workflow, same guarantees, no extra setup. Try it with a prompt like "I want an app to manage my list of mythical creatures." The agent will spin up the schema, wire up the UI, and give you a preview running on a real Postgres branch in a couple of minutes. We built this because a database that only has one environment will break. That's a given on a team, and it turns out to be pretty common solo, too. Try it: https://lnkd.in/gvprMXb Full launch post here: https://lnkd.in/dZnPqvWB

    • Netlify-branded graphic with a teal background featuring layered database icons and connected nodes. Large headline reads “Netlify Database” with subheading “Ship data-driven apps without breaking flow.”
  • Today 66% of pageviews on Neon Docs are from LLMs. Here's the most important thing we learned as we evolved our docs to also serve agents: One canonical source for everything. Never put yourself at risk of content drift. If you manually create a second version of a page just for agents it's going to fall out of date. Philip O. shares much more technical details on our blog - link in comments

    • No alternative text description for this image
  • OpenAI just announced a major update to Codex, and we’re thrilled to share that the Neon plugin is officially available in the Codex marketplace! Query your database, create new projects, or spin up branches directly within the Codex chat interface. Setting it up is simple: head to the plugins menu, search for "Neon," and hit install. Check out our announcement post here: https://lnkd.in/eX5zYJhp

  • Now active for all Neon databases: 𝐂𝐨𝐦𝐩𝐮𝐭𝐞 𝐩𝐫𝐞𝐰𝐚𝐫𝐦𝐢𝐧𝐠 is the first of several features that make compute restarts invisible. Context: We auto-upgrade Postgres minor versions and ship security patches for millions of databases/month. For always-on databases, this requires a compute restart that has 1sec P99. But the compute cache still needs to warm up. Compute prewarming dramatically improves post-restart performance. This is also the first big feature to ship in tandem on Neon and Databricks Lakebase. Thanks to Hans Norheim and team for leading the effort and providing an incredible write-up. (see comments)

    • No alternative text description for this image
  • We talk a lot about "Serverless Postgres," but what does that actually mean for your daily workflow? By separating storage from compute, Neon gives you a database that actually behaves like modern software: 1. Autoscaling: It scales up when your traffic spikes and scales to zero when it doesn’t, so you don’t pay for idle compute. 2. Branching: Create full copies of your database in seconds. Use them for development, preview deployments, or safe AI sandboxes. 3. Point-in-Time Recovery: Treat your data like code. If something breaks, just roll back to the exact second before the error happened. All the Postgres you love, with none of the infrastructure headaches. Check out the breakdown in the video below!

  • Agents are great at writing code, but too much of the other work like configuration of local dev environment and provisioning infrastructure, is still on the developer. Specific (YC F25) solves this with an agent-first cloud. Agents get automatic local dev environments and a Terraform-style IaC layer that gives them the infrastructure context they need to develop, deploy, and maintain apps safely. Also the database layer runs on Neon!

    • No alternative text description for this image

Similar pages

Browse jobs

Funding