Illustrative workplace concept
Tritlas is the product NMM Works is building to connect those three. State Atlas and Infra Atlas are the feature areas of Tritlas: State Atlas is being developed for endpoint and site status, while Infra Atlas covers assets including PCs, equipment, tools, and supplies.
State Atlas and Infra Atlas are feature areas within Tritlas. They serve different purposes within one product and are not separate products. Their progress differs, so we show the current stage for each area separately.
The state that machines and sites report about themselves: what is installed, how it is configured, and how the parts are holding up. It is being built so a failing disk is noticed while there is still time to act, rather than after the machine stops.
Closed beta — invitation only
Open the State Atlas pageA site's assets, including PCs, equipment, tools, and supplies, and the work of registering, ordering, and replacing them. An early prototype implements assets, locations, parts, procurement, and receipts. Currently only the owner can access it; integration with State Atlas and the shared operations platform is not complete.
Early prototype · owner-only access
Teams may not have one accessible record of what is installed, how it is configured, which parts are wearing out, or which equipment is due for inspection or replacement. Tritlas is being built around this problem.
A PC dies or gets ransomware, and what was installed and how it was set up goes down with it. The rebuild runs on memory and guesswork.
A disk or a fan can send warning readings well before it fails, but no one may be watching them. Without a shared record, teams may not know which machine needs inspection or replacement until after it breaks.
The equipment, the tools, and the supplies that run out live in somebody's head. The order goes in after the thing has already stopped, and nobody knows what is due next.
Even when someone writes the state down, it ends up spread across different tools, formats, and screens.
Four components are being developed to do one job each and leave a record of what they did. The State Atlas foundation is implemented in our repository, but it is not running in production and collects nothing yet. Infra Atlas has an early prototype that currently only the owner can access.
One place — the control plane — holds the permission rules, the audit trail of every action, and the defined way to register a device, instead of each tool holding its own.
The endpoint software is being built to send readings in a fixed format and record when they arrive, so any displayed state can be traced back to a report. The path that receives those readings is not switched on yet. State Atlas is being built to follow those readings over time and flag a part for review before it fails.
The customer-facing app and the internal operator app are built as separate applications, each designed to have its own sign-in and its own permissions. They never share a screen.
The release format is designed to be signed, delivered in stages, and to refuse a silent downgrade to an older version. Releases have not yet been signed with keys managed for production use.
State Atlas is in closed beta at a small number of invited sites we chose. Nothing is being collected yet, so nothing is being monitored, and it is not for sale yet. Infra Atlas has an early prototype that currently only the owner can access. One shared operations platform underneath both, with each area keeping its own technical domain, is what we are designing towards — nothing has been moved onto a shared operations platform, and that move is on hold until it is agreed, tested, and reversible.
Operations software works closely with sensitive systems. Tritlas is designed with the following limits to reduce security risks. These are fixed design constraints, not options that can be turned off.
State Atlas is designed to limit automatic equipment-data collection to an explicit allowlist for understanding equipment status. Business file contents, passwords, and patient health information are excluded. Automatic collection has not started and will not begin until each field has been reviewed and approved.
Remote desktop, shell access, file browsing, and command execution are not things Tritlas does.
For State Atlas automatic collection, each data field and each action stays switched off until someone reviews its purpose, approves it, and deliberately enables it.
Tritlas does not copy, store, back up, or restore the original business files on your machines or their contents.
Side projects at much earlier stages than Tritlas. None of them is a product yet, and none of them is a feature area of Tritlas.
Screen content that keeps playing when the network drops. It runs locally today. It has never been left running in a real store, and remote management is untested.
View Labs noteAn early concept with consent designed in from the start. Nothing has been built yet, and whether it becomes a product is undecided.
View Labs noteEmail us at the address below. Please leave out patient records, medical data, passwords, payment details, and anything else sensitive.
