Tools I'm building because I need them
Midnight Labs is consulting first. But between client work - usually after dark - I build small products to solve my own problems. Here's what's on the bench. No launch dates, no waitlists, no hype.
Midnight Monitor
buildingWatches your systems, services, and metrics and pings you the moment something crosses a line - a server falling over, a spike worth celebrating, or any threshold you set yourself. Good news or bad, you hear about it first.
- Custom alert rules
- Positive & negative triggers
- Notify anywhere
Midnight Dev Analytics
exploringTurns a team's commits, pull requests, reviews, comments, and activity into one honest overview - momentum and code quality at a glance, without becoming a surveillance tool.
- Commit & PR insight
- Review & comment signal
- Code-quality trends
Midnight AI Support
conceptA support agent that gets sharper with every ticket it handles - learning from each resolution so the answers it gives tomorrow are better than the ones it gave today.
- Learns from every ticket
- Improves as it solves
- Human handoff when needed
why build products at all?
The best work I've done has always been the same shape: a small problem, the freedom to ship, and the patience to build something useful before the slide deck dries.
My products start as tools I reach for during client work. If one turns out to be genuinely useful, I'll keep going. If it doesn't, it stays a happy little experiment. Either way, the consulting stays sharp.