Pricing

We have integration guides available in our help documentation. The integration process varies slightly dependent on your chip type and/or operating system. Take a look at our documentation for MCU devices, for Android, and for Linux.

You can check our supported architectures and operating systems in our help documentation.

A monthly active device is a device that sends regular debugging and monitoring data to Memfault during the reporting period (calendar month). The fee for monthly active devices is a usage fee which covers the data costs associated. Max fleet size covers the maximum amount of devices on that plan that can check in to Memfault but not send debugging or monitoring data.

This allows for a scenario where you have Memfault integrated on a high number of devices but only a subset of those devices are sending data every reporting period. Please note, if more devices report data than you have within your contracted monthly active devices, this may incur an additional usage fee.

A Heartbeat for Memfault is a configurable time window over which the metrics you track are collected and the data is aggregated. As standard we provide hourly Heartbeats for most devices but this can be configured dependent on your use case and specific device requirements.

A Session refers to a period of activity on the device such as the usage of a feature or function in which Memfault will capture a customizable set of metrics. Each session type is defined by the Memfault customer, for example for a camera you may want to have two session types, recording and uploading but you could define any Session types you want. When either of these functions is used on the device Memfault will capture the occurrence, the interval and the metric information for that Session.

A project is typically used to manage different product lines usually running different hardware with one project per distinct product line. Your data will be collected and sent to a defined project and will be available within that project. You can read more about projects within the organizing your devices section of the Memfault documentation.

A product architecture is the combination of codebase and chipset used to build an end product. If these are materially different product to product then each will count as 1 Product Architecture.

Yes, Memfault can support set-ups which utilize multiple different architectures. For this type of set-up you will likely need our Scale or Enterprise plan but it is best to talk to us.

Memfault provides all the tools required for a customer to make their implementation fully GDPR compliant.

Customers on our Enterprise plan can enable automatic export of the metric data Memfault collects from their devices to an AWS S3 endpoint.