In development — one feature area in closed beta

The product NMM Works is building

Tritlas is the product NMM Works is building to connect a site's assets, their status, and the next action. State Atlas and Infra Atlas are its feature areas.

Tritlas dashboard concept with fictional assets, status and next actions.
Illustrative concept using fictional data. Not an actual dashboard or a representation of currently available features.
View concept image at full size

The feature areas of Tritlas

State Atlas and Infra Atlas are feature areas within one product. They serve different purposes and are not separate products. Their progress differs, so we show the current stage for each area separately.

Endpoints and sites

State Atlas

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 page
PCs, equipment, tools, and supplies

Infra Atlas

A 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

Actual UI of the private Infra Atlas prototype with fictional example data.
The actual UI of the private Infra Atlas prototype, shown with fictional data. Access is currently limited to the owner; this is not a publicly available service or evidence of integration with State Atlas. This screen does not verify actual data storage, authentication, or integration behavior.
View example image at full size

What we are building

What Tritlas is being built to connect, what each feature area covers, and how far each one has actually come.

  • A record being developed for a site's assets: machines first, then the equipment, tools, and supplies covered by Infra Atlas as the product develops
  • Endpoint software being developed to report each machine's status in a consistent format instead of relying on manual records
  • Checks being designed to follow part health over time and flag components that need inspection or replacement before failure
  • A workflow being developed to use status information for a request, an approval, and follow-up work
  • One place — the control plane — that holds the permission rules, the audit trail of every action, and the defined way to register a device
  • State Atlas automatic equipment-data collection is designed to keep each field and action off until its purpose is reviewed and the field or action itself is approved and deliberately enabled — nothing unapproved gets collected
  • Room for another feature area later: Tri is the story of connecting assets, state, and action, not a count of parts
The problem

Why we are building it

A business with several locations may have machines, equipment, tools, and supplies spread across them. When a PC fails, the record of its installed software and configuration can be lost with it. Hardware warning readings, replacement needs, and inventory details can also sit in separate places. Tritlas is being built to bring a site's assets, their status, and the next action into one experience.

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 or which piece of equipment is due for a check or a replacement, so it 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

Tritlas is being built as one experience over two feature areas: State Atlas for endpoint and site status, and Infra Atlas for assets including PCs, equipment, tools, and supplies and the procurement and replacement that follow. The product is being developed to use status information in a future workflow that connects a request, an approval, and follow-up work that people can track. State Atlas is running as a closed beta at a small number of invited sites, where we install endpoint software and test it, and nothing is being collected from those machines yet. Infra Atlas has an early prototype that currently only the owner can access.

Both feature areas are being designed for a shared operations platform, with a shared source of truth for assets and a separate technical domain for each area. This is target architecture, not a description of a running platform. 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 and equipment are spread across them.
  • Nobody on staff looks after any of it 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 Tritlas until every one of these is true.

  1. Each feature area 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.

  2. 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.

  3. It has to be proven on real sites

    It has to run against real endpoints and real assets in a controlled setting, long enough to trust what it reports, before anyone depends on it.

Important notice

This is an early-stage product, and its feature areas are not at the same stage. State Atlas is running as a closed beta at a small number of invited sites; Infra Atlas has an early prototype that currently only the owner can access. Security, privacy, regulatory, and operational requirements still have to be worked through before either opens up further.

What Tritlas will never do

  • State Atlas automatic equipment-data collection is limited by design to an explicit, approved allowlist. Each field and action stays off until reviewed, approved, and deliberately enabled; nothing outside that list can be collected. The State Atlas beta is running, but automatic equipment-data collection has not started.
  • Remote desktop, shell access, file browsing, and command execution are not things Tritlas does.
  • A record of a machine's state is not a backup. Tritlas does not copy, store, back up, or restore the original business files on your machines or their contents.

Common questions

Straight answers about where Tritlas stands today.

Can I use Tritlas?

Not yet. It is not open for you to sign up and use, and it is not for sale yet. State Atlas is in closed beta at a small number of invited sites we chose, and Infra Atlas has an early prototype that currently only the owner can access. Email us and we will tell you when that changes.

Does the name mean there are exactly three of something?

No. Tri is the story of connecting a site's assets, their status, and what to do next. It is not a count of parts, and it does not stop another feature area being added later.

Are State Atlas and Infra Atlas separate products?

No. They are feature areas of Tritlas, covering different ground inside one product. Neither is offered as a standalone product, and they are not competing with each other.

Do State Atlas and Infra Atlas already run on one platform?

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 are not merged, share no database and no credentials, and neither one syncs with the other.

Who provides Tritlas?

NMM Works Co.,Ltd., a company registered in Korea. Its registered details are on the company page.

Get in touch about Tritlas

Email us at the address below. Please leave sensitive details out of the message.

Contact us