Work orders, task sheets, timesheets, parts, scheduling, inspections, machines and fleet in one database, all linked together, on your own server. It works with no internet, it runs on hardware you already own, and it integrates with the finance software you already use.
And you can just ask it. Say “hey umami” across the bay with your hands in an engine, and it answers out of your own records — what is waiting on parts, who is on which job, what you did to that unit the last time it came in.
| WO # | Date | Customer | Machine | Status | Lines | Hrs | Total | Flags |
|---|---|---|---|---|---|---|---|---|
| WO-1042 | 8/21/26 | Demo Pump & Rental | Pump Skid · Natural… | In progress | 3 | 14.6 | 6,842.50 | 2 new write-ups · parts on order |
| WO-1039 | 8/19/26 | Demo Fleet Services | Standby Genset | Waiting parts | 4 | 8.2 | 4,125.00 | parts on order · 1 unapproved |
| WO-1037 | 8/18/26 | Demo Equipment Co | Diesel Welder | In progress | 2 | 5.8 | 2,380.75 | 1 new write-up |
| WO-1034 | 8/14/26 | Demo Industrial | Transfer Pump | Open | 3 | 2.4 | 1,148.20 | |
| WO-1031 | 8/11/26 | Demo Rental Yard | Boom Lift · 60 ft | In progress | 5 | 18.1 | 7,920.00 | 3 new write-ups · parts on order |
| WO-1028 | 8/7/26 | Demo Parish Services | Wheel Loader | Open | 2 | 0.0 | 1,825.00 |
From the phone call to the invoice: the job, the hours, the parts and the machine in one database, not four sources that have to be made to talk to each other.
Ask it instead of hunting. “Hey umami — what is waiting on parts?” and the jobs that are, come back. It reads the same rows the screens do.
Know what a job was quoted at while it is still running.
Job lines carry quoted against actual, and customer approval is recorded on the line it belongs to. Nobody argues about it four months from now.
A man clocks on to a task, not on to the day.
Hours land on the job and the task they were spent on. That is the only reason a margin report is worth reading.
The parts counter is a screen, not a notebook.
Catalogue, receiving, lots, cores and serialised units sit behind the counter ticket and the physical count, so the man selling a part can see what is left and which job it was bought for.
Know what you asked for, who answered, and what you paid.
Purchase orders, vendor offers and quote comparison together, tied to the job the parts were bought for.
One board everybody can see.
Assign the work, set the dates, and escalate the hot job before the customer does it for you.
The paperwork comes back from the yard intact.
Work orders, estimates, sales orders and inspection reports come out of one document engine and are saved onto the record they came from.
The customer, his sites, and every machine he owns, in one place.
Contacts, addresses, the units on each site and the work behind them. What a customer owes you in work is a question with an answer, not a hunt through a filing cabinet.
Wages, costs and margins stay with the people they belong to.
You decide what each person can open and what they can change, and it holds wherever that record turns up: the desk, the tablet and the phone. Payroll is kept off the shop-floor login in the database as well, not only on the screen.
You talk to it and it answers about your shop, out of your own records. It is not a help file, and it is not a chatbot that has never seen a row of your data.
| WO # | Customer | Machine | Waiting on | Assigned |
|---|---|---|---|---|
| WO-1039 | Demo Fleet Services | Standby Genset | Injector set | D. Reyes |
| WO-1031 | Demo Rental Yard | Boom Lift · 60 ft | Lift cylinder seal kit | M. Cole |
| WO-1042 | Demo Pump & Rental | Pump Skid · Natural… | Coupling, gasket set | D. Reyes |
Say “hey umami” and ask. You get your own rows back, not an article.
The everyday answers are read straight out of your database. They need no internet, no graphics card and no subscription behind them, because there is no model in the way. Ask it what is waiting on parts, who is on which job, what a customer owes in work, or what you did to a unit the last time it came in.
Not a fixed list of canned reports somebody else chose for you. A builder over the shop's own data, where every figure keeps the query that made it.
Ask the board a question. Say what you want counted and it will help you write the metric; ask what a number means and it reads the figures back in words, with the query it came from.
If you can describe the number, you can put it on the board.
Write the metric over your own tables, name it, and keep it. Hours over quote, gross margin, work in progress, billable utilisation, jobs awaiting parts, cycle time, on-time close, and then the ones only your shop cares about.
A number that moves traces back to the query that made it.
Every metric is a saved query with revisions. Change how a figure is worked out and the older definition is still there to compare against.
The board tells you what is out of band before the customer does.
Set the threshold once and the exceptions come to you. Then take the result wherever it has to go.
Your shop's way of doing a job, written down, and then handed to whoever picks up the next one. Templates are yours to write and yours to change.
The sheet drafts itself. Ask for a task sheet on a model and it drafts one out of what this shop has already done to that model — your steps, your wording, not a generic checklist.
The way your best hand does the job becomes the way it gets done.
A job breaks into tasks, and the tasks can be drafted from what the shop has already done on that model. The man who picks up the next one starts from the last one instead of from a blank line.
Build your own checklist and run it at the machine, not from memory.
Items, results and photographs on a tablet in front of the unit. A finding becomes a job line without retyping it, so nobody writes the write-up twice.
Every unit the shop has ever touched, and what was done to it, when, and by whose hand. The machine remembers even when the men change.
Ask a machine what happened to it. “What did we do to that genset last time?” is a question with an answer, read out of the unit’s own history while you are standing at it.
The whole history of a machine, on the machine.
Serial, model, hours, who owns it and every job it has been through. When a customer asks what you did last time, the answer is on the screen before he finishes asking.
Attach the manual once, and every unit of that model has it.
Manuals, wiring diagrams, parts books and build sheets hang on the model, not on one machine. The men open them from the job they are standing in.
The right revision stays with the right machine.
A document or a procedure can be pinned to a serial range, so an older unit does not get handed the newer book.
Ownership, custody and state are three different facts about a machine, and the program keeps them apart instead of guessing.
Ask where it is and what it earned. Who has it, when it is due back, what it has made against what it has cost — out loud, from the yard, without going back to the office.
The machine that earns and the machine that gets fixed are the same machine.
Out, back, serviced, out again. What the unit has earned, against what it has cost you to keep it running.
The date that costs money when it passes comes to you first.
Registration, insurance, certification and service intervals, held on the machine and surfaced before they lapse.
What happened to it, when, and by whose hand.
Meter readings, movements, damage, services and the notes the men wrote at the time. The log belongs to the machine and outlives the work order.
Every machine wears a plate. The plate scans to that machine's own record, on a domain the shop owns.
And the paperwork reads itself. Drop a supplier’s quote or invoice on the program and the assistant reads it into rows — part numbers, quantities and prices — then the arithmetic is checked before anything reaches your catalogue.
Your machines scan to your domain, not ours.
A shop that runs Umami stands up its own service-database site. The plates you put on your machines point at it. A customer, a driver or a mechanic scans the plate and gets that unit's record: what it is, what has been done to it, and the documents you chose to publish.
Things that are true of a self-hosted program and are deliberately not true of a per-seat, per-month service that assumes a permanent internet connection.
PostgreSQL on the shop's own box. Nobody else's shop is in your database and nobody else's login reaches it. The shop owns the data even where the vendor hosts the machine — an arrangement in the architecture, not a sentence in a contract.
Capability · your PostgreSQL, your hardware, your backups
Database on your server, documents in that same database, updates from your own update server. A man at a well site with no bars has the whole program, not a cached fragment of it. The optional assistant backend is the only thing that ever reaches outside the building, and it switches off.
Capability · fully usable with the assistant backend switched off
No Google Play account, no App Store review, nobody else approving your shop's software. The mobile app fetches the update from your own box and replaces itself, keeping everything it was holding offline.
Capability · nothing published to a store · Android 7.0 and later
It was written to run on what a shop actually has: the office desktop, a small box in the corner for the database, and the tablets already in the bays. No graphics card is required, on the desk or on the server, and the everyday assistant answers do not need one either.
Capability · no graphics card required · Windows 10 and 11 · Linux
The assistant reads the shop's own rows, so the questions you ask all day need no signal and nothing metered. Where a model genuinely helps, it is optional and it is yours: run it on your own hardware or point it at your own key, and turn it off whenever you like.
Capability · your rows for the everyday answers, your choice of backend for the rest
Umami does not want to be your accounting package and will not ask you to move your books. It owns everything before the invoice — the job, the hours, the parts, the machine — and hands over a clean invoice at the end of it.
Capability · the job, the hours, the parts and the machine here; the books where your accountant already keeps them
Operations that keep machines running and want their own numbers about it, on their own screen, without asking anybody's permission to get at them.
You own the iron and it has to be ready. Service intervals, hours, downtime and what a unit costs you to keep, held on the machine itself.
You work on other people's machines. Quoted against actual, write-ups from the field, and paperwork that comes back from a customer's yard intact.
Out, back, serviced, out again. The machine that earns and the machine that gets fixed are the same machine, and the plate on it should say so.
Model documents, serial ranges and warranty work, shared with the independent shops that service your machines. The manual and the machine's history travel together.
Not for: auto repair, and not a general-purpose field-service tool with an equipment skin on it. This was written on a shop floor, for machines that carry serial numbers, service histories and a plate.
None of the steps is "create an account".
Your own server, or a machine in the office. PostgreSQL goes on it, with the small service the phones talk to beside it. It listens on your network, not on the internet.
An installer for Windows or Linux. It talks straight to your database. Updates come from your own update server, when you decide to take them.
Point them at your box once and they update themselves from it afterwards. No store account, nothing published to Google or Apple. Android 7.0 and later, iOS to follow.
Your existing records come across with you: machines, customers, parts and the jobs behind them. Importing them is a job we do with you, not a wizard we leave you with.
Priced per shop, not per seat per month.
The number depends on the size of the shop. It is not a subscription that grows every time you hire a man. Ask what it costsTell us what you run and how the shop works. You get half an hour with your kind of machines on the screen, and a straight answer about what Umami does and what it does not do yet.
The awkward ones are here on purpose.
No. The database is on your server, the mobile app holds its work offline, and the program updates from your own update server. The only thing that ever reaches outside the building is the optional assistant backend — and the program is fully usable with it switched off, which is the state a man at a well site is in anyway.
It is PostgreSQL, so it is backed up and restored like any other PostgreSQL: your backup, your schedule, your off-site copy, sized to the shop and set up with you at installation. Documents and photographs are rows in that same database, so one dump takes the lot and nothing is left behind in a file share.
Meanwhile the phones and tablets keep working offline and sync when the box comes back.
It is your PostgreSQL on your hardware. Any SQL client, pg_dump,
or the export on the reports board. Documents are rows in that same database, so they come
out in the same dump as everything else. There is no export fee and nothing to negotiate,
because there is nothing to hand back — you never gave it away.
No, and it should not. It integrates with the finance software you already run. Umami owns the job, the hours, the parts and the machine, and hands over a clean invoice at the end of it. Your books stay where your accountant already knows how to find them.
An ordinary office desktop, running Windows 10, Windows 11 or Linux. No graphics card is required, on the desk or on the server. The tablets in the bays can be the ones you already have.
For the server, small. PostgreSQL and the little service the phones talk to sit on the same box. Nobody needs to buy a rack.
Android 7.0 and later today, iOS to follow. The phones update themselves from the shop's own server, so nothing is published to a store. The men can use their own phones; the shop revokes access by killing the token, and the cached copy expires on its own.
Electricity and a box. The everyday assistant answers cost nothing at all, because they are read out of your own database. If you turn the optional model backend on, it is metered by whoever you chose to run it, on your own hardware or your own key, and you can turn it back off.
No. Rights are set per person: a mechanic sees his own time and a manager sees everyone's. Payroll is kept off the shop-floor login in the database as well, not only on the screen.
It is a working system, in daily use in the shop it was written for, and it is still being built. You will be told plainly which parts are finished and which are not — the mobile app is Android today, with iOS to follow — and you will be told before you buy, not after.