Start your free trial, decide on a plan later.
Quickly diagnose problematic builds and tests with an overview of your CI/CD health trends.
Manage app distribution from a single hub and gain clear visibility into your release journey.
Reduce local and CI build times with a
fully-managed remote build and test cache.
7XL)Our Enterprise plan allows for more customizability to your limits and additional benefits for high resource needs.
In contrast to our Pro plans, which provide shared public build environments exclusively, our Enterprise plans offer enhanced flexibility by providing fully managed options for both public and dedicated environments. This empowers you with increased security and control over your build environment. Additionally, you can self-host your build infrastructure through Bitrise on AWS or by utilizing Bitrise Agent for on-premise setups.
Enterprise also offers the best and most performant compute options as well as additional features for a more robust governance of your configuration and team.
With the Starter plan, you can get your new pipeline up and running with unlimited build minutes. The Starter plan allows you to run up to three concurrent builds with up to 10 Bitrise users – ideal for individual developers and small teams just getting started with Bitrise.
As your builds and teams grow, our Pro plan gives you the opportunity to optimize the efficiency of your builds. With flexible tiers tailored to your specific needs, you can easily balance build throughput and cost with increased compute performance out of the box.
Talk to us. The team will make sure the plan fits your exact needs.
Build means a workflow run triggered either as standalone or as part of a pipeline.
For Bitrise Pro and Enterprise plans, our pricing is largely based on the number of monthly builds run on Bitrise Platform. So, you should look at your typical monthly throughput in terms of executed workflows, both successful and not, and use that as a starting point when figuring out the appropriate Tier.
Build cost is calculated based on your pricing plan.
Linux L
Ubuntu VM, 8 vCPU, 32 GB RAM @3.7 GHz
Mobile DevOps Platform Plan and Pro
Linux 4L
Ubuntu VM, 14 vCPU, 56 GB RAM @3.7 GHz
Mobile DevOps Platform Plan and Velocity
Linux XL
Ubuntu VM, 16 vCPU, 56 GB RAM @3.7 GHz
Mobile DevOps Platform Plan
Linux 3XL
Ubuntu VM, 24 vCPU, 96 GB RAM @3.7 GHz
Mobile DevOps Platform Plan
Linux 5XL
Ubuntu VM, 32 vCPU, 128 GB RAM @3.7 GHz
Mobile DevOps Platform Plan
Linux 7XL
Ubuntu VM, 48 vCPU, 192 GB RAM @3.7 GHz
Mobile DevOps Platform Plan
Bitrise’s main goal is to make our Customers’ mobile CI/CD process as efficient and productive as possible. Infrastructure resources play a big part in this. As such, we strive to offer the most performant machines to our customers, and we strive to do it at passthrough cost, without any profit-generating margin. This should allow our customers to focus on running value-add builds, and not counting credits or minutes.
Within the Pro plan, if you consumed the max number of builds or minutes within your tier, you can use the Pay-As-You-Go option. If you pay annually, you can also consider buying an additional 4 months' of resources through Extra Build Capacity (see FAQ below).
Pay-As-You-Go (PAYG) allows all Pro Plan users to run additional builds and compute minutes even after you've reached your plan’s monthly limit. Here's how it works:
If you consistently rely on PAYG, upgrading your plan can reduce costs and prevent build interruptions.
Extra Build Capacity is an exclusive feature for annual Pro Plan users that lets you pre-purchase additional resources to use flexibly throughout the year.
If you have seasonal workload fluctuations, or you anticipate a surge in your usage, Extra Build Capacity ensures your team has the resources it needs without committing to a higher plan year-round.
Total compute time is a function of number of builds * builds’ duration. However, there is a big difference between a large number of short builds and a small number of long builds. And the difference is in the value realized: shorter feedback loop, faster iterations, no context switching.. Through our pricing model, Bitrise is aligning with your goals: pay for value, not hardware consumption. Build more, build faster, build smarter.
In order to create a pricing plan tailored for your needs, you can reach out to our sales team. You can fill in the form here and we will create a unique pricing solution that fits your needs.
The Build timeout is the maximum amount of time a workflow is able to run. When your build hits the build timeout limitation, your build will be stopped. On our Free plan, your build times out at 90 minutes, while on Starter and Pro, it can run up to 210 minutes. On Enterprise, build duration is flexible, up to a maximum of 4 hours.
All Bitrise accounts come with ticket-based email support and community support: ask questions and answer fellow developers’ on our Discuss page and Slack channel, or start a conversation with our Support team in the Messenger in the bottom right corner.
Customers receiving Priority support will gain access to a customer success manager to help you achieve your most pressing goals on Bitrise.
Premium support also includes: a technical account manager, ticket SLAs, a dedicated Slack channel, and impact sessions, where we give guidance driving performance improvements.
Our Hobby tier is free. No strings attached, no credit card needed. We give you 1 private app, 5 concurrencies with 90 mins/build timeout and 300 credits per month. Try Bitrise, it’s on us.
You will have access to all the capabilities of the “Pro” plan. You will also have a total of 500 builds available during the trial. These limits are available just for the trial. When you pick a plan, you get resources as per your plan allowance.
You can check your monthly cycle usage on your Workspace’s Plan & billing page. You can also check your number of builds and build minutes consumed on Insights and see historical trends. Navigate to the “Insights” tab, and find “Utilization” on the left navigation bar. If you run out of resources, you can either request a trial extension or just get going with a paid plan.
Yes, you can activate a paid plan anytime during your 30-day trial. Just click on “Select plan” from the top banner whenever you are ready. Alternatively, you can go to the “Plan & Billing” section of your “Workspace Settings” to view available plans.
You will be able to see the trial end date in your welcome email, on Bitrise as a banner, or even in your Workspace Settings. We’ll remind you 5 days before your trial ends with an email and also on the UI. At the end of the trial, you will be asked to choose a plan before you can continue using Bitrise.
You can also continue using Bitrise for free, you will be able to choose our “Hobby” plan at the end of the trial where you will still be able to access the basic capabilities for free, with a credit allowance of 300 per month.
Build for free and purchase your Starter or Pro plan at any time,
or reach out for the Enterprise plan.
An invocation is a Gradle or Bazel command (e.g. gradle test, bazel build) that runs with Bitrise Build Cache enabled. Only invocations that download data from the cache count toward your limit. Invocations that don’t result in a cache download are free.
A seat represents one developer using Bitrise Build Cache and is a key component of Enterprise plans. It helps estimate the expected number of cache invocations your team will require. Each seat on an Enterprise plan includes 200 monthly invocations.
To estimate how many seats your team needs, begin by counting the number of engineers actively contributing to projects using Build Cache. Keep in mind that actual usage can vary based on several factors. The most accurate way to determine your needs is by starting a free 30-day trial, which provides full visibility into your team’s real invocation usage.
Seat-based pricing makes cost estimation easier, as tracking invocations can be unpredictable. Each seat includes a set number of invocations, simplifying budgeting.
For Enterprise plans, a minimum of 10 seats is required. If you need fewer, the Pro plan may be a better fit.
Build Cache stores previous build and test outputs to speed up future builds. Storage needs depend on your project size—larger projects require more storage to maintain optimal performance. Our default storage package is calculated to accommodate most use cases.
Bitrise Build Cache currently supports caching for Bazel, Gradle, and Xcode.
Bitrise Build Cache offers native integration with Bitrise CI, allowing you to get set up in just two minutes. It also supports other CI platforms, including CircleCI, GitHub Actions, GitLab CI, and Jenkins. Please note that integration with non-Bitrise CI platforms requires an Enterprise subscription, and an egress fee applies.
Build for free and purchase your Starter or Pro plan at any time,
or reach out for the Enterprise plan.
Pricing is billed per app.
You do not need to be a Bitrise user to manage your app distribution with Release management. You can upload release candidates from your local machine or any CI system, though it’s fully integrated with Bitrise CI for a smoother experience.
Yes! We offer whitelabel add-ons and volume discounts as part of our Standard plan. If you're managing releases across multiple client apps or distributing under different brands, reach out to our team to discuss a custom plan tailored to your needs.
Yes! Bitrise Release Management is a powerful alternative to App Center, supporting both beta distribution and store releases for iOS and Android. With automation, CI integration, and scalable workflows, it’s built to handle what App Center users need—and more.
Build for free and purchase your Starter or Pro plan at any time,
or reach out for the Enterprise plan.
Plan overview | Monthly fee | Annual (10% discount) | Price per MAU (annual) | ||
|---|---|---|---|---|---|
Basic Tier | 100,000 | Free | Free | Free | 5,000 |
250,000 | $294 | $3,180 | $0.00106 | 12,500 | |
500,000 | $572 | $6,180 | $0.00103 | 25,000 | |
1,000,000 | $1,111 | $12,000 | $0.00100 | 50,000 | |
2,000,000 | $2,156 | $23,280 | $0.00097 | 100,000 | |
3,000,000 | $3,139 | $33,900 | $0.00094 | 150,000 | |
5,000,000 | $5,072 | $54,780 | $0.00091 | 250,000 | |
CodePush - Enterprise | For more than 7,000,000 MAUs, please contact sales | ||||
Monthly active user is a unique end user who downloads one or more CodePush updates within a single monthly billing cycle. Multiple downloads by the same person in that month count as a single MAU.
Data transfer volume is the total size of files delivered by CodePush updates to your users measured in GiB.
The total amount of space depends on your plan. Free tiers have 5 GiB, CodePush Pro plans have 25 GiB, and Enterprise plans start at 50GiB.
To subscribe to the CodePush Pro or Enterprise tier, users need a paid Bitrise CI plan. Hobby plan users are able to use the free tier.
All of them. Delta updates, code signing, staged rollouts, one-click rollback, mandatory updates, and the Bitrise CI Workflow Step are available on every plan including Basic. Paid tiers give you higher MAU, data transfer, and storage limits, not extra capabilities. See a full list of Bitrise CodePush features here.
Your monthly budget can be used flexibly depending on your platform split: all macOS, all Linux, or a mix of both. Move the slider to see what your monthly minutes could look like on a Basic or Pro Plan.
This example shows how you could choose to split minutes on a Basic or Pro Tier 1 Plans for illustrative purposes only. See all machine rates and overages.
Your Plan includes one monthly compute budget. macOS and Linux builds draw from the same pool, but each machine type uses it up at a different rate. How many minutes you get depends on how you split your usage.
When included compute budget runs out, builds keep going at overage rates.
Track your spend and remaining balance right from your workspace's Plan and Billing page.
| Basic | Pro | |
|---|---|---|
| Fee | Starts at $13.50/month | Starts at $189/month |
| Machines (macOS) | M4 Large | M4 (Large, X Large) |
| Machines (Linux) | Linux (M, 2M, L) | Linux (M, 2M, L, 4L, XL) |
Concurrency (macOS) | Up to 35 vCPU | Up to 136 vCPU |
Concurrency (Linux) | Up to 90 vCPU | Up to 640 vCPU |
Flexible minute allowance | Up to 6,000 minutes on macOS or Up to 14,400 minutes on Linux | Up to 27,000 minutes on macOS or Up to 64,800 minutes on Linux |
Build Hub runs your GitHub Actions workflows on fully managed build infrastructure from Bitrise. You keep your existing GitHub Actions workflows and get dedicated access to powerful macOS and Linux runners, without managing your own hardware.
The Bitrise Build Hub free trial gives you 14-day access to all machines available in Pro and Basic Plans.
On the macOS side, you can test out M4 Large(5 vCPU, 14 GB RAM) and M4 X Large(10 vCPU, 28 GB RAM) machine types. The 30 vCPU macOS limit enables you to run 3 Github Actions jobs on M4 X Large OR 6 jobs M4 Large in parallel.
On the Linux side, you can test out five machine types, ranging from Medium (4 vCPU, 16 GB RAM) up to X Large (16 vCPU, 64 GB RAM). The 48 Linux vCPU limit enables you to find your best price performance machine type, for example you can run 3 Github Actions jobs on Linux X Large OR 12 jobs on Linux Medium in parallel.
The Pro Tiers are the best option for growing teams that need to run more builds in parallel as you get higher vCPU concurrency limits and faster machines. Basic Tiers offer macOS M4 Large and Linux up to Linux Large, making it perfect for solo developers and smaller teams.
Basic Tiers get:
Each Tier has a macOS and a Linux concurrency limit. On both platforms machines will start to run your Github Actions job if the started machine doesn’t exceed the concurrency limit.
Example 1:
If you are on Pro Tier 1 with existing machines tying down 35 vCPU macOS already, then an M4 Large (5 vCPU, 14 GB RAM) machine can spin up to serve your newly triggered Github Actions jobs, to reach your 40 vCPU macOS concurrency limit. On the other hand an M4 X Large (10 vCPU, 28 GB RAM) won’t be able to spin up, since it’s exceeding your concurrency limit.
Example 2:
You are on Pro Tier 1 and running already macOS machines and consuming all your macOS concurrency limit. Given that the machine concurrency limit is platform specific, your Linux Github Actions jobs will still spin up machines to serve them, if it fits within your Linux concurrency limit, despite you already reaching your macOS concurrency limit.
Each Tier Plan includes one shared compute budget that covers both macOS and Linux builds. macOS and Linux machines draw from the same pool, but each uses it up at a different rate, so how many minutes you actually get depends on how you split your usage between the two.
Example 1:
On Basic Tier 4 you get a monthly budget of $180 regardless of monthly or annual billing(which comes with 10% discount). The $180 monthly budget gets you 6000 M4 Large minutes if you use macOS exclusively, given that the M4 Large machine has a $0.03 per minute cost.
If you use it exclusively on Linux Medium machines, then your Github Actions jobs can run a total of 14,400 minutes per month, thanks to the $0.0125 price per minute of the machine type.
Of course you can use both platforms at the same time time. Check out the Price / min rate under the “machine rates and overages” under the “Your monthly budget flex between Mac and Linux” section.
You won’t be able to run more builds until the monthly cycle resets for you.
We are going to implement a new capability shortly, which will enable you to keep running builds, while using the pay-as-you-go overage rates, until the new monthly cycle resets for you. You can track your remaining balance and spend anytime from your workspace's Plan and Billing page.
Enterprise is for teams that need the strongest machines to run at unparalleled scale. The Bitrise Build Hub Enterprise offering includes the full machine range (Apple silicon up to M4 Pro, Linux up to 96 vCPU).
Additionally the All-You-Can-Eat pricing model, provides unlimited Github Action jobs minutes within your dedicated vCPU concurrency.
Yes. You can start with Basic Tier 1 and upgrade to any higher Tier at any time as your team's needs grow, or move to Enterprise by talking to our team.
Build for free and purchase your Basic or Pro Plan at any time, or reach out for the Enterprise Plan.
Each machine type gets its own included minutes: up to 1,440 minutes
Once included minutes run out, every extra minute on that machine is billed up to the monthly cap
Once you hit the cap, you keep running for the rest of the month at no extra charge.
| Basic | Pro | |
|---|---|---|
| Base fee | Starts at $20/month | Starts at $40/month |
| macOS machine | M2 Pro Large (6 vCPU / 14GB) | M2 Pro X Large (12 vCPU / 28GB) |
| Linux machine | Small (2 vCPU / 8GB) | Medium (4 vCPU / 16GB) |
| Included minutes (per OS) | Up to 1,440 minutes (24 hrs) | |
| Concurrent VMs | 1–5, by tier | |
| Overage rate | macOS $0.0288/min · Linux $0.0044/min | macOS $0.0576/min · Linux $0.0088/min |
| Monthly cap | macOS $99–495 · Linux $39–195 | macOS $199–995 · Linux $79–395 |
No. Each OS type gets its own included allocation at the same tier. A Basic Tier 1 customer gets 8 hours of macOS time AND 8 hours of Linux time, not 8 hours split between them.
You're billed per minute up to your monthly cap, at a rate that depends on your package and which VM type (macOS or Linux) you're using:
Yes. Each VM type has its own monthly cap, and it scales with your tier's concurrency:
Once your bill for a VM (OS) type reaches its cap, that VM type is free for the rest of the month. VMs keep running; you just stop paying.
Two weeks, Tier 1 allocation (8 hours per OS, 1 concurrent VM), credit card required at signup for verification only. We will not charge your credit card or require you to purchase a subscription.
No. After your 14 days are up, you can select a Basic or Pro plan to continue using RDE. We won't auto-bill you into either plan.
| TIER 1 | TIER 2 | TIER 3 | |
|---|---|---|---|
Base fee billed annually | $18/month or $20 per month when billed monthly | $36/month or $40 per month when billed monthly | $54/month or $60 per month when billed monthly |
| macOS VM | M2 Pro Large (6 vCPU / 14GB) | M2 Pro Large (6 vCPU / 14GB) | M2 Pro Large (6 vCPU / 14GB) |
| Linux VM | Small (2 vCPU / 8GB) | Small (2 vCPU / 8GB) | Small (2 vCPU / 8GB) |
| Included minutes / month (per OS) | 480 minutes / month (8 hrs) | 960 minutes / month (16 hrs) | 1,440 minutes / month (24 hrs) |
| Concurrent VMs | 1 | 3 | 5 |
| macOS monthly cap | $99 | $297 | $495 |
| Linux monthly cap | $39 | $117 | $195 |
| TIER 1 | TIER 2 | TIER 3 | |
|---|---|---|---|
Base fee billed annually | $36/month or $40 per month when billed monthly | $72/month or $80 per month when billed monthly | $108/month or $120 per month when billed monthly |
| macOS VM | M2 Pro X Large (12 vCPU / 28GB) | M2 Pro X Large (12 vCPU / 28GB) | M2 Pro X Large (12 vCPU / 28GB) |
| Linux VM | Medium (4 vCPU / 16GB) | Medium (4 vCPU / 16GB) | Medium (4 vCPU / 16GB) |
| Included minutes / month (per OS) | 480 minutes / month (8 hrs) | 960 minutes / month (16 hrs) | 1,440 minutes / month (24 hrs) |
| Concurrent VMs | 1 | 3 | 5 |
| macOS monthly cap | $199 | $597 | $995 |
| Linux monthly cap | $79 | $237 | $395 |
| TIER 1 | TIER 2 | TIER 3 | TIER 4 | |
|---|---|---|---|---|
Fee billed annually | $13.50/month or $15 per month when billed monthly | $40.50/month or $45 per month when billed monthly | $81/month or $90 per month when billed monthly | $162/month or $180 per month when billed monthly |
| macOS VM | M4 Large (all tiers) | |||
| Linux VM | Linux (M, 2M, L) (all tiers) | |||
| Monthly budget spent fully on macOS | 500 mins | 1,500 mins | 3,000 mins | 6,000 mins |
| Monthly budget spent fully on Linux | 1,200 mins | 3,600 mins | 7,200 mins | 14,400 mins |
| macOS concurrency | 10 vCPU (2 M4 L) | 15 vCPU (3 M4 L) | 30 vCPU (6 M4 L) | 35 vCPU (7 M4 L) |
| Linux concurrency | 24 vCPU (6 Linux M) | 32 vCPU (8 Linux M) | 64 vCPU (16 Linux M) | 136 vCPU (34 Linux M) |
| TIER 1 | TIER 2 | TIER 3 | TIER 4 | |
|---|---|---|---|---|
Fee billed annually | $189/month or $210 per month when billed monthly | $270/month or $300 per month when billed monthly | $540/month or $600 per month when billed monthly | $729/month or $810 per month when billed monthly |
| macOS VM | M4 Large, M4 X Large (all tiers) | |||
| Linux VM | Linux (M, 2M, L, 4L, XL) (all tiers) | |||
| Monthly budget spent fully on macOS | 7,000 mins | 10,000 mins | 20,000 mins | 27,000 mins |
| Monthly budget spent fully on Linux | 16,800 mins | 24,000 mins | 48,000 mins | 64,800 mins |
| macOS concurrency | 40 vCPU (8 M4 L) | 55 vCPU (11 M4 L) | 70 vCPU (14 M4 L) | 90 vCPU (18 M4 L) |
| Linux concurrency | 160 vCPU (40 M or 10 XL) | 240 vCPU (60 M or 15 XL) | 480 vCPU (120 M or 30 XL) | 640 vCPU (160 M or 40 XL) |
Each machine draws from the included monthly compute at a per-minute rate. Once the included budget is consumed, no more Github Action jobs will be served until the monthly budget resets. We are working on the Pay-As-You-Go capability, enabling you to run additional GitHub Action jobs at the PAYG per-minute rate.
| Specs | Price / min | PAYG / min | |
|---|---|---|---|
macOS M4 Large | 5 vCPU / 14 GB | $0.03 | $0.06 |
macOS M4 XLarge | 10 vCPU / 28 GB | $0.06 | $0.12 |
| Linux Medium | 4 vCPU / 16 GB | $0.0125 | $0.025 |
| Linux 2Medium | 6 vCPU / 24 GB | $0.01875 | $0.0375 |
| Linux Large | 8 vCPU / 32 GB | $0.025 | $0.05 |
| Linux 4Large | 14 vCPU / 56 GB | $0.04375 | $0.0875 |
| Linux XLarge | 16 vCPU / 64 GB | $0.05 | $0.1 |