DocsSign inGet started
The engine is free forever · Pro is live

Free to build.
Paid to stop being surprised.

The engine is MIT licensed and runs on your hardware, so building and shipping costs nothing and always will. Pro adds the hosted half — a dashboard that outlives your laptop, and a warning before a certificate lapses. Team and Enterprise are still roadmap, and what is not built is listed below rather than glossed over.

Available now
Open source
Everything needed to build, sign, submit, and update your app.
$0forever
MIT licensed · available now
Start building
Available today
  • Unlimited builds on your own machine
  • Cloud builds on your own GitHub Actions runners
  • Submit to the App Store and Google Play
  • Over-the-air updates, self-hosted
  • leas doctor — preflight every credential in seconds
  • leas creds — expiry check you can run or schedule
  • Setup wizard, generated workflows and secrets script
  • Local dashboard with live build status
  • No account. No build minutes. No seat count.
Available now
Pro
The watching. For when a laptop being closed should not mean nobody is minding the release.
$19/ month
Cancel any time · 30-day refund
Upgrade to Pro
Available today
  • Everything in Open source
  • Credential expiry alerts to Slack, before anything lapses
  • Hosted dashboard — history outlives your laptop
  • Build history across machines and teammates
  • Sign in with GitHub; no new password anywhere
  • Email alerts — the moment our sending domain verifies
Planned
Team
More than one person with the keys, and someone who asks who shipped what.
$99/ month
Planned · up to 10 seats
Tell us what you need
Planned
  • Everything in Pro
  • Release audit trail — who shipped which commit, when
  • Shared credential inventory across apps
  • Role-based access, no key sharing
  • SSO
Planned
Enterprise
Procurement is involved and the answer to "who holds our keys" matters.
Custom
Planned · scoped per customer
Start a conversation
Planned
  • Everything in Team
  • Self-host the control plane in your own cloud
  • SCIM provisioning
  • Security review and DPA
  • Named support contact

What is not built yet

The free tier and Pro both work today. The following does not, and we would rather you read it here than discover it after paying:

  • Email delivery for expiry alerts — Slack works today, email needs our sending domain
  • The release audit trail, role-based access, and SSO (Team)
  • Organisations and shared team accounts (Team)
  • Self-hosting the control plane (Enterprise)

Pro is fully refundable for 30 days, no conditions, so the one gap above is not a risk you are carrying. Team and Enterprise take no payment at all yet.

Over-the-air updates are free and self-hosted, on every tier. We are not planning to host update delivery for you: it would be a separate service with its own storage and bandwidth, and it is not what the paid tiers are for.

Every line

Full comparison

The first two columns exist today. Team and Enterprise are the shape of the roadmap rather than a menu — read them as what we intend to build, and tell us if we have the order wrong.

Building and shipping
 Open sourceavailable nowProavailable nowTeamplannedEnterpriseplanned
Local builds, iOS and AndroidUnlimitedUnlimitedUnlimitedUnlimited
Cloud builds on your own runnersUnlimitedUnlimitedUnlimitedUnlimited
Build minutes billed by leasNoneNoneNoneNone
Submit to App Store and Play••••
leas doctor preflight••••
Setup wizard••••
Over-the-air updates
 Open sourceavailable nowProavailable nowTeamplannedEnterpriseplanned
Publish, promote, roll back••••
Self-host the update server••••
Hosted update deliveryNot plannedNot plannedNot plannedNot planned
Update code signing••••
Watching
 Open sourceavailable nowProavailable nowTeamplannedEnterpriseplanned
Local dashboard••••
Hosted dashboard—•••
Credential expiry checkleas credsleas credsleas credsleas creds
Scheduled expiry watchYour CI, weeklyYour CI, weeklyYour CI, weeklyYour CI, weekly
Expiry alerts to Slack—•••
Expiry alerts by email—Pending domainPending domainPending domain
Build history retentionLocal, unlimited12 monthsPlannedPlanned
Release audit trail——PlannedPlanned
Team and governance
 Open sourceavailable nowProavailable nowTeamplannedEnterpriseplanned
SeatsUnlimited1PlannedPlanned
ProjectsUnlimitedUnlimitedPlannedPlanned
Role-based access——PlannedPlanned
SSO and SCIM——PlannedPlanned
Self-hosted control plane———Planned
Security review and DPA———Planned
Support
 Open sourceavailable nowProavailable nowTeamplannedEnterpriseplanned
Documentation and issues••••
Email supportBest effort•PlannedPlanned
Response target—Best effortPlannedPlanned
Questions

Pricing, plainly

Do I need a paid plan for over-the-air updates?
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.
What can I actually use today?
The whole free tier, and all of Pro except email alerts. Building, signing, submitting to both stores, over-the-air updates, the setup wizard, leas doctor and leas creds are MIT licensed and run on your own hardware. Pro adds the hosted dashboard, build history across machines, and expiry alerts to Slack. Email alerts are the one thing still waiting on our sending domain — it is listed as pending on the plan rather than hidden. Team and Enterprise are roadmap.
What happens if I pay and something does not work?
Ask and we refund it, in full, within 30 days, with no conditions — that is in the terms, not just here. Pro is new and the one known gap is email alerts, which is stated on the plan itself. If you hit anything else, tell us and we will either fix it quickly or give you your money back.
Do you ever see my signing keys?
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. If a hosted dashboard arrives, what it receives is metadata: a credential name, an expiry date, and a public certificate fingerprint. Never key material, never a password.
Is this really free, or free until you have enough users?
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. Paid plans, if they arrive, will sell the hosted convenience layer — never the ability to build and ship.
Where do cloud builds actually run?
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.
Isn’t eas build --local the same thing?
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.
Why is iOS still tied to Apple hardware?
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.
Can I move off it later?
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.

Start free. Upgrade when you want the watching.

No card and no account to build and ship — that part is yours regardless. Pro is $19, cancellable any time, refundable for 30 days.

Set it up in 10 minutesRead the manual