Onboarding begins now: Compute, Storage, AI Gateway. Access at https://neon.com/backend - Compute: Long-running functions - Storage: object storage that branches with your database - AI Gateway: One API for all frontier and open-source models
Neon Postgres
Software Development
San Francisco, CA 18,285 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
External link for Neon Postgres
- 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
-
Primary
Get directions
San Francisco, CA, US
Employees at Neon Postgres
Updates
-
Starting TODAY every Neon paid plan includes 500 GB of monthly data transfer. That's 5× more than before! 📈 With this change, we expect most Neon customers will never have to pay for egress overages. Best of all, it applies automatically to all existing paid plans. Why we're doing this? Few things are more frustrating than an unexpected egress charge landing on your invoice. Raising the included amount to 500 GB removes that surprise for most Neon customers. Read more about it here: https://lnkd.in/dKSHabpy
-
TECH WEEK by a16z is almost here! We are teaming up with our friends at Sentry and Harness to bring the developer community together in an immersive art and tech experience. We're bringing the developer community together to build real connections and share our love for tech. We can't wait to see you there! Register here: https://lnkd.in/emikmHXG
-
-
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.
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
-
-
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.
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
-
-
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
-
-
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)
-
