Neon
Written by the Bee, read it before you send it
KPIMore first meetings turn into real deals, on less preparation time
selling on-prem storage
Databricks completed its roughly $1B acquisition of Neon in May 2025, and Neon now sits inside Databricks' Data Intelligence Platform under a new corporate governance umbrella — a moment when data handling and control boundaries typically get re-examined.
Governance layer with logging, audit trails, RBAC, SSO, and data residency controls medium
Likely involved in infrastructure/storage decisions given the meeting topic (on-prem storage)
Bhargav Petla
Contact at Neon (title not publicly confirmed) · Unknown — no public tenure data found
Public search did not surface a verifiable professional profile for a Bhargav Petla at Neon (the Postgres database company); most results matched a different, unrelated individual of the same name.
- Likely involved in infrastructure/storage decisions given the meeting topic (on-prem storage)
- Possible interest in data residency and compliance given Neon's HIPAA/SOC2 positioning
- Unable to confirm specific priorities without a verified profile
- No verified public posts or statements found under this name at Neon
Neon today
- Industry
- Cloud database / serverless PostgreSQL infrastructure
- Size
- Startup-scale team, now operating as a business unit within Databricks (post-acquisition)
- HQ
- Menlo Park (originally San Francisco), California, US
- Footprint
- US HQ (Menlo Park/San Francisco) · Distributed engineering team · Operates within Databricks' global cloud infrastructure
Neon is a serverless PostgreSQL database platform that separates storage from compute, enabling instant provisioning, autoscaling, scale-to-zero, and git-like database branching. Founded in 2021, it was acquired by Databricks in 2025 and now operates as "Lakebase Postgres" within the Databricks Data Intelligence Platform, targeting both human developers and AI agent workloads.
- Rebranded/integrated as "Lakebase Postgres" inside Databricks platform, powered by Databricks (2026)
- Databricks completed its ~$1B acquisition of Neon, announced May 14, 2025
- Neon cited that over 80% of databases provisioned on its platform are created by AI agents, not humans (per 2025 acquisition announcement)
- Neon lowered storage pricing from $1.75 to $0.35 per GB-month and cut compute costs 15-25% following the acquisition
- Storage backed by object storage with a caching layer can see higher latency once workloads exceed local page cache, a documented architectural tradeoff
- Competitive pressure from PlanetScale, Supabase (which acquired OrioleDB), and Prisma sharpening rival serverless/Postgres offerings
- Operating under Databricks ownership raises open questions about platform independence and future direction
- Committed to agentic-workload architecture: full compute/storage separation to keep TOC proportional to ephemeral, AI-agent-spun-up databases
- Integrating with Databricks' Unity Catalog and Data Intelligence Platform to unify data/AI governance with database provisioning
- Maintaining 100% Postgres compatibility and open extension support to keep its open-source developer ecosystem intact
Positioning
We give teams a governed, single-workspace layer for search, task automation, and data handling with logging, audit trails, RBAC, SSO, and data residency controls, plus a guarantee that customer data is never used to train models.
Conversation arc
“Bhargav, thanks for making time — I know this meeting was framed around on-prem storage, so I want to be upfront about where our platform actually intersects with what you're doing at Neon.”
“Since the Databricks acquisition closed, how has your team's approach to data governance and access controls changed, if at all?”
“What we bring is a governance layer — audit trails, RBAC, SSO, data residency — plus a hard guarantee that nothing you run through it trains external models.”
“I hear that this sits outside your storage architecture decisions — but the question is who in your org is accountable for AI tool sprawl and compliance risk as Neon integrates into Databricks.”
“If this isn't your call directly, Bhargav, can you point me to whoever owns data governance policy for Neon inside Databricks so we can have a focused 20-minute conversation?”
Ask these
- Q1Since the Databricks acquisition closed in May 2025, who owns decisions about data governance and access controls for Neon's systems?
- Q2With Neon integrating into Databricks' Unity Catalog, are you seeing new requirements around audit trails or data residency for tools your team uses?
- Q3Given the open questions around platform independence under Databricks ownership, how is your team thinking about vendor lock-in for internal tooling?
- Q4Are compliance credentials like SOC2/HIPAA, which Neon already lists publicly, something your team has to re-certify or extend as tools get added?
Feasibility
What they appear to run
- Neon's site names Vercel, Replit and Hasura as integration partners
- Databricks press release states Neon is 100% Postgres-compatible and works with popular extensions
- Neon.com lists PrivateLink-based private networking and SOC2/HIPAA compliance features