We were thrilled to announce our new credit-based plan, Teams, earlier this week, which is available to new customers as well as those already using a concurrency-based plan on Bitrise.
Based on some questions we've received from existing customers over the last few days, we'd like to go into a little more detail about the differences between the concurrency and credit-based models, as well as what you can expect should you make the switch.
For readers who are not using Bitrise already, we'd recommend that you read our announcement to discover the flexibility and power of Teams.
How your Bitrise plan will change
Our new Teams plan is fundamentally different from the traditional concurrency based-plans you found on Bitrise before:
- Instead of being tied to a specific number of concurrent builds, your Teams plan lets you run 30 (Linux) or 10 (MacOS) builds simultaneously;
- Your builds will no longer timeout at 45 or 90 minutes, but can run up to 4 hours uninterrupted;
- You can pick a different compute option for each individual workflow, and;
- You have access to our faster Gen2 build platform.
Like the Velocity plans we launched earlier this year, Teams plans use a system of credits.
Each tier of the Teams plan has a monthly allotment of credits. As you go up in tier, you receive a larger number of credits at a cheaper cost per credit. The faster the machine, the faster your build will finish, and the more credits per minute you’ll use.
Credits and build behaviors
The new credit-based system used in Teams has been extensively tested. There are a number of Velocity customers that have been using it since late last year, and since the start of 2021 we’ve been sending a share of new users into a slightly different version of Bitrise, featuring exclusively credit-based plans.
What we’ve noticed in both cases is that build behaviors have changed. As people became more aware of the cost of a build, most teams started paying more attention to build duration, and — because you can pick a compute option per workflow — started thinking of builds as either urgent or not.
Among those users, we’ve seen:
- Teams kick off slightly fewer builds;
- Planned builds are no longer mostly kicked off at night (a behavior users on concurrency-based plans display to keep concurrencies available for urgent work), and;
- Incentivized by the credits system, teams spend time on optimizing their builds for performance, which has resulted in builds that are faster than explainable by the Gen2 build platform alone.
This last outcome, in particular, is one we’re actively supporting.
In addition to documentation and content around the topic of improved build performance, we’re nearing the beta launch of a build and team performance monitoring feature in Bitrise. There, you'll find granular build performance data, put together to help you optimize your build times, and improve your team's velocity.
In the meantime, contact us, or talk to your Bitrise contact for 1:1 support in improving your build times.
As a concurrency-based user, how can I access Teams?
Over the next couple of weeks, it will be possible for users currently on a Developer, Org Standard, or Org Elite plan to create a new credit-based Teams account from within the UI, which will come with a 500-credit trial. This will allow you to get a feel for the differences first-hand.
If you’re interested in trialing sooner, or feel like you have requirements that you can’t assess within a 500-credit trial, register your interest, and we’ll get back to you as soon as possible.
How can I assess my future credit needs?
You can find build statistics using the Bitrise API and build durations are displayed within Bitrise when a build finishes. Using this information, you can manually assess your current usage to find out what your future credit requirements will be. However, the best way to estimate credit requirements is to begin a 2-week trial of Teams and find out first-hand.
How many credits will be required per build minute depends on the compute option used. The image below compares the credits needed per minute on Gen1 Linux and macOS machines versus macOS Gen2 machines (note that Gen2 Standard and Elite are available on Teams, while Elite XL is available only on Velocity).
If you wish to discover just how much of a difference Gen2 makes to build time — and subsequent build velocity and team performance — please download our Gen2 benchmark report.
Remember that on credit-based plans, you can select the machine type that best fits your needs, even on a Workflow level. For example, you can use our faster Gen2 Elite machines for your time-critical builds but opt for the Standard machines for builds with lower priority.
How much you pay each month and per credit depends on your Teams credit tier:
Building better for mobile
Over the last few years we have seen the limitations that a concurrency-based model imposes on mobile engineering teams.
The switch to a credit-based pricing plan means that teams have greater flexibility and scalability, while also having access to the next generation of the Bitrise Build Environment: Gen2.
This is a change that allows our customers, the Bitrise product, and us as a company to grow together, sustainably.
If you wish to learn more about our new Teams plan, beyond the differences between the concurrency and credit-based models, you can read our introductory blog post. Or, alternatively, contact us and we’ll be happy to answer your questions.
And if you’re ready to trial Teams, register your interest and we’ll get back to you as soon as we can.