
SQL editor for teams
Explore the risks and possibilities with a prompt for ChatGPT, Claude, or your agent.
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.
PopSQL competed with desktop database GUIs, warehouse-native consoles, BI tools, collaborative notebooks, and internal query repositories. Its neutral multi-database workspace distinguished it from vendor consoles. Collaboration and catalog features separated it from personal desktop clients.
Database vendors held the strategic advantage of distribution. They could bundle query experiences with compute, credentials, billing, and support. Timescale's own engineers and analysts already used PopSQL, making acquisition a direct path to a browser and desktop interaction layer for Timescale customers.[2]
PopSQL used a team software model with enterprise controls and deployment options. Collaboration, query organization, and charts drove adoption; VPC deployment, permissions, SSO, audit logs, and approvals supported larger contracts.[5]
The company raised $3.4 million in 2020 and $14 million in 2022.[4][5] Acquisition terms were not disclosed.
No audited ARR, gross margin, customer-acquisition cost, renewal, or post-acquisition retention was found. The company-reported growth and user count demonstrate adoption, but cannot establish standalone economics.
Product Hunt brought early adoption from DoorDash, Redfin, and Shipt.[4] By February 2022, PopSQL said more than 2,000 companies used the product and revenue had grown fivefold since the seed.[5]
Timescale's internal use supplied another signal: the buyer already understood the product as a customer before acquiring it.[2] The later retirement does not erase pre-sale demand. It records the new owner's portfolio decision.
Timescale acquired PopSQL in April 2024 and hired Sondhi and the team.[2] The announced goal was to bring browser and desktop querying, dashboards, history, and collaboration to Timescale users. No observed evidence shows distress before the sale.
The standalone ending was confirmed seventeen months later. On September 2, 2025, TigerData ended active development, set limited support through September 1, 2026, and announced retirement. It said it was “integrating some of the best parts of PopSQL into the core Tiger Cloud experience.”[3]
The mechanism was product-surface absorption. PopSQL's neutral editor had horizontal value, but TigerData could use selected capabilities to improve its own database cloud. Integrated querying supports database adoption and retention even if the editor does not remain a separate business.
PopSQL reported fivefold revenue growth and more than 2,000 company users, and Timescale's team used it.[5][2] It might have remained independent or found a buyer committed to database neutrality.
Missing evidence prevents a verdict. Acquisition price, ARR, renewal, margins, and post-close retention were not disclosed. Retirement proves TigerData's current priority, not that standalone PopSQL was doomed.
The retirement notice lets users download individual queries as .sql files. It does not establish a complete portable export for team history, comments, catalogs, schedules, permissions, or dashboards.[3] That gap cuts against the product's original promise: query value lives in context, not text alone.
A durable collaboration tool needs an exit contract. Teams should be able to move queries, annotations, ownership, review state, and source references without preserving credentials or result rows.
.sql downloads do not preserve the collaborative knowledge that made PopSQL useful.