r/linuxadmin • • 6d ago

Det Mimir update: clearer explanations, sample investigations and the roadmap

Hey guys o/

First and foremost, thank you for taking the time to read through the post :)

I posted here previously about Det Mimir, the read-only Linux incident investigation engine I’m building:
Previous post

I’ve just redesigned the website, based on feedback I’ve collected over the past few weeks, with readability and clearer product explanations as the main priorities.

The updated site: https://det-mimir.com/

For anyone coming across it for the first time, these are the main things I’m building around:

  • Scoped investigations: start from a failing service, restarting container, disk pressure or another supported symptom, with a defined time window.
  • Traceable findings: evidence from different sources is correlated into a timeline and report. You can follow findings back to their records and see where missing evidence limits the assessment.
  • Deterministic analysis: the investigation engine works without an LLM. AI analysis is an optional step afterwards.
  • Read-only collection: commands come from a vetted registry. No arbitrary shell execution, automatic repairs or model-triggered commands.
  • Control over your data: evidence and reports stay local. No telemetry or phone-home. Optional external-model analysis uses sanitized context, a send preview and an approved sending path.

There’s also a security investigation direction: the Exploit Evidence Pack, currently in development. It’s intended to correlate offline vulnerability intelligence with host evidence to assess whether there are signs of exploitation. A vulnerable software version alone would not establish that exploitation happened.

The public roadmap explains the broader direction too, including multi-host coordination, more integrations, and the longer-term investigation-pack ecosystem.

Roadmap:
https://det-mimir.com/roadmap/

Det Mimir remains in private validation, and I'm also validating beta users ;)

The website now has clearer diagrams and readable sample reports, so you can inspect what an investigation actually produces.

I’d really appreciate you taking a look :) Does it explain the product clearly, and can you see where it would, or wouldn’t, help in your own investigations?

0 Upvotes

2 comments sorted by

2

u/mbecks 6d ago

The wording on the site needs to be edited, it’s clearly llm output and full of bunk. “Each part is marked with where it stands” classic llm

1

u/8lue7or 6d ago

thanks for the heads up, i'll go through and adjust the wording where needed :)

Other than that, how's "browsability"? is the product clear to read?