The problemWhy 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 we are buildingTritlas 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.