a web UI for fastlane,
on your own machine
A browser interface for the lanes you already have, running on hardware you own. Pick a lane, click run, watch the output stream, download the artifact. It replaces neither fastlane nor your Fastfile — it drives them.
Runs on macOS and Linux. iOS builds need a Mac, as they always have; Android builds do not, so put it wherever it makes sense.
$ laneyard --why
- you keep the keys
- Signing certificates, keystores, provisioning profiles, store credentials — everything needed to publish under your name — stays on your machine. A hosted CI is a third party holding all of it.
- minutes stop existing
- Hardware you already own costs less than a year of most CI plans, and never bills by the second. Long builds stop being a budget decision.
- it is just fastlane
- No new DSL, no YAML dialect to learn, no vendor config to port. Laneyard reads the Fastfile you already have and asks your fastlane what it can do.
$ laneyard add
Run it inside a project that already uses fastlane. It reads what is there and writes the configuration for you.
$ cd ~/code/your-project $ laneyard add Project “your-project” added to ~/.laneyard/config.yml repo git@github.com:you/your-project.git (main) fastlane fastlane runtime bundle artifacts **/*.ipa, **/*.app.dSYM.zip
Then open the browser. Your lanes are listed, because Laneyard asked your project's own fastlane for them — plugins included.
$ laneyard --compare
| Laneyard | Hosted CI | Self-hosted runner | |
|---|---|---|---|
| who holds your signing keys | you | the vendor | you |
| cost per build | electricity | per minute | electricity |
| setup | one command | a signup form | a weekend |
| works offline | yes | no | yes |
| build queue across a team | planned | yes | yes |
| runs on pull requests | planned | yes | yes |
If your team needs parallel builds across a fleet today, use something else — and come back later; the queue is next on the list. Laneyard is for one machine you control.
$ laneyard --price
[00:00:00]: computing invoice [00:00:00]: seats 0 [00:00:00]: build minutes unmetered [00:00:00]: concurrency fee 0.00 [00:00:00]: ✓ total 0.00 — self-hosting is free forever
Self-hosting is free forever, and the source is MIT licensed. Not a trial, not a tier that expires: you run it on your own machine, so there is nothing of ours to bill you for.
A paid hosted option may follow later, for people who would rather not keep a machine running — the way Coolify does it. It would never take anything away from the self-hosted version, which stays free and open. Saying so now seems better than discovering it in a changelog.
$ laneyard --roadmap
Read the markers the way the tool does: ✓ shipped, ▸ being built now, ○ planned. Nothing on this list is a refusal — it is an order of work.
- ✓ declare a project, clone it, list its lanes, run one, watch it live, download the artifact
- ✓ configuration entirely in files you can version and back up
- ✓ adopt an existing fastlane project with one command
- ✓ encrypted secret vault and log redaction
- ▸ build queue, cancellation, timeouts
- ○ a checklist that gets a project running unattended
- ○ Fastfile editor in the browser
- ○ git-triggered and scheduled builds
Early, and saying so. If one of the unshipped lines is what would make Laneyard useful to you, the issue tracker is the place to say which — it is how the order gets decided.