
Overview

Product video
Bitrise on AWS is sold via AWS Private Offer and a Bitrise Mobile DevOps Platform account is required before you can use Bitrise-provided AMIs. Contact us to get started: sales@bitrise.io
Bitrise on AWS unites Bitrise Mobile DevOps platform with your trusted AWS infrastructure. It enables you to meet your organization's security requirements through AWS while delivering cost and resource optimization via AMIs that support both macOS virtual and bare-metal EC2 instances, and Linux bare-metal EC2 instances.
The Linux AMI contains the most used mobile CI/CD tools for Android development preinstalled, and ready for Linux machine types.
Key Benefits & Capabilities: Deploy on macOS or Linux: Use Bitrise on AWS with macOS and Linux, either on virtual or bare-metal EC2 instances.
Resource Maximization: With Bitrise's unique virtualization approach, run multiple builds on each EC2 instance, ensuring optimum cost and performance balance.
Compliance: Keep your source code within your trusted AWS environment, meeting all compliance standards through AWS.
Optimized Workflow: From code building to testing and release management, Bitrise automates the CI/CD process, driving efficiency.
Highlights
- The AMI is contains the mobile CI/CD tools preinstalled for your Android, Flutter and React Native Workflows. https://stacks.bitrise.io/stack_reports/aws/
- Automatically manages stack and mobile tooling and dependencies (including macOS, Xcode, simulator runtimes, Android SDKs, etc), reducing the engineering burden of maintaining CI environments and increasing organizational efficiency.
- Android emulators are available in the AMI, but they can only be used with metal AWS instances
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/12 months |
|---|---|---|
Bitrise on AWS | Request Marketplace private offer at aws@bitrise.io | $36,900.00 |
Vendor refund policy
No refunds are provided. For inquiries, please contact us: https://support.bitrise.io/hc/en-us
Custom pricing options
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
This update changes the underlying OS from Ubuntu 20.04 to Ubuntu 22.04.
It also contains some breaking changes to preinstalled tooling, such as newer default versions. Please review the full list of breaking changes here: https://stacks.bitrise.io/announcements/ubuntu-22/
Additional details
Usage instructions
Bitrise on AWS is sold via AWS Private Offer and a Bitrise Mobile DevOps Platform account is required before you can use Bitrise-provided AMIs. Contact us to get started: https://bitrise.io/contact Please see our documentation on how to setup the AWS machines with your Bitrise organization: https://devcenter.bitrise.io/en/infrastructure/running-bitrise-builds-on-aws.html
Resources
Vendor resources
Support
Vendor support
As part of our basic support package we are offering documentation, access to our community forums and ticket raising, without SLA. Premium support may be selected as part of AWS Private deals. Please raise your support request here for technical help: https://support.bitrise.io/hc/en-us We aim to respond within 24 hours. Reach out to our support team:
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.


Standard contract
Customer reviews
Faster builds have accelerated mobile releases and support rapid feedback from teams
What is our primary use case?
My main use case for Bitrise is the deployment of our application to the iOS store and Android store, mainly.
We migrated our pipelines from Bitrise to GitHub because we wanted to unify our tools. A simple example is our application deployment, where we automated all the processes from building to deployment and testing within Bitrise.
Another use case that we had for Bitrise was the automatic building of the application and automatically depositing it to a bucket in which our QA team retrieves all the information, not just about the building but also the artifact, so they can do automated testing in other platforms.
What is most valuable?
The best feature Bitrise offers is the friendly UI that allows you to configure your own pipeline by dragging and dropping everything.
Specifically, the drag-and-drop UI and custom code steps have helped us because at some point, we had two applications, one for businesses and one for people in general. The UI allowed us to duplicate the workflow, so we did not have to configure it again, just changing some specific variables.
Bitrise has positively impacted our organization by providing a huge improvement at the very beginning of our operations. We previously used Azure Pipelines to deploy our application, which took two to three hours for an iOS deployment, while Bitrise reduced the simple building time to just 45 minutes.
The faster deployment with Bitrise allows us to get to the market quickly, enabling us to receive feedback from clients rapidly, test our application internally, and deliver more robust solutions efficiently.
What needs improvement?
Bitrise can be improved by perhaps showing the statistics of usage without requiring a greater subscription, as the prices were really high compared to other tools and we lacked metrics of our usage, such as how many builds were completed and how many failed.
Bitrise did what it needed to do during my time working with it, and I do not think anything else was needed since it was really easy to use, and its runners were really fast and optimized to do their job well.
Regarding Bitrise's AI capabilities, I do not know much about its governance and security, as when I was working with them, the only AI features I used were a chatbot, which did not provide much information about how they manage the information.
As for Bitrise's AI capabilities, the accuracy and reliability of output were not that good. Most of the time, it redirected me to a human or advised me to open a ticket, so it was not really useful.
For how long have I used the solution?
I have been working as a DevOps engineer for three years.
What do I think about the stability of the solution?
Bitrise was stable.
What do I think about the scalability of the solution?
We did not have the chance to make really huge solutions or pipelines. I think Bitrise has worked a lot on scalability, and I find it really scalable because you can create small portions of code or stages that can be reused in other workflows.
How are customer service and support?
My experience with customer support at Bitrise was really nice, as they were very patient, particularly with my non-native English speaking. They were always checking if we needed something, which was really good.
It was really amazing to work with Bitrise. They have a really good customer support team, and technically, everything was really good. They found an employee who speaks Spanish to join one of our meetings, making it easy to continue our negotiations.
Which solution did I use previously and why did I switch?
We previously used Azure Pipelines and switched to Bitrise because it was way faster, had many integrations, and was really easy to set up. The UI helped us a lot to do our job well.
What was our ROI?
I have seen a return on investment with Bitrise, as at the very beginning, our deployment times for our iOS application were three hours, but with Bitrise, it was reduced to just 45 minutes, showing it was really fast.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for Bitrise was positive since it was really cost-optimized. The setup cost was actually null, and it was really easy to set up and renovate the licensing.
Which other solutions did I evaluate?
We evaluated CircleCI and GitHub Actions before choosing Bitrise.
What other advice do I have?
My advice for others looking into using Bitrise is that it is a platform to start new products, giving you an optimized version of a runner with good customer support that you can reach out to for anything you need. I would advise choosing it with complete confidence. I would rate this review a 9.
Automation has reduced weekly build overhead and simplifies sharing releases across teams
What is our primary use case?
My primary use case for Bitrise is for continuous integration and continuous delivery, commonly known as CI/CD purposes. I use Bitrise to automate repetitive tasks of managing my app's life cycle for sharing multiple builds with the QA team, product team, and for finally releasing the build to the App Store or Play Store.
Being in the mobile development field, I have to constantly handle multiple apps for my organizations. I need to share these builds across QA teams for both iOS and Android and with product teams for their reviews and for their tasks. Doing so manually would take a lot of time, but if I automate this process using Bitrise, I can easily share and easily reduce this time-consuming task.
Primarily in case of iOS development, the build-making process is quite complex due to provisioning profile handling and related tasks. Bitrise simplifies that process completely for me.
What is most valuable?
The best features Bitrise offers include direct deployment to the App Store and Play Store and direct connection to both TestFlight and App Store releases, which is a great Bitrise tool.
Doing the task of direct deployment manually can lead to several bugs in the release pipeline process, but once I automate it using Bitrise, this particular task is taken off the developer's hand and is automated, saving a lot of development time.
The integration is quite simple, and once done, I do not need to revisit it again. Bitrise can easily handle multiple applications.
Since I started using Bitrise, the development time, specifically the time that I spend on sharing these builds and handling the release process, is significantly reduced.
A ballpark figure indicates that I save around three to four hours per week since using Bitrise.
What needs improvement?
Sometimes the builds fail, and the error messages that I get are not very descriptive. That could be improved.
I give Bitrise an eight out of ten because sometimes builds fail, and the error paths are not that descriptive.
For how long have I used the solution?
I have been working in my current field for more than twelve years.
What do I think about the stability of the solution?
Bitrise is stable, apart from the odd build failure.
Apart from the odd build failure, Bitrise is quite reliable in its accuracy and reliability of output.
What do I think about the scalability of the solution?
Bitrise's scalability is quite good. I have automated multiple apps from the same organization across iOS and Android, and they work quite well.
How are customer service and support?
The customer support for Bitrise is good. I never faced any issues.
Which solution did I use previously and why did I switch?
I previously tried Jenkins . Different organizations prefer different tools, so in my previous organization, I used Bitrise, while Jenkins is also used in my current organization.
How was the initial setup?
The integration is quite simple, and once done, I do not need to revisit it again.
Which other solutions did I evaluate?
I have evaluated Jenkins before choosing Bitrise; it is also a good tool.
What other advice do I have?
My developer's time is definitely saved, and I can say that in a week, three to four hours are easily saved.
I would advise others looking into using Bitrise to definitely try it, as they can save a lot of their developer's time. The automation part, the redundant part of sharing builds and managing app lifecycle can be handed over to an automated system, significantly improving their output.
I rate this product an eight out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Mobile pipelines have supported app releases and now need reusable templates and modular workflows
What is our primary use case?
What is most valuable?
I think the best feature of Bitrise is the flexibility to use third-party engines like Fastlane.
I use third-party integrations like Fastlane with Bitrise to avoid vendor lock-in, facilitate my migration to another platform, and have a unique workflow for deploying about twenty to thirty apps.
Bitrise has had a significant positive impact on my organization because we do not have any other platform to realize these builds and deploys with mobile apps.
Bitrise has helped reduce errors in my workflows because I have tests, E2E tests, integration tests, and Appdome tests.
What needs improvement?
Bitrise has a strong mobile focus, and what could improve is the native support for reusable pipeline modules like actions in a GitHub Action, better templates, think Terraform style but for CI, and easier parameterization across workflows.
Templates would be a significant improvement for me. It is the one thing I need and it would make my life easier with the workflows.
For how long have I used the solution?
I have been using Bitrise for four years.
What do I think about the stability of the solution?
Bitrise is sometimes stable, and sometimes I experience problems with Bitrise.
What do I think about the scalability of the solution?
Bitrise's scalability is adequate.
How are customer service and support?
Bitrise customer support is slow but functional.
Which solution did I use previously and why did I switch?
I am not using a solution different from Bitrise. I am working on a migration from Bitrise to GitHub Actions because the cost is lower.
Which other solutions did I evaluate?
Before choosing Bitrise, I did not evaluate other options.
What other advice do I have?
You should consider Bitrise as it is a strong platform when used appropriately. The biggest mistake is treating it like a general-purpose DevOps solution. I would advise others that Bitrise is best used for its intended mobile focus, and this approach saves you time. I would rate this product a seven out of ten.
Drag and drop workflows have streamlined iphone build, test, and app store deployment
What is our primary use case?
My main use case for Bitrise is for iPhone CI/CD and App Store Connect build deployment.
I am using Bitrise for iPhone CI/CD and App Store Connect to take a Git clone, create a build, deploy to the App Store, and send a push notification to the teams that the build is uploaded and it is in review.
I am using the Xcode build, which is really working great for me in Bitrise.
What is most valuable?
The best feature of Bitrise is that it gives a drag and drop interface, so you don't need to code in the YAML, making it very easy compared to other platforms.
The drag-and-drop feature helps my workflow because I just have to select which tool I want to use. For example, if I want to add the test cases, I can search for test cases, and if that is available, I can directly drag and drop it in my current workflow above or below a specific other task, and then I just have to add the input parameters. In contrast, with a YAML file, I have to add all the data and read the documentation, but with drag and drop, it is easy.
Bitrise has positively impacted my organization by helping me reduce time by around 50% or more while I am using it for my personal project.
Bitrise saves me time mainly in building, testing, and deployment because I don't have to use my own machine to check the data or change the branch for that.
What needs improvement?
Currently, I haven't found any features in Bitrise that can be improved, but related to Xcode, they need some extra tools that are available in the market, or they have to give specific errors, which are currently hard to find when there is so much log.
They need to add some extra documentation for how to use the parameters, such as variables, where to add them, and how to use them below the workflow.
For how long have I used the solution?
I have been using Bitrise for around five years.
What do I think about the stability of the solution?
Bitrise is very stable in my experience.
What do I think about the scalability of the solution?
Bitrise's scalability is fine for my needs as of now, and I see no need to change anything.
How are customer service and support?
I have used the community support for Bitrise, and it is great. I haven't reached out to customer support.
Which solution did I use previously and why did I switch?
Bitrise is the first one I have used, and I haven't used any other solutions.
What was our ROI?
I can see a return on investment with Bitrise, but since I am using the free tier, I don't have any idea about the pricing and those things.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for Bitrise would be good, but I haven't used that because I am using the free tier.
Which other solutions did I evaluate?
Before choosing Bitrise, I haven't evaluated other options.
What other advice do I have?
I chose eight out of 10 because currently, it is easy for me, but there is some documentation missing, and also related to iOS development, there are some use cases that are not in the support portal, so I have to find it out by myself. On a scale of 1 to 10, I would rate Bitrise an eight.
Continuous QA builds have streamlined testing workflows and provide clear logs for faster fixes
What is our primary use case?
What is most valuable?
The best features Bitrise offers, in my opinion, are the QA itself, the artifact it generates, and the log, which makes it very simple to know what step we got an error or the log for the error, so we know what we have to do to fix it.
The logs help us significantly; for example, if we generate a QA for Android and iOS, and if a specific step for Android fails, I can look at the log and see exactly what step we got an error, and with this log, we can find out what went wrong.
Bitrise has positively impacted our organization by improving release speed.
What needs improvement?
I think Bitrise could be improved if it was easier to generate Android QA and iOS at the same time.
For how long have I used the solution?
I have been working in my current field for about five years.
What do I think about the stability of the solution?
I think Bitrise is stable, and I do not remember having any problem with stability.
What do I think about the scalability of the solution?
I think Bitrise's scalability is very good.
Which solution did I use previously and why did I switch?
Bitrise was the first and only solution we used; I did not previously use a different solution before Bitrise.
What other advice do I have?
I would advise others looking into using Bitrise to start using it; it is a very good tool. There is no other relationship between my company and this vendor other than being a customer. I give Bitrise an overall rating of 8.