Self-hosted, Mac-first build & release hub for Flutter. Refine your code. Forge your artifacts. Own your metal.
Caution
This project is in very early development. Most features don't work yet. The codebase is unstable and APIs will change without notice. I'm still figuring out the architecture and evaluating different approaches.
Do not use this for anything real. If you're interested in the concept, star/watch the repo and check back later.
Oore is a self-hosted, "Mac-first" CI/CD orchestration hub designed specifically for Flutter projects. It turns a Mac mini or Mac Studio into a private build machine that can:
- listen to GitHub/GitLab webhooks (or run builds manually),
- store per-app build configuration and signing material locally (encrypted / Keychain-backed),
- run builds and produce signed artifacts,
- publish to distribution targets when you choose (manual promotion),
- and provide a simple web UI where non-devs can browse and download builds.
The goal is to remove the "Apple signing/notarization" friction and the overhead of hosted CI, while keeping your code and credentials on hardware you control.
Note: The UI exists but most functionality is not implemented yet.
| Dashboard | Repositories |
|---|---|
 |
 |
| Builds | Settings |
|---|---|
 |
 |
# Build from source
cargo build --release
# Install as system service (macOS/Linux)
sudo ./target/release/oored install
# Configure
sudo nano /etc/oore/oore.env
# Start
sudo oored start
# Check status
oored statusSee the Service Management guide for detailed installation instructions.
| Guide | Description |
|---|---|
| Service Management | Install, configure, and manage oored as a system service |
| Configuration | Environment variables and configuration reference |
| CLI Reference | oore command-line interface |
| API Reference | REST API endpoints |
| Architecture | System design and technical decisions |
| GitHub Integration | GitHub App and webhook setup |
| GitLab Integration | GitLab OAuth and webhook setup |
┌─────────────────────────────────────────────────────────────┐
│ Oore Platform │
├─────────────────────────────────────────────────────────────┤
│ oore (CLI) ──▶ oored (server) ──▶ Build Executor │
│ │ │ │ │
│ │ ┌────┴────┐ ▼ │
│ ▼ ▼ ▼ Artifacts/Logs │
│ REST API SQLite Webhooks (/var/lib/oore) │
│ ▲ │
│ │ │
│ Next.js Dashboard (web/) │
└─────────────────────────────────────────────────────────────┘
Components:
- oore-core - Shared library (database, models, crypto, webhook handling)
- oore-server (
oored) - Axum HTTP server with service management - oore-cli (
oore) - Command-line client - web - Next.js dashboard (in development)
| Decision | Rationale |
|---|---|
| Run as root | Industry standard for system daemons (cloudflared, Homebrew services). Avoids macOS user/group complexity. |
| SQLite | Simple, portable, no separate database server. Sufficient for self-hosted use. |
| Async webhooks | Store immediately, process in background. GitHub requires <10s response. |
| ULID for IDs | Sortable by time, unique, URL-safe. Better than UUIDs for builds. |
| System service | LaunchDaemon (macOS) / systemd (Linux) for boot-time startup. |
See the Architecture guide for detailed rationale.
# Terminal 1: Run server
cargo run -p oore-server
# Terminal 2: Use CLI
cargo run -p oore-cli -- health
cargo run -p oore-cli -- repo list
# Terminal 3: Run dashboard
cd web && bun devIn industry, ore is raw, unrefined material—valuable, but unusable until processed.
- Your source code is the ore.
- Oore is the refinery that turns it into signed, distributable artifacts.
Pronounced like "ore," the spelling also nods to Apple's "Core" ecosystem and the Mac-first focus.
Very early development - evaluating architecture and approaches.
What exists (scaffolding only, not production-ready):
- GitHub App manifest flow
- GitLab OAuth integration
- Webhook ingestion and storage
- Repository/build database models
- Service management (install/start/stop)
- REST API and CLI basics
- Web dashboard UI (no real functionality)
What doesn't exist yet:
- Actual build execution - the core feature
- Code signing / Keychain integration
- Artifact storage and downloads
- TestFlight / App Store publishing
- Notifications (Slack, email)
- Multi-user / team support
The "done" items are mostly plumbing. The hard parts haven't started.
MIT License
Developed by Aryakumar Jha