White-label apps
Update all your apps with a single command.
Ship a branded Flutter app for each of your customers? Fix a bug once, run one CI job, and every brand’s app in the stores gets the fix on its next launch, without waiting for app store review.
One bug. Hundreds of store submissions.
A white-label app is published once per customer, each with its own name, icon and store listing. Whether you run a branded app for every gym, restaurant, school or bank on your platform, or build apps for clients as an agency, a fix in shared code used to mean a new version for every brand.
Before
- A build, an upload and a review for every brand
- Days to weeks before every brand has the fix
- Brands left on the broken version while they wait
After
- One fix in your shared Dart code
- One CI job patches every brand’s app
- Users get it on their next launch
Fix your customers’ apps without their store accounts.
When each brand is published under your customer’s own developer account, every store update waits on their credentials, their sign-off or their time. A patch goes from your CI to Shorebird, not through the App Store or Google Play, so you ship a fix without signing in to anyone’s store account or waiting on the customer.
New app versions, for a new icon or native code, still go out through each brand’s store account.
“Our job is to deliver value regardless of whether a gym owner has time to sign App Store documents. With Shorebird, we can do that.”
Set up once. Then every fix reaches every brand.
Connect each brand
Each app in the stores gets its own Shorebird app. One covers that brand’s Android and iOS builds.
$ shorebird init --display-name="Brand A"Let CI sign in
Your pipeline signs in with a key that doesn’t depend on any person. Service accounts are on every plan.
$ export SHOREBIRD_TOKEN=…Ship each brand to the stores
Build each brand’s release with Shorebird and upload it to that brand’s store listing, as you do today.
$ shorebird release --platforms=android,iosFix every brand at once
A fix to shared code is a loop over your apps, from one CI job.
$ shorebird patch --release-version=latest
Every brand, from one script.
This script from the docs patches every brand’s app for Android and iOS. It doesn’t stop at the first brand that fails: it patches the rest and lists the failures at the end, so one bad build never holds back the fleet.
Patch every app from one CI job#!/usr/bin/env bash
# Needs SHOREBIRD_TOKEN set to the service account’s key.
failed=()
for app in apps/*/; do
if ! (cd "$app" && shorebird patch --platforms=android,ios \
--release-version=latest --track=stable); then
failed+=("$app")
fi
done
if [ ${#failed[@]} -gt 0 ]; then
echo "Patching failed for: ${failed[*]}"
exit 1
fi
Works with the way you build brands today.
Shorebird gives every brand its own app however your project is laid out. Your Dart code doesn’t change.
One Flutter project per brand
For host apps generated from a template that share your Dart code as a package. Run shorebird init in each project; each gets its own shorebird.yaml. Works on Android, iOS, macOS, Windows and Linux.
$ cd apps/brand_a && shorebird patchOne project with a flavor per brand
shorebird init creates a Shorebird app for each flavor and lists them in shorebird.yaml. Pass --flavor to release and patch. Flavors work on Android, iOS and macOS.
$ shorebird patch --flavor=brand_aDecide what each brand gets, and when.
- Try a fix on a few brands first
- Patch your flagship and two or three other brands on a staging track, test them, then promote and patch the rest. Staging patches
- Roll out gradually
- Offer a patch to a share of a brand’s devices, such as 10%, and raise it as you gain confidence. Percentage rollouts
- Require approvalEnterprise
- Protect a brand’s production track and no patch reaches it until an admin or owner approves, whether it comes from the console, the CLI or CI. Protected tracks
- Freeze a brandEnterprise
- Block production changes for a period you set, such as a customer’s busiest weekend, for one app or all of them. Deployment freezes
- Roll back one brand
- Each brand has its own releases, tracks and rollbacks, so taking a patch back for one brand leaves the others alone.
- See each brand’s rollout
- Mission Control shows patch coverage and adoption for each app, so you can see which brands have the fix. Meet Mission Control
- One failure doesn’t stop the fleet
- The CI loop keeps going past a brand that fails and lists every one that did at the end. Split a large fleet across parallel jobs.
- Automatic fallback
- A patch that fails to load on a device falls back to the last version that worked.
- Only your patches run
- New releases are signed by default, so each brand’s app runs only patches signed for it.
Change anything your brands share in Dart.
Anything in Dart ships as a patch, to one brand or all of them. What the stores list for each brand, and native code, goes out in a new app version.
Ships as a patch
- Bug fixes in shared code, for every brand at once
- Features, screens and copy
- Brand colors, themes and settings defined in Dart
- Backend endpoints and configuration
Needs a new app version
- App name, icon and bundle ID
- Images, fonts and other assets in pubspec.yaml
- Native code and build files
- App permissions
PushPress · Software for gym owners
“We were manually clicking through 30 app builds at a time. With over 1,500 Branded Apps, that could take up to two weeks to finish between all the other work and distractions.”
Allan Wright, Senior Mobile Developer, PushPress
Read the PushPress story- 1,500+
- white-labeled apps maintained through Shorebird
- 3,600+
- releases and 100+ patches sent in 4 months
- 100+ days
- of release management time saved
Common questions

Built by the people who made Flutter
Shorebird was founded in 2023 by Eric Seidel, the creator of Flutter, and is backed by Accel.
About the teamDoes Shorebird support white-label apps?
Yes, out of the box. Give each brand's store app its own Shorebird app, then release and patch them all from one CI job. There's nothing extra to turn on, and every plan includes unlimited apps. The White Labeling guide walks through the setup.
Can several brands share one Shorebird app?
No. A patch is built against one release's build and installs only on it, and Shorebird matches patches to devices by app ID and release version. Separate apps also give each brand its own releases, tracks, rollbacks and insights. One Shorebird app covers a brand's Android and iOS builds, so 100 brands on both stores is 100 Shorebird apps.
Do I need flavors for white-labeling?
No. If each brand is its own Flutter project, run shorebird init in each one. If you use a flavor per brand, shorebird init creates an app for each flavor and you pass --flavor to release and patch. Flavors work on Android, iOS and macOS. See Apps with flavors.
Does each brand cost extra?
No. Every plan includes unlimited apps and releases. Plans are priced by patch installs a month, not by the number of apps, so adding a brand adds no fee of its own. See Pricing.
Can a patch change a brand's logo, icon or name?
Not the app's name, icon or bundle ID, and not images or fonts listed in pubspec.yaml: those need a new app version in the stores. Anything written in Dart can change in a patch, including brand colors, themes, copy, settings and features.
How do I test a fix before it reaches every brand?
Patch a few brands on a staging track first. Devices check the stable track by default, so their users don't get it. Test with shorebird preview --track=staging, promote the patches to stable in the console or with shorebird patches promote, then patch the remaining brands. See Staging patches.
Do I need my customers' store accounts to ship a fix?
No. A patch goes from your CI to Shorebird, not through the App Store or Google Play, so you don't sign in to a customer's App Store Connect or Play Console account, and they don't have to sign anything. A new app version, for example for a new icon or native code, still goes out through each brand's store account.
Can I require approval before a patch reaches a brand?
On Enterprise, yes. Protect a brand's production track and no patch reaches it until an admin or owner approves it; Shorebird's servers enforce this whether the patch comes from the console, the CLI or CI. Deployment freeze windows block production changes for a period you set, for one app or all of them. On every plan, a percentage rollout offers a patch to a share of a brand's devices first. See Protected tracks.
Can I roll back a patch for one brand only?
Yes. Each brand is its own Shorebird app, so you roll back its patch in the console without touching any other brand's.
Are code push updates to white-label apps allowed by the stores?
Code Push works within App Store and Google Play guidelines: each app's native shell goes through normal store review, and patches must not change the app's primary purpose (Apple Developer Program License Agreement section 3.3.1(B)). Your agreements with the stores still apply to each brand's app. See the store compliance FAQ.
How does CI sign in to patch every brand?
With a service account: create a key and store it in your CI's secrets as SHOREBIRD_TOKEN. Give it the Developer role if CI only releases and patches, or App Manager if it also runs shorebird init to create apps for new brands. Service accounts are on every plan.
How long does patching a large fleet take?
Each patch is a build, so the time grows with the number of brands. Split the apps across parallel CI jobs to shorten it. iOS patches need a macOS runner; on Linux, patch Android there and iOS from a macOS job.
Ship your first patch today.
Install the CLI, create a release and send a patch. Free for 5,000 patch installs a month.
Larger team? Talk to sales