Summary pending. The diff below shows exactly what changed.
What changed
Struck in red is what Bitrise removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
Changed#1
Before: …pipelines. Pro Starting from $30/month Up to 1000 invocations , with: 100 monthly invocations for $30 50 GB high-performance storage Self-serve…
After: …pipelines. Pro Starting from $30/month Up to 1000 CI invocations Start a 30-day free trial 100 monthly CI invocations for $30 50 GB high-performance storage Self-serve…
Removed#2
Before: …way to speed up your CI/CD pipelines. Pro Plan Starting from $30/month Up to 1000 invocations ,…
After: …way to speed up your CI/CD pipelines. Pro removed Starting from $30/month Up to 1000 invocations ,…
Changed#3
Before: …2 minutes Enterprise Starting from $600/month Includes 10 seats , with: 200 monthly invocations per seat 100 GB high-performance storage $0 egress fee for…
After: …2 minutes Enterprise Starting from $600/month Includes 10 units Start a 30-day free trial 200 monthly CI invocations per unit 100 GB high-performance storage $0 egress fee for…
Changed#4
Before: …$0 egress fee for Bitrise CI Add-ons: Additional seats: $60/seat/month Additional storage: $0.80/GB/month Non-Bitrise CI egress fee: $0.12/GB…
After: …$0 egress fee for Bitrise CI Add-ons: Additional units: $60/unit/month Additional storage: $0.80/GB/month Non-Bitrise CI egress fee: $0.12/GB…
After: …$60/unit/month Additional storage: $0.80/GB/month Non-Bitrise CI egress fee: $0.12/GB Enterprise+ Starting from $750/month Custom pricing. Includes 10 units Contact sales 200 monthly CI invocations per unit 2,000 monthly local invocations per unit 10 remote build execution (RBE) workers for Bazel 100 GB high-performance storage $0 egress fee for…
Changed#6
Before: …a cache download are free. What is a seat? 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…
After: …a cache download are free. What is a unit? A unit represents a set of CI and local cache invocations which can be used across your team per month. On Enterprise, you get 10 units of CI invocations per month. This equates to 2,000 total CI invocations (200 x 10) spread across your team. On Enterprise Plus, you also get 10 units of local cache invocations, where each unit represents 2,000 invocations. This equates to 20,000 total local invocations (2,000 x 10) spread across your team. To estimate how many units your team needs, begin by counting the number…
Changed#7
Before: …invocation usage. Why is Enterprise pricing based on seats rather than invocations? Seat-based pricing makes cost estimation easier, as tracking invocations…
After: …invocation usage. Why is Enterprise pricing based on units rather than invocations? Unit-based pricing makes cost estimation easier, as tracking invocations…
Changed#8
Before: …easier, as tracking invocations can be unpredictable. Each seat includes a set number of invocations, simplifying budgeting.…
After: …easier, as tracking invocations can be unpredictable. Each unit includes a set number of invocations, simplifying budgeting.…
Changed#9
Before: …simplifying budgeting. Is there a minimum number of seats required? For Enterprise plans, a minimum of 10…
After: …simplifying budgeting. Is there a minimum number of units required? For Enterprise plans, a minimum of 10…
Changed#10
Before: …required? For Enterprise plans, a minimum of 10 seats is required. If you need fewer, the Pro…
After: …required? For Enterprise plans, a minimum of 10 units is required. If you need fewer, the Pro…
Changed#11
Before: …Build Cache currently supports caching for Bazel, Gradle, and Xcode. What CI tools does Bitrise Build Cache integrate…
After: …Build Cache currently supports caching for Bazel, Gradle, Xcode, and React Native. What CI tools does Bitrise Build Cache integrate…
Compared with the previous archived version (#5274 to #14520). Text is normalized before comparing: dates, counters and tokens show as ‹date›, ‹count›, ‹tok›, and noise-only edits are hidden. Rewindex shows changed passages with a few words of context, not a copy of the page. View the live page (opens in new tab).
Archive proof
Rewindex commits each page capture it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.