About Tracmar · Why I built itI built Tracmar because the PSA I was paying for didn't do what I needed.

I was running my client work in one system, my daily reminders and recurring routines in another, and I still couldn't get a straight answer to simple questions — how much tech time went out this week, which clients keep breaching SLA. Every report meant a ticket to support or a session in a report builder. Meanwhile the cost went up every year and I could never make it look or feel the way I wanted.

So I built the thing I actually wanted to use. Tracmar has run my business every day since.

Mark Shepard, Adelaide IT Solutions
One system, not threeClient work, projects, tickets, daily reminders and recurring routines all in one place.
Answers, not report buildersTime logged by day, week, client or staff member. SLA breaches by client. No support request required.
Predictable costNo per-seat creep, no surprise renewal increases. Founding customers get 20% off for their first twenty-four months.
Built by someone who runs an MSPEvery feature came out of a real need in a real business.

I like the fast-paced workflow — the data is just there. Need a client’s runbook? Search with a shortcut: a few keys, two clicks of the mouse, and it’s there. The data is shared with the team — no emails, it’s all just a chat away.

I can plan out complex workflows on a job, share the ticket, follow the ticket, or even create child workflows. The options are there. But most importantly, with clear workflows on the Today page, I’m not visually over-encumbered, and I can see what work needs to be done.

Nick, Adelaide IT Solutions

If that sounds like your week, have a look at it.

Book a look See the product

Thirty years in IT, and one recurring problem

Mark runs Adelaide IT Solutions, a managed service business in Adelaide, and has spent thirty years in this industry. Long enough to notice 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.

From April to go-live

Tracmar began in April 2026 as a replacement for HaloPSA and went live on 1 September 2026. It is written by somebody who has to use the result the next morning, and that 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.

The fair question

What if something happens to the person who wrote it?

It is the right thing to ask a small software business, and a better one to answer than to leave hanging.

Your data is yoursIt stays in Adelaide, under Australian law. If you ever leave, you get a complete copy of it.
Backups are restored, not just takenBacked up every night to more than one location, and the backups are restored in practice, not just taken — because a backup nobody has restored is only a hope.
Not on anybody's deskTracmar runs on servers operated by Adelaide IT Solutions and R&N Data, not on one person's laptop, and its backups are held off-site.

Next step

Ready to replace your PSA?

Every deployment starts with a conversation, not a signup form. We will look at how you work now, plan the migration from Halo or CSV, configure your instance, and agree a go-live date with you once we have seen your setup.

08 8358 0944

Adelaide, South Australia  ·  hello@tracmar.au

Download the overview (PDF)

No details needed for the download. Prefer a walkthrough? Leave your name and company in the form and we will ring you.

🔒 Spam check

What happens to what you send: privacy.

No newsletter, no drip sequence. A person reads it and replies.