About
We think endpoint inventory should be current, bounded, and checkable
KeepRails started from a small, annoying observation: the AI tools doing the most work inside engineering teams were the ones no inventory could see. They arrive per-laptop, update themselves, and leave their traces in config files rather than asset registers.
What we believe
A measurement is only useful if you can repeat it
So the scoring and mapping path is deterministic and versioned. Same machine, same snapshot, same result — and the version numbers travel with the artifact.
A blank is worse than a declared gap
Anything the scan could not cover is labeled, not omitted. "Not observed in the window" is a different claim from "unused", and we never collapse the two.
Inventory tooling should not become a new risk
Prompts, code and tool payloads never leave the device. Software that quietly exfiltrates your work is not a trade anyone should accept.
What we will not do
What we publish
No team roster, funding history, customer list, or testimonial section appears here, because none has been established for publication. When there is something citable, it goes here with its source.
See whether it holds up on your fleet
Start with one machine. No account required.