nRFCloud legacy vs memfault confusion

RE: nRFCloud legacy vs memfault confusion

Eau Du Puid — Wed, 25 Feb 2026 19:41:56 GMT

Great thanks, that was helpful

Kind regards

Peter

RE: nRFCloud legacy vs memfault confusion

Natasha_C — Wed, 25 Feb 2026 19:21:40 GMT

Hi Peter,

We do not have a comparison table of the different platforms but you do not need to migrate existing devices.

Both nRF Cloud and Memfault are active at this time to support customers from both as we integrate the platforms. We are working to ensure a seamless transition of nRF Cloud customers into Memfault by ensuring device data, security and OTA capabilities in nRF Cloud are supported in Memfault without requiring device side changes. This includes:

Memfault will support the same device-to-cloud claiming for the nRF91 Series. Currently this is only done in legacy nRF Cloud;
Device data sent to nRF Cloud by any existing registered devices will be passed to Memfault without any device changes; and
For devices set up in nRF Cloud today, they must use the nRF Cloud OTA. As we integrate OTA systems, the UI will move to Memfault and be able to OTA devices regardless of where they were setup.

For all devices setup and maintained in nRF Cloud, the UI is still active. As the integration proceeds, functionality will move to Memfault.

As you mention, it is possible to set up and use Memfault today with the nRF91, nRF52 and nRF54 chips. This is because the Memfault SDK is implemented within the nRF Connect SDK allowing customers to onboard easily to Memfault. The full functionality of Memfault would be available for chips setup with this approach.

TLDR:

You do not need to migrate existing devices. As we integrate the platforms, we'll do it for you.
If you want to use security services to onboard the nRF91, or make use of device-to-cloud location services, then use nRF Cloud today as this functionality is not yet available in Memfault.
If you want to experience the full capabilities for device debugging, observability and OTA, integrate with the Memfault SDK via NCS in the new platform. As the functionality is linked, we will be able to merge your accounts

Thanks,

RE: nRFCloud legacy vs memfault confusion

Eau Du Puid — Fri, 20 Feb 2026 20:57:42 GMT

Thank you for your reply.

Is it possible to have a comparison between nRFClound and memfault (table ) ?

Kind regards

Peter

RE: nRFCloud legacy vs memfault confusion

Natasha_C — Fri, 20 Feb 2026 18:30:57 GMT

Hi there,

Thanks for your patience.

At the moment, using nRF Cloud and Memfault requires switching between two separate accounts to access their respective functionality. We are planning to merge the platforms in the future; however, I’m unable to provide an estimated timeline at this time.

Memfault’s OTA functionality is definitely worth exploring. In addition to providing a robust and secure infrastructure for delivering updates quickly across your fleet, it offers several capabilities that differentiate it from other OTA providers. These include the ability to pause or abort an ongoing deployment, roll back to a previous software version, and perform staged rollouts — allowing you to deploy updates to a subset of devices first to evaluate real-world performance before releasing them fleet-wide.

You can find more information about OTA here: https://docs.memfault.com/docs/platform/ota

Thanks,

RE: nRFCloud legacy vs memfault confusion

Eau Du Puid — Thu, 12 Feb 2026 14:15:18 GMT

If I mad add: the main functionality for all our devices is OTA

RE: nRFCloud legacy vs memfault confusion

Eau Du Puid — Wed, 11 Feb 2026 13:01:44 GMT

Hi Michal, thank you that would be nice. I have also nRF52 and nRF54L15 that I would like to integrate in the same platform. For the nRF91 series in particular , I need cloud based security according to European law for public sector data.

Kind regards

Peter

RE: nRFCloud legacy vs memfault confusion

Michal — Wed, 11 Feb 2026 12:36:27 GMT

Yes, you can use the memfault functionality with nRF91 series.

The question is which functionality do you need right now. We are currently actively working on merging everything into one platform, but it takes time.

I will ask the nRF Cloud team to provide some more information about the current way of working with nRF91, nRF Cloud and Memfault.

Best regards,

Michal

RE: nRFCloud legacy vs memfault confusion

Eau Du Puid — Wed, 11 Feb 2026 10:37:45 GMT

But it seems to be possible to use the memfault platform:
docs.memfault.com/.../nordic-nrf-connect-sdk-guide

RE: nRFCloud legacy vs memfault confusion

Michal — Wed, 11 Feb 2026 09:12:42 GMT

Currently you still have to use legacy view for cellular devices, yes.

Best regards,

Michal

RE: nRFCloud legacy vs memfault confusion

Eau Du Puid — Tue, 10 Feb 2026 16:08:06 GMT

Hi Michael

The link you provided brings me to the legacy view. But this was not my question. I am wondering if the legacy view is still active or if I need to migrate devices to the new platform. I can not find any information and that.

Kind regards

Peter

RE: nRFCloud legacy vs memfault confusion

Michal — Tue, 10 Feb 2026 15:13:16 GMT

A quick update: in the left menu at the very bottom there should be an "nRF Cloud Home" button that should bring you to the legacy view.

Best regards,

Michal

RE: nRFCloud legacy vs memfault confusion

Michal — Tue, 10 Feb 2026 15:00:06 GMT

Hello Peter,

I am checking that with our nRF Cloud team.

Could you tell me if this link works for you? If it does then you should be able to choose nRF91 there.

https://app.nrfcloud.com/#/experience-chooser

Best regards,

Michal