Thirty years in IT, and one recurring problem

Thirty years in this industry teaches you that the software meant to run a service business is almost always built by people who have never had to run one. It handles the shape of the work a vendor imagines, and then you spend your evenings bending your actual week to fit it.

Why it exists

Tracmar began in April 2026 as a replacement for HaloPSA. Halo is a capable platform, and that is rather the point: it is capable in ways a five-person shop pays for, configures around, and never uses. What a small team needs is not more features. It is a system where raising a job, doing the work, recording the time and getting the money in are one continuous motion rather than four applications and a spreadsheet.

It went live on the first of September 2026 — four months ahead of the deadline, because it was ready — after roughly four hundred releases. Every one of those was written by somebody who had to use the result the next morning. That is the whole difference, and it shows up in odd places: the clock stops when the job is resolved rather than when somebody remembers to close it, because forgetting to close a ticket is a thing people do.

Why you can ring it

Tracmar is Australian owned, written in Adelaide, and runs on servers here — owned and operated by Adelaide IT Solutions and R&N Data. When something is wrong you talk to the person who wrote it, in your own timezone. That is not a support tier. It is the only arrangement a business this size can honestly offer, and it happens to be the one most people actually want.