Heroku will transition its Automated Certificate Management to ECDSA keys between December 21, 2026, and January 29, 2027. The upgrade applies to custom domains on Common Runtime alongside both custom and default domains within Fir Private Spaces. Heroku's automated monitoring will keep applications on legacy certificates if traffic from clients lacking modern support is detected. Replacement certificates will typically deploy during normal renewal cycles approximately one month before expiration.
Key points
Most eligible applications will transition automatically during standard certificate rene…: Most eligible applications will transition automatically during standard certificate renewal windows without needing manual intervention.
Automated system monitoring will prevent upgrades for applications that actively receive…: Automated system monitoring will prevent upgrades for applications that actively receive traffic from clients lacking ECDSA support.
Developers can use the Heroku CLI to either adopt the new certificates early or permanent…: Developers can use the Heroku CLI to either adopt the new certificates early or permanently lock domains onto RSA.
Sources checked by our analysis pipeline: 1
- Last Updated: November 18, 2026
Heroku Automated Certificate Management (ACM) is moving from Rivest-Shamir-Adleman (RSA) keys to Elliptic Curve Digital Signature Algorithm (ECDSA) keys for the Transport Layer Security (TLS) certificates it issues.
ECDSA certificates are more secure: every connection gets forward secrecy, and the keys are stronger. They’re also the only certificate type allowed in the strictest profile of TLS Ref, which now maintains the TLS guidelines Mozilla used to publish. Starting December 21, 2026, Heroku will begin automatically refreshing ACM certificates to switch them from RSA to ECDSA. By January 29, 2027, all ACM certificates for eligible apps will be ECDSA.
Most apps don’t need to do anything. If our monitoring has detected clients that can’t use ECDSA connecting to your app, we’ll keep the app on RSA certificates automatically and your app will continue working normally for all clients. We’ve also sent you an email with details.
To keep RSA certificates for an app, or to go back to RSA after it switched:
$ heroku features:enable acm-rsa-cert -a example-app
The programming language's maintenance strategy has been updated to deliver both security patches and select backported bug resolutions going forward. Because of this expanded focus on stability, the development team has officially rebranded the support period as the legacy maintenance phase. This ongoing support remains fully guaranteed through the previously established timeline ending in March 2027.
The core language maintainers have delivered critical maintenance updates addressing identified security vulnerabilities and routine software flaws. Published by k0kubun, this distribution arrives alongside coordinated maintenance releases across multiple supported release lines to ensure ecosystem stability. Developers relying on these platforms can now access updated packages through standard project distribution channels.
Maintainers have delivered vital security patches and general bugfixes through community contributions from numerous developers and testers. This deployment addresses ongoing stability concerns for systems running modern branches of the language. It arrived as part of a synchronized maintenance cycle impacting several supported release lines on the same day.