Build infrastructure
Oore CI
Mobile releases, on your own terms.
WHY I BUILT IT
From my own release workflow.
I wanted to run Flutter mobile CI on my own Mac, handle signing, and share internal builds without stitching together too many tools. Oore started there.
01 / The dashboard
A place to start the day.
The dashboard brings running builds, waiting jobs, and runner availability together. Problems surface alongside the work: here, a source that cannot be checked out needs attention before its build can start.
Real product UI · Demo data · Tap to enlarge
02 / The build queue
From a commit to a build.
Each run keeps its project, branch, commit, and trigger together. Filter by project or status to find a release, or see what is still queued. GitHub and GitLab webhooks can start builds when code changes.
Real product UI · Demo data · Tap to enlarge
AFTER THE BUILD
Share what you made.
Oore also handles signing workflows and artifact delivery through signed, time-limited links. Android, iOS, and macOS Flutter builds run on your own macOS infrastructure.
THE TRADEOFF
Your machine, your upkeep.
Self-hosting means keeping the build machine and toolchain running yourself. Oore is still in public alpha, with room to improve through real use and feedback.