Metabase 63 End of Life: November 1, 2026
Metabase 63 reaches end of life on November 1, 2026, less than four months after its release on July 7, 2026. That is normal for Metabase. Its version support page says every release receives bug fixes and security updates until its end-of-life date, that Long-Term Support versions are supported for 14 months, and that other versions usually reach end of life after about two months. Metabase 62, 61, 60 and 59 all reached end of life together on September 1, 2026.
Metabase versions and their dates
| Version | Released | End of life | Status |
|---|---|---|---|
| Metabase 63 (0.63) | July 7, 2026 | November 1, 2026 | Approaching |
| Metabase 62 (0.62) | June 1, 2026 | September 1, 2026 | EOL |
| Metabase 61 (0.61) | April 30, 2026 | September 1, 2026 | EOL |
| Metabase 60 (0.60) | March 26, 2026 | September 1, 2026 | EOL |
| Metabase 59 (0.59) | February 12, 2026 | September 1, 2026 | EOL |
| Metabase 58 LTS (0.58) | December 17, 2025 | February 17, 2027 | Approaching |
| Metabase 57 (0.57) | November 1, 2025 | May 31, 2026 | EOL |
Metabase 64 was released in September 2026. Metabase's support file gives its end of life as November 17, 2026, only sixteen days after Metabase 63.
Source: Metabase's version support page and the support file behind it, version-info.json. Our build re-reads that file and fails if the dates for Metabase 58, 63 or 64 change. Metabase has set several versions to the same end-of-life day before, so expect these dates to be revised as new versions ship.
Reading a Metabase version number
Metabase writes versions as licence, major, minor, patch. The first number is the licence, not the version: 0 is the free open source edition and 1 is the source-available Enterprise Edition used by the Pro and Enterprise plans. So 0.63.3 and 1.63.3 are both Metabase 63, and they share one end-of-life date. Our pages use the open source numbering, for example 0.63, because that is what a self-hosted instance reports.
Follow every release, or stay on the LTS
- Following every release means an upgrade roughly every two months just to stay supported. That suits teams with automated deployments and a test environment.
- Staying on the LTS version means one line for 14 months. Metabase 58 is the current one, supported to February 17, 2027. It gets bug fixes and security updates but not the features of later versions.
- Metabase Cloud customers are upgraded by Metabase, which says it can pin an instance to the LTS version on request.
What to do
- On 62 or older, other than 58: past end of life. Upgrade now, to the latest release of 64 or to the latest 58 if you want the long line.
- On 63: supported until November 1, 2026. Decide which of the two tracks you are on before then.
- On 58: stay on its latest release, and put February 17, 2027 in the calendar, and check Metabase's support page for the next LTS version well before then.
- Whatever the version: run the latest patch release of it, keep the instance off the public internet unless it has to be there, and give its database accounts read-only access to only the schemas it needs.
Frequently Asked Questions
When does Metabase 63 reach end of life?
Metabase's own version support file gives the end of life for Metabase 63 as November 1, 2026. After that date it receives no bug fixes or security updates.
How long is a Metabase version supported?
Metabase says every release receives bug fixes and security updates until its end-of-life date, that Long-Term Support versions are supported for 14 months, and that other versions usually reach end of life after about two months.
Which Metabase version is the LTS?
Metabase 58 is the current Long-Term Support version. Metabase's support file gives its end of life as February 17, 2027.
What is the difference between Metabase 0.63 and 1.63?
The first number is the licence, not the version. Metabase says 0 is the free open source edition and 1 is the source-available Enterprise Edition used by the Pro and Enterprise plans. Both are Metabase 63 and share the same end-of-life date.
Related
- Metabase — every version, live status and EOL Risk Score
- What is LTS?
- Exploited and Unpatchable
- EOL Risk Score vs EPSS and CISA KEV