The PopSQL Shutdown: What It Means and What to Do

Last updated August 30, 2026 · By the SaturnSQL team

PopSQL was scheduled to shut down on September 1, 2026. That date has been called off. The collaborative SQL editor remains in limited support indefinitely, which means no new features and no fixes beyond critical security issues. There is no hard deadline any more, but there is also no long-term commitment: 90 days’ notice is all you are guaranteed. This page explains what changed, what it means for your team, and which alternatives are worth your time.

Ready to move now? Read the step-by-step PopSQL to SaturnSQL migration guide, or compare all the best PopSQL alternatives first.

What is happening to PopSQL?

PopSQL was acquired by Tiger Data (formerly Timescale) in 2024. In early 2026, the team announced PopSQL would move into a limited-support phase, citing the difficulty of scaling the standalone business, and set a retirement date of September 1, 2026. In August 2026 that date was postponed. PopSQL now stays online indefinitely, with no shutdown date announced and a commitment to at least 90 days’ notice if one is set.

Limited support has not changed. Active development has stopped, no new features or non-critical updates are planned, and only critical security issues and emergency fixes get attention. Existing organizations, queries, connections, API access, and integrations keep working, and billing is unchanged, though annual subscriptions convert to monthly at renewal.

Timeline: how we got here

• 2024PopSQL is acquired by Timescale, the company now called Tiger Data.
• Early 2026PopSQL moves to limited support: active development stops, and a retirement date of September 1, 2026 is announced. Customers are told every saved query, connection, and team setting will be permanently deleted on that day.
• August 2026Roughly three weeks before the deadline, Tiger Data postpones the shutdown indefinitely. Nothing is deleted, no new date is set, and the team commits to at least 90 days' notice before any future retirement.
• TodayPopSQL is online in limited support with no shutdown date. No new features are planned; only critical security issues get fixes. This page tracks any change to that status.

Where things stand

• Today: PopSQL runs in limited support with no shutdown date. You can log in, run queries, and use integrations as normal. Nothing is being deleted.
• If a shutdown is announced: Tiger Data has committed to at least 90 days’ notice, so you would have roughly three months to migrate a team.
• Ongoing: No new features, and no fixes beyond critical security. Whatever gaps PopSQL has today, it will still have.

Should you still migrate?

The panic is over, so do not rip out a working tool this week. But the direction has not changed: PopSQL is a product being wound down, and 90 days is a short window to move a team’s query library, connections, and schedules once the clock actually starts. The sensible middle ground is to stop treating PopSQL as a long-term bet, keep an export of your queries somewhere you control, and know which replacement you would pick.

The reversal cuts both ways, too. It is genuinely good news for anyone mid-migration, but it also means the roadmap for your SQL editor is now a series of announcements you find out about after the fact. This is a team that set a firm date for deleting customer data, held it long enough for teams to plan around, and then moved it. The next notice could just as easily go the other way, and by their own commitment you would have 90 days to act on it.

At minimum, work through this checklist once while the product is comfortably online:

1. Export every query you want to keep. The fastest way is PopSQL’s free GitHub Sync, which pushes your whole shared library to a GitHub repo as .sql files in one step. For personal queries it skips, open each one, use the three-dot menu, and choose Download as .sql. Either way, keep them in folders that mirror your PopSQL structure.
2. Note your database connections. Connection credentials do not export, so record the host, port, database name, and username for each connection (you will re-enter these in your new tool).
3. Write down your schedules. List any scheduled queries or dashboards and where their results were going, so you can recreate them.
4. Pick a replacement and import. Choose an alternative and move your queries in. See the options below.

Your options after PopSQL

The right replacement depends on how your team used PopSQL. The full breakdown is in our PopSQL alternatives comparison, but in short:

• SaturnSQL — the closest like-for-like replacement: a browser-based collaborative SQL editor with a shared query library, scheduled queries, schema-aware autocomplete, AI SQL assistance, and Google Sheets export. Free tier, paid plans from €19/month per user. Supports PostgreSQL, MySQL, SQL Server, Oracle, Redshift, ClickHouse, BigQuery, and DynamoDB.
• Hex — best if you want to graduate to notebooks with SQL and Python, plus Snowflake support.
• DBeaver / Beekeeper Studio — free desktop SQL clients if you do not need cloud collaboration or scheduling.

Also lost SeekWell? It reached end of life on July 31, 2026. See the SeekWell shutdown guide.

Frequently asked questions