# Announcing the release of 5.0.0 of the CHT Core Framework

**URL:** <https://forum.communityhealthtoolkit.org/t/announcing-the-release-of-5-0-0-of-the-cht-core-framework/5441>\
**Category:** Releases\
**Created:** [November 21, 2025, 8:02am UTC](https://forum.communityhealthtoolkit.org/t/announcing-the-release-of-5-0-0-of-the-cht-core-framework/5441 "2025-11-21T08:02:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![diana](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/diana/32/2049_2.png) [@diana](https://forum.communityhealthtoolkit.org/u/diana)\
**Post date:** [November 21, 2025, 8:02am UTC](https://forum.communityhealthtoolkit.org/t/announcing-the-release-of-5-0-0-of-the-cht-core-framework/5441/1 "2025-11-21T08:02:06Z")

</div>

_We’re excited to announce the release of 5.0.0 of the CHT Core Framework_

See below for some highlights, read the [release notes](https://docs.communityhealthtoolkit.org/releases/5_0_0/) for full details.

## 5.0.0 Highlights

### [Reducing hosting total cost of ownership](https://docs.communityhealthtoolkit.org/releases/5_0_0/#reducing-hosting-total-cost-of-ownership)

Based on the knowledge of hosting dozens of CHT instances for over a decade, Medic found disk space [to be the main cost](https://docs.google.com/presentation/d/1rbpJi654VDvm-zJnqqCO7bDZ6anA77zTPZZh9GjQSS8/) in hosting. CHT 5.0 uses [CouchDB Nouveau](https://neighbourhood.ie/blog/2024/09/23/couchdb-3-4-0-feature-nouveau) to enable disk savings in excess of 30% for large instances.

### [Faster synchronization which uses less server CPU](https://docs.communityhealthtoolkit.org/releases/5_0_0/#faster-synchronization-which-uses-less-server-cpu)

As national deployments scaled to over 5,000 users, the server CPU became overburdened. Upon close inspection, one of the bottlenecks was found to be CHWs requesting the list of documents needed for replication. The API handling this request has been massively improved in CHT 5.0. This means synchronizations take less time and, in turn, reduces server load. This reduction enables the same server to handle more requests with only a software upgrade, without any hardware changes.

### [Welcome prompt when starting a new instance for how to easily add data](https://docs.communityhealthtoolkit.org/releases/5_0_0/#welcome-prompt-when-starting-a-new-instance-for-how-to-easily-add-data)

Administrators logging in to the CHT for the first time reported confusion about whether the app was working. They would see an error message saying `No message selected` . CHT 5.0 leverages [existing training cards](https://docs.communityhealthtoolkit.org/building/training/training-cards-resources/) technology to help administrators get started with adding contacts and configuring the app.

### [And more…](https://docs.communityhealthtoolkit.org/releases/5_0_0/#and-more)

We’ve also implemented loads of other features, improvements and fixed a heap of bugs.  
Please have a look at the [upgrade notes](https://docs.communityhealthtoolkit.org/releases/5_0_0/#upgrade-notes) before proceeding with the upgrade.

---

<div class="post-metadata">

**Author:** ![andra](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/andra/32/1965_2.png) [@andra](https://forum.communityhealthtoolkit.org/u/andra)\
**Post date:** [November 21, 2025, 9:10am UTC](https://forum.communityhealthtoolkit.org/t/announcing-the-release-of-5-0-0-of-the-cht-core-framework/5441/2 "2025-11-21T09:10:58Z")

</div>



---

<div class="post-metadata">

**Author:** ![jkuester](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/jkuester/32/806_2.png) [@jkuester](https://forum.communityhealthtoolkit.org/u/jkuester)\
**Post date:** [November 25, 2025, 5:13pm UTC](https://forum.communityhealthtoolkit.org/t/announcing-the-release-of-5-0-0-of-the-cht-core-framework/5441/3 "2025-11-25T17:13:20Z")

</div>

Unfortunately, [an issue](https://github.com/medic/cht-core/issues/10481) has been identified with the Helm charts included in the `5.0.0` release. Instances running on Kubernetes should wait for the issue to be resolved in `5.0.1` before upgrading.
