Free warranty and repair management software: does it exist?

Yes. But the phrase "free software" covers three very different things, and picking the wrong one is where service centres lose a few months and start over.

This article separates the three kinds of free, points out a common search-result mix-up, walks through the options that carry no licence fee, and says plainly what the word free does not include.

Three kinds of free, and the catch in each

Free trial. Fourteen or thirty days, enough to see the interface, not enough to know whether the software survives the way you actually work. When it expires you pay, and by then your data is already inside.

Limited freemium. Free forever, but capped: one user, a hundred tickets a month, or exactly the features you need once the work gets real. That is a business model rather than a promotion, and the cap always sits just below what a growing service centre needs.

Open source. The licence lets you use, modify and deploy with no licence fee, no user limit and no expiry date. This is the only kind where the word free still means the same thing in year three. In exchange, the infrastructure and the operations are yours.

When reading a "top free software" list, the first useful move is to sort each name into one of those three buckets. The list usually shrinks fast.

Maintenance software is not repair-service software

This is the most expensive mix-up, and search results actively encourage it: ask for free warranty and repair software and half the answers are equipment maintenance software.

The two solve different problems:

• Equipment maintenance. Managing your own machines: preventive schedules, breakdown alerts, asset life. The user is your internal engineering team.
• Warranty and repair. Managing customer devices that come through the door: intake, quotation, repair, parts, handover, and answering "is mine ready yet". The user is an outside customer.

Maintenance software has no concept of a customer intake ticket, no tracking portal, and no process for sending faulty parts back upstream. Finding that out after installation costs you the data entry twice.

Options with no licence fee

Spreadsheets. Genuinely free, and not to be sneered at when volumes are low. The ceiling sits around a few dozen tickets a month at a single intake point. Past that, three things break: nobody knows where a job stands when the owner of the file is away, customers still have to phone for status, and parts stock drifts from reality because it is deducted by hand.

Open-source ticketing. osTicket, FreeScout and Zammad carry no licence fee and handle request flow well: receive, assign, reply, close. But they were built for support desks, not workshops. No parts inventory, no serial tracking, no return process for faulty components. A good fit when the work is mostly answering people, a poor fit when physical goods move in and out.

Open-source ERP. ERPNext ships a warranty claim module: pick a serial number and it tells you whether the item is under warranty or covered by a maintenance contract, tracks the status through to closure, and can raise a visit when someone has to go on site. Dolibarr pairs a ticket module with stock. With Odoo, check first, because the module split between the community and paid editions is not the same. The common trade-off: no licence fee, but you swallow an entire ERP to use one module, and configuration is measured in months.

Purpose-built open-source repair software. This is the thinnest category, because writing specifically for repair operations addresses a far smaller market than ERP or helpdesk. Goby Care sits here, MIT licensed, running on your own servers.

What free actually costs

The zero is on the licence line, not on the total. The rest is still real:

• Servers and backups. A small server covers most service centres, but backups have to exist and have to be restore-tested at least once. A backup never restored is not a backup.
• Security updates. Anything facing the internet needs patching. Nobody does that for you.
• Setup and configuration. Every workshop runs differently. The software bends to your process, not the reverse.
• Training and initial data. Parts catalogue, existing customers, jobs already in progress. This is the heaviest part and the one most often left out of the plan.

Put simply: open source saves you the annual subscription and the vendor lock-in. It does not save you the human effort.

Choosing by size

• Under thirty tickets a month at one location. A spreadsheet still works. Do not install software because it seems like the done thing.
• Above that, or several branches. You need one place to check progress, otherwise every branch grows its own file.
• Serial-based warranty or returns to the manufacturer. Spreadsheets are out. Serials and return flows have to be traceable for the life of the product, searchable years later.
• Customers calling for status. A public tracking page removes that entire category of calls. It is usually the most visible gain in month one.

Four questions before you commit

1. What is the licence, and is it still free in year three?
2. Where does the data live, and can you take it out if you ever switch?
3. Does it track parts and serials, or only tickets?
4. Can customers check status themselves, or must they call a person?

The first three filter for software that is genuinely free. The fourth filters for software genuinely built for repair work.

Where Goby Care sits

Goby Care is warranty and repair management software under the MIT licence: no licence fee, no per-seat pricing, no cap on tickets or technicians, running entirely on your own infrastructure.

It follows the full life of a device: the customer submits a request through a public portal with no account, the request is approved into a service ticket, the ticket moves through repair steps and ends as repaired, replaced under warranty, or unrepairable. Parts and serial inventory live in the same place, faulty components are grouped for return to the supplier, and handover is confirmed with a signature. Customers check status by ticket code and get email updates, so your team stops fielding progress calls.

One thing stated plainly so you do not go looking: the source is opening progressively, so there is no public download link yet and no self-service demo. The build is handed over and configured by Tetra to match how your centre runs. Setup is a one-off fee, additional development is charged by the day, and there is no subscription.

If you are weighing a spreadsheet against dedicated software, get in touch and we will look at which one your process actually needs. If the spreadsheet still does the job, we will say so.