We built FuelNote because logging fuel should take five seconds, not five minutes.
It started as a small frustration: punching numbers into a spreadsheet at the pump, losing receipts, forgetting odometer readings, second-guessing what "good mileage" even meant for our cars. We wanted a tool that respected the thirty seconds between pulling the trigger and the receipt printing — and not one second more.
FuelNote is what we wished existed. We use it every day, across every vehicle in the household.
Four beliefs that shape every decision.
- 01
Speed is the feature.
If logging takes more than five seconds, people stop doing it. Every screen we ship defends that bar — and the ones that don't, we cut.
- 02
Offline isn't optional.
Cellular at a pump is unreliable. An app that fails offline is worse than a paper notebook. Ours queues locally and reconciles later.
- 03
Your data is yours.
No ads. No third-party SDKs. No data resale. CSV and JSON exports any time. If we ever stop shipping, your fuel log walks out with you.
- 04
Multi-vehicle by default.
Real households have a car, a bike, sometimes a scooter. FuelNote treats that as the norm, not a paywalled tier.
A small stack, chosen carefully.
We won't pretend the toolchain is exotic — it's deliberate. Every choice is something we can debug at 11pm without a vendor call.
See the open changelog- React 19 + TypeScriptStrict mode, tnum-everywhere
- Dexie (IndexedDB)Local-first store, conflict-free sync
- Supabase PostgresRow-level security, magic-link auth
- Vite + PWAWorkbox service-worker, sub-second cold
- Astro (this site)SSG, zero client JS by default
- Vercel + GitHub ActionsCD on every merge to main
Found a bug? Disagree with a design call? Want a feature?
Every reply comes from a human who works on the product. We read everything.
Stop fighting the spreadsheet.
Start logging in five.
One tap to install. One link to sign in. The next time you stop for fuel, the log is already waiting.