Can I keep Bitrise CI and use AppForShare?

Yes. Add a Script step with the AppForShare CLI after your build step (an AppForShare step for the step library is in review). Bitrise keeps building, testers install from AppForShare.

Is AppForShare a CI like Bitrise?

No. It does not run builds on its own machines. It can set up builds on your own GitHub Actions (Pro and Team) and takes uploads from any CI.

Do testers need an account?

No, on either for public links. On AppForShare iPhone testers can also send their device for registration without any account.

How is pricing different?

Bitrise Release Management Standard is listed at $250 per app per month billed yearly. AppForShare Pro is $12 and Team $39 per month per workspace, not per app.

Does AppForShare do staged rollouts?

Google Play production rollouts (set %, raise, halt, resume, complete) on Team and App Store phased release controls on Pro and Team, each done by a person.

Does AppForShare have CodePush?

No. It shares whole builds; there is no SDK.

Is there an MCP server?

Yes, hosted with OAuth sign in (Pro and Team). Bitrise has one too.

AppForShare Upload a build

Keep Bitrise CI, share builds and ship releases with AppForShare

Bitrise is a mobile CI: hosted macOS and Linux machines run the Workflows in your bitrise.yml, with hundreds of Steps in its public step library. Next to it sits Release Management, which works with any CI and adds install pages, tester groups, TestFlight and Google Play releases, approvals and staged rollouts. As listed on November 4, 2026, Release Management Basic is free with an existing Bitrise plan, and Standard costs $250 per app per month billed yearly ($280 monthly).

AppForShare is not a CI and does not run builds on its own machines. It is the part after the build: install links testers open without an account, iPhone device setup, feedback, a store readiness check on every build and the App Store and Google Play steps. You can keep Bitrise CI and add AppForShare with one Script step after your build step. An AppForShare step for the Bitrise step library is in review; until it is listed, the Script step does the same.

Pick AppForShare if

You want a flat price per workspace (Pro $12, Team $39 a month with 5 seats) instead of a price per connected app.
Your testers and clients should install from a link with no account, in their own language (13 install page languages), with install help when an iPhone build will not install.
You want iPhone testers to send their device without any account: the free UDID finder and Remember this device on every plan, an onboarding link per iOS project and one click registration on Apple on Pro.
You want tester feedback with screenshots from the install page or from inside the test build through a link, with no SDK.
You want every build checked against current App Store and Google Play rules before it reaches testers, with a fix per issue.
You want the App Store and Google Play listing editor with AI translation, a reviews inbox with AI reply drafts and an App Store review checklist, next to the builds.
You deliver apps to clients and want a client portal with signed sign offs.

Pick Bitrise if

You need a CI with hosted Macs. AppForShare does not build; at most it sets up builds on your own GitHub Actions.
You want one vendor for builds and releases, with a release object per version, named approval tasks and release presets.
You want Google Play rollouts raised automatically over 7 days. On AppForShare an Admin changes the rollout by hand.
You ship CodePush updates for React Native or Expo. AppForShare shares whole builds only.
You need SSO, an SLA, self hosted or dedicated machines.
Free 2 GB artifacts kept 150 days on Release Management Basic are all you need. Our Free plan takes 150 MB with 7 day links.

Side by side

What it is: AppForShare
Test build sharing and store release steps for builds made by any CI. Not a CI.; Bitrise
A mobile CI with hosted macOS and Linux machines, plus Release Management that works with any CI
Price: AppForShare
Free, Pro $12/month with a 7 day free trial, Team $39/month (5 seats). Yearly = 10 months. Lower regional prices in many countries.; Bitrise
CI: Hobby free (1 member, 1 private app), Starter $89/month billed yearly or $99 monthly, Pro $200/month yearly or $218 monthly, Enterprise by quote
Release Management price: AppForShare
No per app price: Pro and Team cover every app in the workspace; Bitrise
Basic free with an existing Bitrise plan; Standard $250 per app per month billed yearly, $280 monthly, volume discounts
Largest file: AppForShare
50 MB without an account, 150 MB Free, 2 GB Pro, 4 GB Team; Bitrise
2 GB per artifact on Release Management Basic
Retention: AppForShare
3 days without an account, 7 days Free, as long as you subscribe on Pro and Team; Bitrise
150 days on Basic, 365 days on Standard; 1,000 artifacts per app on Basic
Testers: AppForShare
Open the link and install, no extra app. Channel links that always open the newest build (Pro and Team); tester groups, install status and reminders (Team).; Bitrise
Public install page with QR code; access links with their own expiry or none and an optional access code; external tester groups by email (since July 2026)
Tester accounts: AppForShare
Never needed. Private projects for invited testers use an emailed link (Team).; Bitrise
Not needed for public install pages and external tester groups; the private install page needs a Bitrise login
iOS devices: AppForShare
Free UDID finder built in, saves devices to your account, imports UDID lists. Pro adds an onboarding link per app and one click registration on Apple; Team can register, remake the profile and start the build hands free; Bitrise
Devices registered from a Bitrise user profile or by UDID by hand, added on Apple by its signing steps during a build. A way for testers without a Bitrise account to send a UDID was not found in its docs.
Install page languages: AppForShare
13 languages incl. Hindi, Urdu, Bengali, Indonesian, Spanish, Arabic, Chinese, Portuguese (Brazil), French, Turkish, Vietnamese and Russian, picked from the phone; Bitrise
Other languages than English not found in its docs
Install help: AppForShare
Install pages say why a build will not install (iOS too old, iPad only, profile ended, App Store signed) and list the usual fixes (every plan); Bitrise
Not found in its docs
Tester feedback: AppForShare
From the install page and from inside the test build through a link, with screenshots; no SDK (every plan with an account). Send to Linear or Jira (Pro and Team).; Bitrise
"What to test" text up to 4000 characters on the build page; feedback from the install page not found in its docs
Store readiness check: AppForShare
Every account build checked against current App Store and Google Play rules, with a fix per issue (Free and up); Bitrise
Not found in the Release Management docs
App Store review: AppForShare
Checklist before sending (build, export compliance, review contact, texts, screenshots); an Admin sends, cancels, releases and pauses, resumes or completes a 7 day phased release (Pro and Team); Bitrise
Release stages: release candidate, TestFlight, approvals, App Store review, release; "What's new" editable before review
Google Play rollout: AppForShare
Every track, release notes and promotion between testing tracks (Pro); production promote, set, raise, halt, resume and complete the rollout % (Team). Each change by an Admin, never automatic.; Bitrise
Rollout raised automatically over 7 days with pause, resume and cancel; staged rollout support on Standard
Release sign off: AppForShare
Release checklist ticked per build that holds the Live channel until every step is done (and, if you turn it on, no blocker is open); Admin override recorded (Team); Bitrise
Approval tasks for named stakeholders inside each release
Store listing: AppForShare
App Store and Google Play listing editor with AI translation, reviews inbox with AI reply drafts (Pro and Team); Bitrise
Listing editor and reviews not found in its docs
Notifications: AppForShare
Webhooks to Slack, Microsoft Teams, Google Chat, Discord or a signed URL for builds, installs, feedback and store status (Pro and Team); Bitrise
Slack and Teams release notices and outgoing webhooks on Standard only
CI tools: AppForShare
CLI in a Bitrise Script step today (a Bitrise step is in review), GitHub Action, fastlane plugin, Gradle plugin, Diawi and Pgyer compatible APIs, with the store readiness result in the pipeline (Pro and Team); Bitrise
Its own CI and step library; Release Management REST API and an upload script for other CIs
AI coding tools: AppForShare
Hosted MCP server with OAuth sign in, and an npm MCP package: uploads, links, readiness, testers, release status (Pro and Team); Bitrise
Hosted MCP server with OAuth sign in, about 90 tools incl. builds, artifacts and tester groups
Agency tools: AppForShare
Client projects with a portal, deliveries, feedback and e-signed sign offs (Pro 2 active, Team unlimited); Bitrise
Not found in its docs
CodePush: AppForShare
No. Whole builds only, no SDK.; Bitrise
Yes, for React Native and Expo; free up to 100,000 monthly active users

	AppForShare	Bitrise
What it is	Test build sharing and store release steps for builds made by any CI. Not a CI.	A mobile CI with hosted macOS and Linux machines, plus Release Management that works with any CI
Price	Free, Pro $12/month with a 7 day free trial, Team $39/month (5 seats). Yearly = 10 months. Lower regional prices in many countries.	CI: Hobby free (1 member, 1 private app), Starter $89/month billed yearly or $99 monthly, Pro $200/month yearly or $218 monthly, Enterprise by quote
Release Management price	No per app price: Pro and Team cover every app in the workspace	Basic free with an existing Bitrise plan; Standard $250 per app per month billed yearly, $280 monthly, volume discounts
Largest file	50 MB without an account, 150 MB Free, 2 GB Pro, 4 GB Team	2 GB per artifact on Release Management Basic
Retention	3 days without an account, 7 days Free, as long as you subscribe on Pro and Team	150 days on Basic, 365 days on Standard; 1,000 artifacts per app on Basic
Testers	Open the link and install, no extra app. Channel links that always open the newest build (Pro and Team); tester groups, install status and reminders (Team).	Public install page with QR code; access links with their own expiry or none and an optional access code; external tester groups by email (since July 2026)
Tester accounts	Never needed. Private projects for invited testers use an emailed link (Team).	Not needed for public install pages and external tester groups; the private install page needs a Bitrise login
iOS devices	Free UDID finder built in, saves devices to your account, imports UDID lists. Pro adds an onboarding link per app and one click registration on Apple; Team can register, remake the profile and start the build hands free	Devices registered from a Bitrise user profile or by UDID by hand, added on Apple by its signing steps during a build. A way for testers without a Bitrise account to send a UDID was not found in its docs.
Install page languages	13 languages incl. Hindi, Urdu, Bengali, Indonesian, Spanish, Arabic, Chinese, Portuguese (Brazil), French, Turkish, Vietnamese and Russian, picked from the phone	Other languages than English not found in its docs
Install help	Install pages say why a build will not install (iOS too old, iPad only, profile ended, App Store signed) and list the usual fixes (every plan)	Not found in its docs
Tester feedback	From the install page and from inside the test build through a link, with screenshots; no SDK (every plan with an account). Send to Linear or Jira (Pro and Team).	"What to test" text up to 4000 characters on the build page; feedback from the install page not found in its docs
Store readiness check	Every account build checked against current App Store and Google Play rules, with a fix per issue (Free and up)	Not found in the Release Management docs
App Store review	Checklist before sending (build, export compliance, review contact, texts, screenshots); an Admin sends, cancels, releases and pauses, resumes or completes a 7 day phased release (Pro and Team)	Release stages: release candidate, TestFlight, approvals, App Store review, release; "What's new" editable before review
Google Play rollout	Every track, release notes and promotion between testing tracks (Pro); production promote, set, raise, halt, resume and complete the rollout % (Team). Each change by an Admin, never automatic.	Rollout raised automatically over 7 days with pause, resume and cancel; staged rollout support on Standard
Release sign off	Release checklist ticked per build that holds the Live channel until every step is done (and, if you turn it on, no blocker is open); Admin override recorded (Team)	Approval tasks for named stakeholders inside each release
Store listing	App Store and Google Play listing editor with AI translation, reviews inbox with AI reply drafts (Pro and Team)	Listing editor and reviews not found in its docs
Notifications	Webhooks to Slack, Microsoft Teams, Google Chat, Discord or a signed URL for builds, installs, feedback and store status (Pro and Team)	Slack and Teams release notices and outgoing webhooks on Standard only
CI tools	CLI in a Bitrise Script step today (a Bitrise step is in review), GitHub Action, fastlane plugin, Gradle plugin, Diawi and Pgyer compatible APIs, with the store readiness result in the pipeline (Pro and Team)	Its own CI and step library; Release Management REST API and an upload script for other CIs
AI coding tools	Hosted MCP server with OAuth sign in, and an npm MCP package: uploads, links, readiness, testers, release status (Pro and Team)	Hosted MCP server with OAuth sign in, about 90 tools incl. builds, artifacts and tester groups
Agency tools	Client projects with a portal, deliveries, feedback and e-signed sign offs (Pro 2 active, Team unlimited)	Not found in its docs
CodePush	No. Whole builds only, no SDK.	Yes, for React Native and Expo; free up to 100,000 monthly active users

Bitrise details checked on November 2026 from its public pages (Bitrise pricing, Bitrise Release Management, Release Management concepts, Release presets, Distributing builds to testers, Installable artifacts, Registering a test device, External tester groups, CodePush, Bitrise MCP server). Plans change; tell us at contact if something here is out of date.

Use both: Bitrise CI plus AppForShare

Keep your Bitrise Workflows as they are. Add APPFORSHARE_TOKEN (made in AppForShare under Dashboard, Settings) as a Bitrise Secret, then add a Script step after the Xcode Archive, Android Build or Gradle Runner step that runs npx --yes appforshare upload "$BITRISE_IPA_PATH" --notes "$GIT_CLONE_COMMIT_MESSAGE_SUBJECT" --channel beta. Use $BITRISE_APK_PATH or $BITRISE_AAB_PATH for Android.

The step prints the install link, puts the build into the Beta channel (one link that always opens the newest build) and returns the store readiness result. Add --fail-on blocked and the step fails with exit code 2 when the check finds a blocker; the build stays uploaded. An AppForShare step for the Bitrise step library, with the same inputs and outputs such as APPFORSHARE_URL and APPFORSHARE_READINESS, is in review.

Per app vs per workspace pricing

Bitrise Release Management Standard is priced per connected app, which is one App Store or one Google Play app. Bitrise does not state whether the iOS and Android app of one product count as two. If both count, a team on CI Starter ($89 a month billed yearly) with one iOS and one Android app pays $89 plus 2 x $250 = $589 a month billed yearly for Standard, as listed on November 4, 2026.

AppForShare is priced per workspace: Team is $39 a month with 5 seats and covers every app you upload. Release Management Basic is free, so if Basic covers what you need, the honest comparison is free against our paid plans. The difference shows when you need the parts Bitrise keeps for Standard, such as notices to Slack and Teams, webhooks and store integration.

Where Bitrise is ahead

Said plainly: Bitrise is a full CI with its own Macs, and AppForShare is not. Release Management Basic is free with 2 GB artifacts kept 150 days. A release in Bitrise is one object per version with stages and approval tasks for named people, release presets fill in notes and phased release settings, and Google Play rollouts can be raised automatically over 7 days. Bitrise also hosts CodePush, a build cache and build analytics, and offers enterprise options such as an SLA and self hosted or dedicated machines. If those matter most, Bitrise is the better fit, and you can still add AppForShare for testers and clients.

Switching guides

Questions

Can I keep Bitrise CI and use AppForShare?: Yes. Add a Script step with the AppForShare CLI after your build step (an AppForShare step for the step library is in review). Bitrise keeps building, testers install from AppForShare.
Is AppForShare a CI like Bitrise?: No. It does not run builds on its own machines. It can set up builds on your own GitHub Actions (Pro and Team) and takes uploads from any CI.
Do testers need an account?: No, on either for public links. On AppForShare iPhone testers can also send their device for registration without any account.
How is pricing different?: Bitrise Release Management Standard is listed at $250 per app per month billed yearly. AppForShare Pro is $12 and Team $39 per month per workspace, not per app.
Does AppForShare do staged rollouts?: Google Play production rollouts (set %, raise, halt, resume, complete) on Team and App Store phased release controls on Pro and Team, each done by a person.
Does AppForShare have CodePush?: No. It shares whole builds; there is no SDK.
Is there an MCP server?: Yes, hosted with OAuth sign in (Pro and Team). Bitrise has one too.

Try it with your next build

No account needed for a first upload. Free accounts keep links for longer.

Upload a build Pricing