In development. Not yet released.
Most shop software treats a rebuild as a work order with a lot of lines on it. This one treats it as an engine: a block with a serial number, positions that get measured, tolerances that pass or fail, and a build sheet the customer keeps.
The part that is actually different.
Per-position readings — every journal, every bore — against the spec for that build, with pass or fail on the number rather than in somebody's memory. Out of tolerance is a glyph and a weight as well as a tint, because the shop printer is a black-and-white laser.
Built and checked: HPSM-011 HPSM-012
A printed record of what was measured and what it came to. The document is the deliverable on a $14,000 rebuild, and it prints from the same data the shop worked from — not a summary typed up afterwards.
Built and checked: HPSM-013
An engine has a nickname, a serial number and a history that outlives any one ticket. It comes back three years later and the shop can see what was done to it, by whom, and what the bores measured.
Built and checked: HPSM-010
The parts every shop needs, done properly.
Estimate, approval, work, invoice, close — and the transitions are enforced by the server, not by hoping. A ticket cannot be invoiced with a clock still running on it.
Built and checked: HPSM-001 HPSM-004
The tax rate, the discount and the price group are snapshotted onto a document when it is written. Changing a rate next year cannot rewrite what a customer was quoted.
Built and checked: HPSM-003
A stack of jurisdictions with their own rules — state, county, city, transit — each taxed on its own base and rounded once, because that is how a return is filed. Exemptions are a reason, with the certificate on record.
Built and checked: HPSM-060 HPSM-061 HPSM-062 HPSM-067
One page of cards: what is promised this week, what is finished and still on the floor, what is below minimum, what the floor asked for that nobody ordered. Drag them into the order you want; each role starts somewhere sensible.
Built and checked: HPSM-087
Stock that adds up, and suppliers you can argue with.
On-hand and average cost are replayed from an append-only movement ledger, so the shelf value and the parts screen cannot quietly disagree. Counts adjust through the same ledger.
Built and checked: HPSM-006 HPSM-030 HPSM-039
What is below minimum, grouped by supplier, ready to become an order. A shop should not be re-typing a buying list it already has.
Built and checked: HPSM-018 HPSM-019
Enter the bill and see it against what was ordered. The $4,090 order that arrived as a $4,180 invoice is nobody's job to notice, which is exactly why it goes unnoticed.
Built and checked: HPSM-045
Charged with the part, credited when the old unit comes back, and chased from the supplier when it goes the other way — joined on the physical object rather than on two separate hopes.
Built and checked: HPSM-042 HPSM-070 HPSM-071
The month, in the bookkeeper's terms.
A ledger, not a stack of photocopied invoices: balance forward, what was charged, what was paid, what is due — tying to the receivables report to the cent, which is checked rather than assumed.
Built and checked: HPSM-044
Sales, payments and supplier bills as journals, with the debits and credits proven equal before the file is handed over. Your chart of accounts, not ours.
Built and checked: HPSM-036 HPSM-045
On your hardware, with the boring things done.
PostgreSQL on a machine in your building. Backups run on a schedule, and the restore is rehearsed rather than hoped for — an untested backup is a rumour.
Built and checked: HPSM-025 HPSM-034
Staff passwords are hashed and never recoverable. Secrets the server has to present — a mail password, an API key — are encrypted with a key that is not in the database, so a stolen backup carries ciphertext and nothing that opens it.
Built and checked: HPSM-080
An audit log over the things worth arguing about later, and a save that would erase somebody else's work is refused — naming who changed it and when.
Built and checked: HPSM-035 HPSM-046
It runs on a PC in your shop. The server and the database are yours, on your hardware, on your network. A hosted option is planned for the things that have to reach outside the building — emailed links, off-site backups — and the on-prem product will stay the product.
Windows, with a single installer that sets up the database, the service and the firewall rules. Linux is supported for the server. macOS is a client story and is not finished.
Yes, and without asking anyone. It is a PostgreSQL database you own; the accounting export and every report also write CSV.
Not decided. Nothing is released yet, so there is no price to quote and no point pretending otherwise.
Not yet. There is nothing to hand out until the first release.