Where does your data go? Nowhere.

The first question a serious operation asks about monitoring software is where the data lives. With MEMAR the answer is short: on your hardware, on your network, and nowhere else. No cloud, no telemetry, no phone-home. This page is the brief you can hand your security team.

Self-hosted means self-hosted.

Your data never leaves

MEMAR is self-hosted. Machine telemetry, job history, and OEE data live only on your hardware, on your network. There is no Stratum cloud that sees it — because there is no cloud in the loop at all.

No telemetry, no phone-home

MEMAR does not call out to us. No usage analytics, no crash reporting to a vendor, no background sync. By default, core monitoring, control, and licensing talk only to your machines on your LAN — an optional license-renewal check (disabled entirely for air-gap licenses) and two optional features, the Prusa Connect adapter and 3D floor-plan generation, are the only things that need outbound access. Skip those and block everything else.

Offline license, no activation server

License keys are Ed25519-signed and verified locally against an embedded public key. Nothing contacts a license server to unlock the product. An air-gapped instance validates its key with every outbound port blocked.

Open source — read it yourself

MEMAR is AGPL-3.0-licensed. The entire codebase is public on GitHub. Your security team can audit exactly what it does and what it touches before it ever runs on your floor. No black box.

You own everything

Your data, your hardware, your database schema. A SQLite database you control. Export anytime. Nothing about MEMAR holds your floor hostage or locks your data behind a vendor.

Runs where you put it

Docker Compose on a NUC in the shop, a VM in your DMZ, or a hardened box inside an isolated OT segment. No managed service, no required external dependency, no account.

What your security review will ask.

Where does machine data go?
Nowhere but your own instance. MEMAR reads from your machines over your LAN and writes to a database on your hardware. No external destination exists.
Does MEMAR send usage analytics or telemetry?
No. There is no analytics or telemetry pipeline in the product. Nothing is reported back to Stratum.
What outbound connections does it make?
By default, only an optional license-renewal heartbeat (so subscriptions auto-renew). It is turned off for air-gap licenses, which are offline-verified and manually renewed instead — the product is fully functional with all outbound traffic blocked.
How is the license validated?
Locally. An Ed25519 signature is checked against a public key embedded in the build. No activation server, no license check-in, no internet required.
Can our security team audit it?
Yes. Licensed under the GNU AGPL v3, full source on GitHub. Review it, build it yourself, run it forever.
What happens if internet is cut?
Nothing — MEMAR keeps monitoring. The only thing a disconnected instance forgoes is automatic subscription renewal, which air-gap licenses replace with a manually-issued key file.

Deployment options

  • Docker Compose — the standard path. One file, one command, on any Linux box on your network.
  • On-prem VM / bare metal — run it in your DMZ, a dedicated host, or alongside your existing OT tooling.
  • Air-gapped / isolated OT segment — fully disconnected, license delivered as a signed key file. See the air-gap page →

Need it stood up for you? White-glove deployment →  ·  Questions from your security team? Email us →