Self-hosted Flutter CI/CD
for Mac
What It Does
Core capabilities for Flutter CI/CD on your hardware
Webhook receiver
Listens to GitHub and GitLab push/PR events
Build execution
Runs Flutter builds for iOS, Android, macOS, web
Keychain integration
Uses macOS Keychain for code signing credentials
Artifact storage
Stores IPAs, APKs, and build logs locally
REST API + CLI
Manage repos, trigger builds, check status
System service
Runs as launchd daemon, starts on boot
Why Self-Host?
Flutter teams building iOS apps need macOS for code signing. Cloud CI services require uploading certificates and provisioning profiles. Oore runs on hardware you control—a Mac mini or Mac Studio—so signing credentials never leave your machine.
Credentials stay local
Signing certificates and provisioning profiles never leave your machine. No uploading to third-party services.
No per-build costs
Fixed hardware investment. Run as many builds as you want without pay-per-minute charges.
No queue times
Dedicated hardware means builds start immediately. No waiting for shared CI resources.
Quick Start
Get Oore running on your Mac in under a minute
# Clone the repository
git clone https://github.com/devaryakjha/oore.build
cd oore
# Build
cargo build --release
# Install as system service sudo ./target/release/oored install
# Start the service sudo oored start
# Check status
oored status
● oored is running (pid 1234) # View logs
oored logs -f Project Status
Oore is in early development. Here's what's working and what's next.
Implemented
- GitHub/GitLab webhook ingestion and verification
- Repository and build management (API + CLI)
- Service management (install/start/stop/logs)
- Background webhook processing
In Progress
- Build execution pipelines
- Artifact storage and retrieval
- Code signing integration
- Web dashboard