Since 2006, as an operator first, software company second.
We built what we needed — and couldn't find.
After two decades managing submetering operations in Brazil, we kept running into the same gap: the data came in fine, but getting it all the way to a resident's bill — accurately, automatically, at scale — required stitching together systems that were never designed to talk to each other. So we built one that was.
We were operators before we were a software company.
We started as a submetering operator in 2006 — doing manual readings, managing billing cycles, handling resident disputes. We were the ones in the field, and the ones on the phone when something went wrong.
LegitOS wasn't designed from the outside. It was built from the inside of an operation that depended on it. Every module exists because, at some point, we needed it to exist and found nothing good enough.
That history is the reason the platform goes all the way from meter reading to resident invoice — not because we wanted to build more features, but because partial solutions kept breaking at the seams.
See it in production →Built inside a live operation.
Across water, gas, and energy in residential and commercial buildings.
From small condominiums to large multi-family developments.
Across all active meters and protocols.
Four things we kept learning the hard way.
A reading is worth nothing until it becomes a charge.
Collecting meter data is the easy part. The hard part is what comes after: validating the reading, applying the right tariff for the right unit, splitting shared costs, generating an invoice a resident actually understands. When billing lives in a separate system, that last mile breaks constantly — and it's always the operator who gets blamed.
Leaks are discovered in billing cycles, not in meters.
With monthly readings, a leak shows up as a high bill — 30 days after it started. With continuous data and billing in the same platform, we can detect abnormal flow within hours and alert the property manager before the damage compounds. That's only possible when the system owns the full chain.
Disputes are won or lost on data you either have or don't.
When a resident questions their bill, the answer is either immediate or it isn't. Operators using separate MDM and billing systems spend hours reconciling exports across vendors. We wanted one screen that shows exactly what the meter recorded and exactly what was billed — interval by interval.
White-labeling only works if the whole platform is yours.
Partners who resell submetering services need to put their name on everything the resident sees — the portal, the app, the invoices, the alerts. If part of the stack comes from a third party, that third party's brand leaks through. LegitOS is built to be invisible as infrastructure and fully branded as a product.
This is why LegitOS is one platform, not a stack of point solutions.
Every layer above exists because a partial solution broke somewhere. See exactly what that looks like today, module by module.
See it running on real data.
We'll walk through the full chain — from a meter reading in the field to a resident invoice — using live data from our network. No slides, no mockups.