FLUTTER CI/CD

Repeatable Flutter builds across mobile and web

Mach gives Flutter teams one profile-driven workflow for signed IPA, AAB, APK, and web artifacts, while keeping flavors, targets, credentials, test runs, and release delivery visible.

Start building free

Read the Flutter setup guide

Flutter

iOS · Android · web

Ready

~/app $ mach build --platform android --profile staging

Validating project configuration...

Configuration verified. Starting managed build.

Source

Your repository

Signing

Encrypted

Delivery

Traceable

DELIVERY WORKSPACE

Everything around the build stays connected

Mach keeps source validation, signing, artifacts, tests, and store delivery in one release record.

Pinned Flutter SDK

Use the validated stable SDK selected for the project so builders produce repeatable results.

Flavors and targets

Keep shared or platform-specific flavors, Dart targets, modes, and environments inside named profiles.

Mobile artifacts

Create signed APK, AAB, and IPA artifacts with versioning and release metadata attached.

Flutter web bundles

Produce deployable web output from the same linked project and profile model.

Release symbols

Retain release symbols when configured so production troubleshooting has the required build evidence.

Push, links, and OTA

Configure push and verified links, then connect a project-owned Shorebird account for eligible Dart patch delivery.

REPEATABLE WORKFLOW

From existing app to managed release

Configuration lives with the repository, so local development and CI use the same profiles.

Install Mach

Add the CLI to the workstation or CI environment that owns the repository.

npm i -g @radhya/mach

Detect the project

Link the Flutter workspace and confirm the selected app directory and SDK.

mach init

Model profiles

Declare flavors, Dart targets, build modes, environments, and mobile identifiers.

mach config --profile staging

Build a target

Run a signed mobile build or web bundle and keep its delivery trail in the dashboard.

mach build --platform android

COMMON QUESTIONS

Flutter delivery answers

Which Flutter targets can Mach build?

Mach supports managed Flutter builds for iOS and Android plus Flutter web bundles. Available artifact types depend on the selected platform and profile.

Can different Flutter flavors use different Dart entrypoints?

Yes. Profiles can declare a flavor, Dart target, build mode, and environment for each release workflow.

Does Mach replace Shorebird for Flutter OTA?

No. Eligible Dart patches use your own Shorebird account and token. Mach connects that delivery activity to the wider project workflow.

Are signing credentials stored in the Flutter repository?

They do not need to be. Mach stores managed credentials separately and makes them available only to the requested build workflow.

Ship your next Flutter build with Mach

Start with the free monthly allowance. No credit card is required.

Create a workspace