Free to build.
Paid to stop being surprised.

No, and you never will. Publishing, promoting, rolling back, and code-signing updates are all in the free tier, and the update server is yours to run. We are not planning to host update delivery — that would be a separate service with its own storage and bandwidth, rather than a tier of this one. If you would rather not run it, several projects host Expo-protocol updates and we would sooner point you at them than half-build it.

Everything required to build, sign, submit, and update, with no account. leas creds will tell you what is about to expire when you run it, and you can schedule that yourself. Pro is the part that keeps watch while you are not there: email and Slack before a credential lapses, and a dashboard that still has your history when the laptop is shut. Team and Enterprise are roadmap.

Yes, from your account page, at any time. Cancellation stops the next charge. The period you have already paid for runs to its end, and we do not refund it. Building, signing, and submitting do not depend on the subscription, so they continue either way. The terms say the same thing.

No, and there is no code path that would let us. Your certificate, provisioning profile, keystore, and API keys live on your machine and in your own repository secrets. The hosted dashboard receives metadata and nothing else: a credential name, an expiry date, and a public certificate fingerprint. Never key material, never a password — there is no endpoint that accepts it, and anything else sent to one is discarded before it is stored.

The engine is MIT licensed. That licence is irrevocable for the code already published, so the version you have today stays yours whatever happens next. Pro sells the hosted convenience layer — a dashboard that outlives your laptop, and alerts before a credential lapses. It has never sold, and will never sell, the ability to build and ship.

On machines you rent, under your own account — GitHub Actions by default. leas build --cloud dispatches a workflow in your repository whose body is the same engine you run locally. We are not in that path, which is why there is no per-minute build charge.

Not quite. Expo's own documentation for local builds notes that it requires eas login or an EXPO_TOKEN, and that it still communicates with Expo servers to confirm the project exists and to download managed credentials. leas has no account to log in to and no server to ask.

Apple's macOS licence forbids running macOS on non-Apple machines, so every iOS build in the world happens on somebody's Mac. leas is honest about it: use the Mac on your desk, or rent one by the minute. What it removes is the requirement that the Mac belong to a vendor who also holds your certificate.

Yes, and the exit is cheap by design. Your configuration is a leas.json in your repository, your workflows are ordinary GitHub Actions files, and your credentials never left your control.