Oore documentation
Build, sign, and ship Flutter apps from Macs you control.
Oore builds Flutter apps on your own Macs and delivers them to testers, Google Play, and the App Store. Builds, signing keys, and artifacts stay on hardware you operate. Pick the goal closest to yours.
Start from nothing
Install Oore on one Mac
Check the Mac, install Oore in Local Only, and open the web UI.
Ship an Android app to testers
Build a debug APK, sign a release, and send it to testers on Google Play.
Ship an iOS app to TestFlight
Build for iOS, sign with an App Store Connect key, and deliver through TestFlight and the App Store.
Decide which setup you need
Compare Local Only and External Access, local and connected repositories, and one Mac against several.
Do one thing with an existing install
Build on every push and check pull requests
Connect GitHub or GitLab, then let pushes and pull requests start builds.
Keep the pipeline in the repository
Move a pipeline from the UI into .oore.yaml so it changes with the code.
Let the team sign in
Turn on External Access, then invite people and give them project roles.
Keep Oore running
Add runners, upgrade, back up, and troubleshoot.
Look something up
- How Oore works explains the architecture, build lifecycle, repository trust, signing, and artifact delivery.
- Reference lists every command, configuration field, state, role, error code, and API operation.
Hosted UI
ci.oore.build is an optional browser client for an Oore backend that is
already reachable over HTTPS. It does not host an Oore instance and is not
part of the one-Mac Local Only path.