Built by an Engineer,
for Engineers

Arbiter exists because shipping software shouldn't require living in front of a terminal.

Mason

Founder & Engineer

I've spent the last 7+ years building software across startups and large corporations. I love the craft of engineering — but somewhere along the way, the ratio of building to shipping got out of balance.

I had too many projects and not enough hours in the day. Even with all the great AI tools out there (and I was paying for most of them), they still required me to sit down, prompt them, refine the output, iterate — over and over. As a husband and father, that time just isn't there.

I didn't need another AI assistant that waits for me. I needed something that works while I'm away.

That's why I built Arbiter. The idea is simple: front-load your thinking into well-written issues, then let Arbiter pick them up and do the work autonomously. When it's done, you review and merge. If something needs refinement, a few commands is all it takes.

I still build things the way I want to — I just spend less time sitting in front of a keyboard, and more time shipping.

What drives Arbiter

Local-first

Your code stays on your machine. No cloud middleman, no data leaving your control.

Time back

Automate the work that doesn't need you watching. Review when you're ready.

Engineer-first

Built as a CLI tool for developers, not a dashboard for managers.

Your stack

Works with the AI providers and models you already use — Claude, Ollama, Cursor, and more.

Ready to start shipping more?

Set up Arbiter in minutes and let it handle the backlog.

Get Started