
SQL editor for teams
Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.
If you only have a few minutes to spare, hereβs what investors, operators, and founders should know about PopSQL (S19).
PopSQL treated SQL as shared team knowledge rather than disposable text in a personal editor. Founded in 2017 by former Instacart engineer Rahil Sondhi, the Summer 2019 YC company combined multi-database editing, version history, live collaboration, charts, query organization, and shared results.[1]
Timescale acquired PopSQL in April 2024 because the editor could become an interaction layer for its database cloud.[2] This was strategic absorption, not a pre-sale collapse. The standalone outcome arrived later: TigerData ended active development in September 2025, placed PopSQL on limited support through September 1, 2026, and announced retirement after that date.[3] PopSQL's collaboration thesis survived, but its owner valued selected features more inside Tiger Cloud than as a neutral cross-database product.
Sondhi started PopSQL as a side project while working at Instacart. SQL lived in local files, results moved through Slack, and charts landed in Google Sheets. Context disappeared as work crossed tools.[4]
He described himself as βfrustrated with the disjointed experience.β His goal was collaboration that felt βeasy and natural for engineers to work together.β[2] The insight was that a query was not merely code. Its value depended on who wrote it, why it existed, which schema it expected, what changed, and whether teammates trusted it.
An initial Product Hunt launch attracted teams at DoorDash, Redfin, and Shipt before PopSQL entered YC.[4] That adoption turned the side project into a company. The early users validated a horizontal need across databases: teams wanted a shared memory inside the place they queried data.
PopSQL raised a $3.4 million seed round in September 2020 led by Gradient Ventures.[4] The product then expanded from a collaborative editor into a broader data workspace.
PopSQL combined SQL editing across PostgreSQL, Timescale, Redshift, Snowflake, BigQuery, MySQL, and SQL Server with version history and team organization.[2] Users could store queries centrally, search them, collaborate live, share results, and turn outputs into charts.
By 2022, the product included a data catalog, SQL notebooks, dbt integration, and enterprise controls. VPC deployment, granular permissions, SSO, audit logs, and approval workflows addressed the security obligations created when a cloud collaboration tool touches databases.[5]
The distinguishing bet was team query memory. Desktop database clients optimized individual work. Warehouse consoles tied users to one vendor. BI tools emphasized dashboards. PopSQL centered the query and its collaborative history across sources.[6]
That neutrality also created complexity. PopSQL had to support many dialects, credentials, network configurations, permission models, and result behaviors. Enterprise features were not optional decoration; they were required to make collaborative query execution acceptable inside larger companies.
PopSQL targeted data analysts, analytics engineers, software engineers, and data teams using several databases. Named users included Vroom, Redfin, Shipt, Udacity, Ramp, DoorDash, and Optimizely.[1]
No audited ARR, pricing history, paid conversion, renewal, or margin data was observed. At the 2022 Series A, PopSQL reported revenue growing fivefold since its seed round, a team that had more than doubled, and usage by more than 2,000 companies.[5] These are company-reported figures.
Read the complete post-mortem, the rebuild playbook, and the exact reasons PopSQL is still worth studying now.