AMOS
AMOS is the operations hub Aspen’s asset team uses every day to run a fleet of solar sites from one place. It started as a six-figure outsourcing proposal; I built a prototype in a few days, made the case to bring it in-house, and took ownership of the product decisions, design, engineering, and launch. It has been in daily production use since.
- Role
- Solo Founder + Lead Engineer
- Period
- 2024 to present
- Status
- Production
How the system fits together.
The calls that shaped it.
- 01
Vendor proposal → a product I own
I took it from an outside vendor’s six-figure proposal to a product I own end to end. The biggest growth wasn’t technical — it was learning what to build, what to cut, and what “done” really means.
- 02
One calm place to work
Data that used to be scattered across monitoring platforms and spreadsheets now lands in a single, fast interface — so the team spends its time on decisions instead of hunting for information.
- 03
Access control admins own
Different roles see and do different things, and admins manage that themselves — no engineer in the loop to change who can do what. Getting that boundary right matters more than any one feature.
- 04
Dependable by default
The team leans on it daily, so everyone sees live updates in real time, automated tests catch regressions before users do, and it stays fast as the workload grows.
- 05
ML in the workflow
Forecasting site output and flagging equipment likely to fail in the next couple of weeks — so the team can act before something breaks, not after.
The interesting work isn't the stack. It's the boundaries.