Important notice
This is an early-stage feature area of Tritlas, running as a closed beta at a small number of invited sites. Security, privacy, regulatory, and operational requirements still have to be worked through before it opens up beyond them.
Closed beta — not open to the public
The Tritlas feature area for endpoints and sites
State Atlas is the Tritlas feature area for the state of endpoints and sites. It is in closed beta at a small number of invited sites.
What we are building
What this feature area of Tritlas is being built to gather, who gets to see it, and what it refuses to touch.
- A record of each machine and site — what is installed, how it is configured, how the hardware is doing — designed to be built up from what each machine reports
- Checks designed to follow part health over time and flag a component that needs replacing or inspecting before it fails
- One place — the control plane — that holds the permission rules, the audit trail of every action, and the defined way to register a device
- A data design where every field stays off until someone approves it — nothing unapproved gets collected
- Two separate interfaces, one for customers and one for our own team, built separately from the start
The problem
Why we are building it
When a PC fails or ransomware locks it, the record of its installed software and configuration can be lost with the machine, forcing a rebuild from incomplete information. Hardware health can create a separate problem: warning readings may not be reviewed in time. State Atlas is being built to keep machine and site status records outside the machines and help surface issues before failure.
What kept happening
- A machine dies or gets ransomware, and the rebuild runs on memory and guesswork — nobody wrote down what was installed or how it was configured.
- A disk or a fan sends warning readings for months before it fails, and nobody is watching them.
- Nobody can say which machine is due for a part check or replacement, so hardware gets attention only after it breaks.
- Even when someone writes the state down, it is scattered across different tools, formats, and screens.
What we are building
We are developing State Atlas to help address those situations. The planned workflow would let machines report their status, keep software and configuration records outside the machines, and notify users when hardware-health readings suggest that a component may need inspection or replacement. It is now running as a closed beta at a small number of invited sites, where we install endpoint software and test it. Nothing is being collected from those machines yet, and no field is collected until we approve it.
State Atlas is one of the two feature areas of Tritlas, the product NMM Works is building. Infra Atlas is the other, covering assets including PCs, equipment, tools, and supplies. Both are being designed for a shared operations platform, with a separate technical domain for each area. This is target architecture. Nothing has been moved onto a shared operations platform, the two share no database and no credentials, and neither one syncs with the other.
Who it is for
A situation, not an industry. If these three are true of you, this is being built for you.
- You run more than one location, and the machines are spread across them.
- Nobody on staff looks after those machines as their actual job.
- The cost of retaining an outside IT firm to monitor them is difficult to justify.
- Where we saw it
- We saw this first at dental clinics, then found the same problem at other small clinics and small offices. The situation is what matters, not the industry.
- Who decides
- Whoever runs the business or its operations. There is no IT department to route this through — that is the point.
- How it is delivered
- Software you will install on the machines you already have. No new hardware, no on-site visit, no consulting engagement. There is nothing available for you to install yet.
- Pricing — planned
- Planned: a subscription per location, with an additional charge once a location passes a yet-to-be-defined number of machines. Prices and the device-count threshold are not set, and billing is not available.
What has to be true before launch
We will not offer State Atlas until every one of these is true.
- It has to work end to end
The control plane, the reporting path, and both apps have to hold together as one working system, not as separate pieces.
- The data rules have to be settled
For every field: why it is needed, how sensitive it is, who can see it, how long it is kept, and when it is deleted. All of it decided before anything is collected.
- It has to be proven on real machines
It has to run against real endpoints in a controlled setting, long enough to trust what it reports, before anyone depends on it.
What State Atlas will never do
- The design allows only a fixed, approved list of data fields, and nothing outside that list can be collected. The beta is running and nothing is being collected yet.
- Remote desktop, shell access, file browsing, and command execution are not things State Atlas does.
- A record of a machine's state is not a backup. State Atlas does not copy, store, back up, or restore the original business files on your machines or their contents.
Common questions
Straight answers about where State Atlas stands today.
Can I sign up for State Atlas?
Not yet. State Atlas is in closed beta at a small number of invited sites, and it is not open for you to sign up and use. Email us and we will tell you when it opens up.
Does State Atlas currently monitor Windows endpoints?
No. Endpoint software is installed on machines at the beta sites, but nothing is being collected from them, so nothing is being monitored anywhere. There is nothing you can install yourself, and there is no list of supported Windows versions. Monitoring starts only once we approve the fields it would collect.
Is State Atlas already running on the same platform as Infra Atlas?
No. A shared operations platform is what we are designing towards. Nothing has been moved onto it, and that move will not happen until it is agreed, tested, and reversible. Today the two feature areas are not merged, share no database and no credentials, and neither one syncs with the other.
Is State Atlas a separate product from Tritlas?
No. Tritlas is the product NMM Works is building, and State Atlas is one of its two feature areas. It is not offered as a standalone product, and Infra Atlas is not a rival to it.
Get in touch about State Atlas
Email us at the address below. Please leave sensitive details out of the message.