Ledger
Bookkeeping for one. An AI autopilot reconciles the bank feed and email receipts into an approval inbox, and 63 Rust tests guard the money side. I see my whole financial position on one screen.
alexevoy.dev/dashboards
The whole business on one screen. Even with no signal.
Most owner-run businesses live across a dozen browser tabs and a spreadsheet or two, none of them talking to each other. I build consoles that put the numbers you actually check and the controls you actually use in one place, on your own machine.
My roots are in rural Wales, so local-first is just how I build. The console keeps working when the broadband doesn't, and there's no monthly fee per person just to look at your own numbers. The data stays on your machine, and the proof below controls a real battery in a real house.
Island · a real Powerwall, controlled offline
The Proof
Island: offline control of a real Powerwall
The stakes go up when a dashboard changes numbers instead of just showing them. Island proves it can be done safely: a client build where the buttons move real electricity.
Private build for the client
- The job
- A friend needed to monitor and control a home Powerwall without depending on anyone's cloud. If the internet goes down, the battery still needs managing. Arguably more, not less.
- How it works
- The app talks to the battery over home Wi-Fi only. Nothing leaves the house. Real control only unlocks when the app has confirmed the hardware actually supports it, so it can never send a command the kit can't handle.
- The safety net
- The safety-critical parts are written twice, once in Rust and once in Python, and they check each other. Disagreement means the app refuses rather than guesses.
- How it shipped
- As a private, signed Android app installed straight onto the owner's phone, no app store involved and nothing to subscribe to.
Daily Drivers
The consoles I run my own life on
I use this stuff myself. My own books and my own community platform run on consoles I made, which is where the habits in the client work come from. Both are personal builds, shown honestly as such.
Gwerin
A self-hosted platform for off-grid living, seventeen modules from a swap marketplace to livestock records, in daily real-world use. One screen for a whole smallholding.
The Contents
What goes on one screen
The rule of thumb: if you check it every day, it belongs on the screen. If you copy it between two systems by hand, the console should do the copying.
- Money
- Today's takings against the month. The invoices that haven't been paid and how overdue they are. What's about to go out.
- Work
- The job list, who's on what, and what's stuck waiting on someone. The bookings coming in and the gaps in the calendar.
- Stock and kit
- What's about to run out. Tank levels, battery readings, sensor alerts, whatever your business physically runs on.
- Controls
- Not just numbers to look at. The two or three actions you take every day, right there, like Island's battery controls. Guarded so a mis-tap can't do damage.
What It Costs
Quoted per console
No two consoles hold the same things, so dashboards are quoted after I've seen the job. A full one sits in the App & Product Build tier on the main site, and a smaller console can come in under that band.
If you want the thinking on paper before committing to anything, start with the audit below. Half a day mapping what you check, chase, and copy between systems every week, and you get a written report of what belongs on one screen and what should be automated outright.
comes off the build if you go ahead
The same audit that starts the automation work, pointed at your dashboard problem: what you check every day, where it lives now, and what one screen would need to show.
- Every number you chase each week, mapped to its source
- A sketch of what belongs on the one screen
- An honest effort estimate and a quote with evidence behind it
- A written report you can act on with anyone
Timeline: one week
↗ Book the audit
Contact
Show me the spreadsheet
Tell me where your numbers live today, however messy. I'll come back with what a console would look like and what it's likely to cost, usually within a day.
Email: alex@alexevoy.devIf the mess is more about jobs than numbers, the automation page is probably where you want to start.