If you're evaluating software for an Australian apartment building, MYBOS and NaloHub will both come up, and on a feature list they overlap on more than half their surface. This page is a fair attempt at the comparison, written by NaloHub's founder, including the situations where MYBOS is simply the better fit. Everything about MYBOS here comes from its public website and support material as at August 2026, if anything is out of date, tell us at info@nalohub.com and we'll correct it.
The one-sentence difference
MYBOS is a building manager's operating system with a resident app attached. NaloHub is a committee-and-resident portal with building manager tools attached. Same category, opposite centres of gravity, and almost every practical difference follows from that.
Side by side
| Dimension | MYBOS | NaloHub |
|---|---|---|
| Built for | Paid building managers first; residents get a companion app MYBOS describes as complimentary | Committees and residents first; the building manager is one of six roles |
| Governance | No motions, voting, minutes, by-law management or state-specific compliance tools evidenced in public material | The core of the product: maintenance-to-motion voting, by-laws readable by residents, dispute records, jurisdiction-aware Compliance Calendar |
| Operations depth | Deep: work orders, preventative maintenance calendars, parcel tracking, visitor check-in, contractor licence/insurance verification, SMS, media screens | Focused: staged maintenance workflow with quotes, recommendations and committee decisions; walk-through checklists; one-click reporting |
| Resident & committee experience | Resident app is a companion to the manager's platform | Residents and the committee are the primary users, visibility of every job's state, self-serve documents and by-laws, decisions on the record |
| Legislation | International facilities platform (strata, hotels, aged care and more), no Australian state-specific statutory tooling evidenced | Australia-only by design; strata legislation of all eight states and territories modelled, with cited answers via Nalo |
| Apps & access | Native iOS and Android apps, including branded options | Runs in the browser on any device, installable to the home screen, nothing to download, nothing to update |
| Trying it | Demo by booking | Live demo building, no signup: demo.nalohub.com |
| Who owns the record | The platform serves the manager's operation | The committee owns the relationship and the data, portable on exit, no lock-in |
| Track record | Founded 2012; company-reported 3,000+ buildings across six countries, with major named customers | New entrant; no case studies yet, the demo building is the evidence on offer |
MYBOS information from mybos.com and support.mybos.com, August 2026.
When MYBOS is the better choice
Honestly: in a large, staffed tower where a professional building manager runs daily operations and the priority is operational throughput, work order volume, parcels, visitor check-in, contractor compliance at scale. MYBOS is deeper, longer-proven, and built precisely for that job. If your building manager is the main user and the committee mostly wants the engine room run well, MYBOS is the safer pick, and its track record is genuinely substantial.
When NaloHub is the better choice
- Committee-led buildings. If the pain is decisions, records and accountability, quotes dying in email threads, votes that take two meetings, handovers that don't happen, that's the half of the job NaloHub is built around and MYBOS doesn't publicly evidence at all.
- Resident visibility. If residents assuming "nothing is happening" is generating complaints and chasing, the fix is a portal where the state of every job is visible, which is NaloHub's centre of gravity, not a companion app.
- Compliance under your state's law. Statutory obligations are shifting onto committees in several states. NaloHub generates your scheme's compliance year from your jurisdiction's actual requirements.
- Owning your record. With NaloHub the committee owns the relationship and the data, portable on exit, no lock-in.
- Buildings without a paid building manager, where MYBOS has no natural daily operator.
Can they coexist?
Yes, and in manager-run buildings with an engaged committee it's sometimes the right answer: the manager's platform runs the engine room, NaloHub runs the committee room, the decisions, the records, the residents. The honest trade-off is two subscriptions, which is why the cleaner fits are the situations above.
How to decide in one evening
- Ask who the software's daily operator would be in your building. If the answer is "our building manager", weight MYBOS. If it's "the committee", or the real goal is residents and the committee seeing and owning what's happening, weight NaloHub.
- Walk through NaloHub's demo building at demo.nalohub.com (no signup) and book a MYBOS demo at mybos.com, evaluating both is exactly what we'd do.
- Put the same four questions to each: Where do committee decisions live? What can residents see? What happens to our records if we leave? What does our state's legislation require of us this year? And ask each for pricing for your building (NaloHub publishes ours: $2 per unit a month plus GST, $99 minimum), then weigh the whole answer, not one number.
Related reading: Nobody is hiding anything. That's the problem. on why maintenance stalls in good buildings, and strata software built for committees on the gap in the middle of the market.