Follow up question… https://fleetdm.com/ implies the whole product is still open-source… the telemetry portion of fleet utilizes osquery, what does the MDM portion utilize? MicroMDM? NanoMDM? Or was it built completely “in-house”?

https://github.com/fleetdm/fleet/blob/main/go.mod#L64 NanoMDM

ty

We use some components of MicroMDM as well 🙂

And some ideas from another open source project 😅

Hehe yes indeed

The check is in the mail, I assume 😜

I mean, that’s cool, I guess, but we implement Nudge ourselves, and have an MDM… we liked being able to select individual products that do one thing and do it well, and now it feels like everyone’s trying to do everything.

MDM is totally optional in Fleet -- if you don't configure it you'll get the same old Fleet experience.

I feel fleet has a usp for the mdm part with it being source control driven.

@Shawn Maddock Our goal is to keep it all modular enough that you can use whichever components you like.

USP?

Unique selling point

I get we can choose to not use that component, but it’s still there in the UI. My preference, which probably only matters to me, would be to have separate but connected products that can be installed and enabled as needed. Fleet Telemetry, Fleet MDM, Fleet Patching. etc.

As Zach mentioned, please reach out to us directly if you're seeing any interference or 'auto enabling' of functionality that you didn't choose to deploy. This is not the expected behavior and we can work with you to resolve. (no $$ required 🙂)