Systems | Development | Analytics | API | Testing

At Bitrise, we continually invest in security best practices to ensure that our customers' data stays safe and secure. As part of this ongoing effort, we are pleased to announce that we have successfully completed our 2026 SOC 2 Type II assessment, with no exceptions recorded in the final report. The report covers the period from July 1, 2025 to June 30, 2026 and is valid until June 30, 2027.

When top leaders from AI frontier model companies, who are often seen as competitors, come to a resounding agreement that AI development needs to slow down, we need to listen.

We're pulling back the curtain on a project we've been working on for some time now: the next evolution of the Kong brand. You may have noticed some changes recently to our site, swag, or socials. But today it's official: we're announcing Kong's rebrand and introducing our new mascot, Karl. Without further ado, let's dig in. Along the way, we'll give some insight into the "why" behind it all, while looking back at how things have changed since the early days of Kong. We were the API connectivity company.

You’ve rolled out a modern data stack, built self-service dashboards, and empowered your team to ask their own questions. Job done, right? Not quite. The data landscape is shifting rapidly beneath our feet, which makes it critical to understand how to build your AI for BI platform so you can scale and navigate technology evolutions.

A shared Kubernetes cluster rarely belongs to one team. Payments runs checkout in one namespace, search runs search-api in another, and a risk team runs a scorer somewhere else. One Speedscale forwarder captures API traffic for all of them. Redacting that traffic before it leaves the cluster is what makes it safe to use for testing (the background is in The PII Testing Dilemma). Until now, that forwarder ran exactly one DLP rule. Every team that needed a field redacted had to edit the same JSON document.