Welcome back

Opening shared build

Preparing your Mach workspace…

Preparing your secure download…

Login
Start
New: first-class Flutter delivery on iOS, Android, and web

Mach CLI for React Native, Flutter & Expo CI/CD

The Mach CLI lets you build, sign, test, and release iOS, Android, and web apps from one workflow. Vanilla React Native, Flutter, and Expo React Native teams get cloud builds, secure app signing, live logs, artifacts, and store delivery.
Start building free
See how it works
Read the documentation
No credit card
Setup in 5 min
Free tier forever
FIRST-CLASS FRAMEWORK SUPPORT
Vanilla React Native
Flutter
Expo React Native
BUILDS FOR
iOS
Android
Flutter web
Flutter staging build
staging · signed Android artifact
Running
Spin up build environment
done
Activate pinned Flutter SDK
done
Fetch Dart dependencies
done
Inject signing credentials
ready
Compile staging APK
running
Framework
Flutter
Platform
Android
Secrets
Locked
~/myapp $ mach build android --profile staging
Flutter SDK... pinned & verified
assembleStagingRelease... running
Dashboard: https://getmach.dev/build/abc123
< 5 min
Typical project setup
4-in-1
Build · submit · signing · test
20
Free builds every month
37%
Lower on a 60-build EAS mix
Features

Mobile app CI/CD and release management in one place

Mach keeps the mobile release path together instead of scattering builds, store upload, credentials, and test evidence across separate tools.
Build
Artifact
Submit
Cloud builds that stay connected to the rest of release
Run iOS, Android, and Flutter web builds, keep signing assets secure, download artifacts, submit mobile releases to stores, and attach Maestro validation without losing context.
mach build --platform ios
Build runs in cloud
Artifact generated
APK / AAB / IPA ready
mach submit --latest
Store upload tracked
Credentials
Manage certificates, provisioning profiles, keystores, and service credentials from one secure place.
Maestro Tests
Run Maestro flows against your artifacts and keep test results attached to the build history.
Live Dashboard
Follow logs, artifacts, submissions, credentials, and test runs without digging through CI output.
Powerful CLI
Build, submit, manage credentials, and start tests from commands that fit local or CI workflows.
Device Hub
Register devices for testing and push installable builds directly to connected phones.
Store Submissions
Submit the latest successful build to App Store Connect or Google Play, then track status beside the build.
Flutter support

Flutter CI/CD for iOS, Android, and web

Use the same CLI and dashboard for Flutter mobile and web builds, signing, versioning, audits, push, deep links, Shorebird OTA, release symbols, artifacts, and mobile store submissions.
Detected and pinned
mach init recognizes Flutter apps and Dart workspaces, then pins the installed stable SDK for repeatable builds.
Profiles without limits
Use any profile names you need, with shared or platform-specific flavors, Dart targets, modes, and environments.
Mobile and web artifacts
Build signed APK, AAB, and IPA artifacts plus deployable Flutter web bundles, with retained release symbols when enabled.
Push, links, and OTA
Wire Mach Push and verified deep links, then ship Dart patches through your own Shorebird account and token.
Profile-driven Flutter builds
Your names, environments, flavors, and targets
Ready
staging environment: staging distribution: internal flavor: staging target: lib/main_staging.dart
APK
AAB
IPA
mach build android --profile staging
Invalid flavors and targets stop before a cloud runner is allocated.
Read the Flutter setup guide
Security
Security isn't a feature. It's the foundation.
Your signing keys, secrets, and credentials are protected end-to-end — encrypted at rest, never exposed during builds.
Secrets Encrypted at Rest
All secrets and credentials are stored encrypted. They are never accessible outside of a build.
Expiring Download Links
Build artifacts are served via short-lived links that expire automatically — no permanent public URLs.
Secure Authentication
Every API request is authenticated with short-lived tokens. No long-lived credentials are accepted.
Zero Credential Exposure
Your signing keys are never accessible to the build environment — injected just-in-time and immediately discarded.
Encrypted Vault
Signing keys and provisioning profiles are stored in an encrypted vault, decrypted only when a build runs.
How It Works
Get from install to build, submit, and test
Four steps from zero to a cloud build, then keep the related submissions, credentials, and Maestro results in the dashboard.
Read the setup guide
1
Install the CLI
Get started with a single npm command.
$ npm install -g @radhya/mach
2
Login & link your project
Authenticate and connect your React Native, Flutter, or Expo React Native project.
$ mach login && mach link
3
Run a build
Kick off a cloud build for any platform.
$ mach build --platform ios
4
Monitor in dashboard
View builds, submissions, Maestro test results, artifacts, and credentials from the web.
Dashboard handoff ready
Stack fit
Built for the mobile release path, not generic CI
Mach keeps vanilla React Native, Flutter, and Expo React Native teams close to the work they repeat every week: build the app, sign it safely, submit it, and validate it with Maestro.
4 surfaces
Build, submit, creds, tests
1 CLI
Local and CI friendly
No sprawl
Release context stays together
Release stack
Vanilla React Native, Flutter, or Expo React Native to a store-ready artifact
Ready
Build
iOS / Android
Sign
Credentials
Submit
Stores
Validate
Maestro
Vanilla React Native
Flutter
Expo React Native
Cloud builds
Store submissions
Credentials
Maestro tests
Why Mach?
A complete mobile delivery workspace
Mach brings builds, secrets, OTA releases, device installs, submissions, test runs, and delivery status into one workspace.
Build, ship, and update
Managed builders, OTA channels, and store delivery status stay tied to the same release record.
Test on connected devices
Use Install Hub to discover a local test device and push an installable build from the dashboard.
One secure team workspace
Keep credentials and secrets protected while managing member roles and project ownership.
Feature
Mach
Manual CI
React Native, Flutter & Expo React Native
iOS, Android & web builds
Managed builds & live logs
Credentials, secrets & signing
Connected-device installs
OTA releases & rollback
Store submissions, push & tests
Team roles & read-only MCP access
Loved by teams
Don't take our word for it
"Mach cut our CI costs by 60% overnight. We were paying for EAS seats we barely used. Now we pay per build."
AM
Arjun Mehta
CTO, FinTrack
"The security model is what sold us. Our signing keys never touch the build runner — that's a huge deal for compliance."
SK
Sarah Kim
Lead Engineer, Shopify Partner
"One command and the build is running in the cloud. We haven't touched Xcode in weeks."
PN
Priya Nair
Mobile Architect, HealthApp
Pricing
Start free. Scale only when builds grow.
Free monthly builds are included. After that, pay per build run beyond the free tier with no seat tax.
Free
Free plan
$0
/ month
For personal apps, test projects, and exploring the complete delivery workflow.
20
free builds every month
10 Android builds each month
10 iOS builds each month
1 concurrent build slot
Dashboard, CLI, and live build logs
OTA, device installs, push, submissions, and teams
Start free
POPULAR
Pay as you go
Pay only for build usage
Android
$0.70
per build
iOS
$1.20
per build
Maestro
$0.40
first 15 min
Maestro then $0.20 per additional 10 minutes.
Prepaid wallet billing: only add credit when you are ready to run paid builds or managed tests.
Continue after the free allowance with straightforward usage pricing and capacity you can add when needed.
Build beyond the free monthly allowance
Wallet pricing at the rates shown above
1 concurrent slot included
Add capacity for +$50 per slot / month
Release workspace: OTA, devices, push, and store delivery
Managed Maestro tests billed by runner time
Start building
What 60 builds costs
30 Android + 30 iOS in one month
EAS Build
$90/mo
Bitrise Starter
$99/mo
Mach
LOWEST
$57/mo
About 37% lower than EAS Build for this mix
Illustrative USD comparison for 30 Android and 30 iOS builds using the prices represented in this calculator. Taxes, credits, and custom plans are excluded. Checked August 2026.
FAQ

Mobile app CI/CD questions, answered

Ten practical answers on setup, pricing, security, and the full mobile delivery workflow.
Frameworks
Which frameworks does Mach support?
Mach supports Vanilla React Native, Flutter, and Expo React Native projects. Each framework keeps the delivery workflow it needs while builds, credentials, release activity, and history remain in one workspace.
Workspace
What is included in a Mach workspace?
Mach brings together cloud builds, live logs, artifacts, credentials and secrets, OTA releases, connected-device installs, push, store delivery, Maestro testing, project roles, and release history.
Platforms
Can Mach build iOS, Android, and web apps?
Mach runs managed iOS and Android builds for supported projects, and supports Flutter web bundles. The selected framework and build profile determine the targets available for each project.
Getting started
How do I move an existing app to Mach?
Install the CLI, sign in, then initialise or link the project and review the generated mach.config.json. Keep that configuration in version control so your team and CI use the same build profiles.
Pricing
How does Mach pricing work?
The free plan includes 10 Android and 10 iOS builds each month. After that, Android builds are $0.70, iOS builds are $1.20, and managed Maestro testing is $0.40 for the first 15 minutes plus $0.20 for each additional 10-minute block.
OTA delivery
When should I use an OTA release instead of a new build?
Use OTA for compatible JavaScript, styling, and asset changes. Native code, permissions, SDK, or runtime changes still require a new binary; Mach uses channels and runtime compatibility to protect the installed app.
Device installs
Can I install a build directly on a test device?
Yes. Install Hub discovers compatible devices through the local Mach agent and lets you push an installable artifact from the dashboard, without passing files around manually.
Quality & stores
How do testing and store submissions work?
Maestro test runs and store submissions stay attached to the build that produced the artifact, creating a traceable release record. Managed Maestro runs require a Pay as you go wallet.
Security
How does Mach protect signing credentials and secrets?
Mach stores credentials and secrets encrypted at rest, scopes them to the requested build, and keeps sensitive values out of normal dashboard views and build logs.
Teams & AI
Can my team and AI tools access Mach safely?
Project roles control who can work in each workspace, and ownership can be transferred deliberately. Connected MCP apps receive read-only access to allowed project, build, OTA, test, and usage data—not secrets or publishing controls.
Ready to ship faster?
Start building in the cloud today. No credit card required. Free tier forever.
Get started for free
Mach
Cloud builds, submissions, credentials, and Maestro tests for React Native, Flutter, and Expo React Native teams.
© 2026 Radhya Softlabs
Built for mobile release teams
Public documentation for every Mach workflow