Oore documentation

Oore is for Flutter teams that want builds and artifacts to stay on hardware they control. Start on one Mac, build a debug APK from a local Git repository, and expand only when your team needs more.

Start on one Mac

Build your first debug APK

Install Oore in Local Only, create a project from a repository on your Mac, and run Quick Debug APK.

The default install includes oored, the oore operator CLI, a local web client, a managed Direct macOS runner, and automatic local artifact storage.

Oore dashboard showing system status, active builds, and recent build activity

After your first build

Build and distribute

Create projects and pipelines, connect Sources, sign builds, and deliver artifacts.

Team and access

Invite people, manage access, and configure External Access.

Operate Oore

Choose a deployment, manage runners and storage, update, back up, and troubleshoot.

Understand Oore

Learn how builds, runners, signing, artifacts, and instance security fit together.

Reference

Look up commands, configuration, states, roles, and generated API operations.

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.