Two minutes to set up / then it runs
Set It Once. Get Reminded Forever.
Two minutes to add a machine and its interval. ServiceDue does the remembering.
Free while ServiceDue is in early access. No card required.
One line per machine. One date that matters.
Every asset, its interval, and the date it comes due next. The only thing on the page that catches your eye is the thing that needs you.
Shop ledger / example
| Asset | Every | Last serviced | Next due |
|---|---|---|---|
| Air compressor, 60 gal | 90 days | 2026-05-02 | 2026-07-31 Overdue 19 days |
| Rooftop unit RTU-1 | 120 days | 2026-04-25 | 2026-08-23 Due in 4 days |
| Bridgeport mill | 180 days | 2026-03-14 | 2026-09-10Due in 22 days |
| Forklift #2 | 30 days | 2026-08-04 | 2026-09-03Due in 15 days |
Example ledger. Set the interval once; the next-due date recomputes itself after every logged service.
How the date is kept
Maintenance memory that never takes a day off
A last-serviced date of 2026-05-02 plus a service interval of 90 days gives a next-due date of 2026-07-31.
You enter two things
Name the machine, set how often it needs service, and record when it was last done. That is the entire setup, and it takes about a minute per asset.
ServiceDue keeps the date
Next due is last serviced plus the interval. Every asset sits in one table marked ok, due soon, or overdue, so a glance is enough.
A logged service rolls it forward
Mark a machine serviced and the next-due date recomputes from that day. The status clears, the history keeps the date, and the cycle starts again.
Before it lapses
Built on Supabase with reminder delivery through Resend
What this replaces
You are the only reminder system your shop has
Sticky notes and calendar guesses do not scale past a few machines
Remembering intervals for 20 assets is a full-time job
Start tracking
Every untracked day is another interval quietly slipping past
Free while ServiceDue is in early access. No card required.