MemBrowse

About MemBrowse

MemBrowse tracks firmware memory footprint on every commit so embedded teams stop discovering size regressions at the moment the linker fails. It plugs into CI, records flash and RAM usage per build, and renders memory trends as interactive charts tied to the git history, so a 3KB creep introduced six weeks ago is attributable to the commit that caused it rather than to whoever happens to be on the release. Builds can be compared pairwise with symbol-level breakdowns, which is the practical difference from a simple size counter: you can see which symbols grew, which padding appeared, and where a compiler or library bump moved the numbers. Memory budgets can be set per feature and enforced in CI, failing builds that exceed them. The testimonials on the site come from recognisable names in the embedded world — Flipper Devices, TinyUSB, MicroPython, Apache NuttX, RT-Thread — which is unusual social proof for a tool this young and a reasonable signal that the integration actually works against real firmware projects. Pricing is deliberately structured for the open-source case: unlimited use for public projects, seat-based for private repositories, with an on-prem option at the top.

Key Features

Tags