Heroku Postgres 15 Is Being Retired: Why It's a Good Moment to Move Your Database to Your Own Cloud Account
Blog post from Qovery
Heroku stopped provisioning new Postgres 15 databases on November 11, 2026, will begin forced upgrades on January 28, 2027, and plans to restrict access to and delete remaining Postgres 15 databases after February 28, 2027. Because Heroku’s three-year support window is shorter than PostgreSQL’s five-year community support period and the timelines of major cloud providers, affected teams can either upgrade on Heroku or move to a database in their own cloud account. Staying on Heroku is the simpler option for teams that plan to remain there; the article recommends testing an upgrade on a fork and generally targeting Postgres 18. Moving to Amazon RDS, Aurora, Google Cloud SQL, or Azure Database for PostgreSQL can provide more control over upgrade timing and infrastructure, and combining the migration with an upgrade to Postgres 17 or 18 avoids upgrading twice. Since Heroku does not support logical replication to external databases or provide the permissions required by common change-data-capture tools, the article recommends rehearsing a pg_dump and pg_restore migration, scheduling a write freeze based on the test, and validating the restored data before switching applications; application-level dual writes are presented as an alternative for systems that cannot pause writes. A public-price comparison suggests that moving may yield limited savings for entry-level setups but larger savings for some high-availability plans, while noting that costs depend on compute, storage, transfer, and engineering effort. The article also describes Qovery as an option for deploying applications and managed databases in a team’s own cloud account, while emphasizing that the database migration itself remains a separate task.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| MCP | 8 | 7,404 | 711 | 183 | -38% |
| Kubernetes | 7 | 3,388 | 294 | 94 | -34% |
| Platform Engineering | 2 | 1,080 | 220 | 61 | -46% |
| AI Agents | 1 | 4,689 | 923 | 218 | -33% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.