Alessandro Yuichi Okimoto

We're excited to announce Bucketeer 2.0, a major update to our feature flag management platform. This release is all about usability, speed, and flexibility — making it easier than ever to manage flags, collaborate with your team, and roll out changes with confidence.

Over the past months, we've listened closely to feedback from the community. Many of you wanted a smoother workflow, faster flag management, and more intuitive tools. With Bucketeer 2.0, we've reimagined the console from the ground up to deliver just that.

Bucketeer has always been a powerful open-source platform for feature flag management and A/B testing.
But until now, self-hosting Bucketeer required Google Cloud services like BigQuery and Pub/Sub. That meant local testing was difficult, and teams who preferred to host outside GCP had limited options.

With Bucketeer Lite, we're changing that.

Now you can run Bucketeer in just a few minutes using Docker Compose, with Redis Streams for pub/sub and MySQL for data storage.
No GCP required — just Docker, MySQL, and Redis.

Feature flags are a powerful way to control how users experience your product. But over time, flags that were once useful can become technical debt if they aren't cleaned up properly. That's why we're excited to introduce Code References in Bucketeer, a new feature that helps you track where feature flags are used in your codebase.

Whether you're a developer managing dozens of toggles or an open-source contributor maintaining a large project, Code References gives you the visibility and tools to keep your flags clean, useful, and safe.

Reducing latency is crucial when delivering a better user experience. Bucketeer has just made a game-changing update for developers using its Node.js and Go server SDKs. This new version allows end-user evaluations to happen locally within the SDK, significantly reducing latency.

As our users base expands worldwide, Bucketeer noticed that latency was becoming an issue for our users who operate in different regions. In response, we decided to implement a multi-region architecture on Google Cloud Platform (GCP) to reduce latency and improve the overall performance of our platform.

Feature flags play a fundamental role in software development, permitting feature rollout and testing flexibility. Nevertheless, the selection of the appropriate feature flag ID to be applied is vital and often neglected. This tiny detail can result in a wide variety of user experience results and can even seriously change security.

Feature flags are a versatile tool in modern software development, allowing teams to control new feature rollouts, experiment with ideas, and mitigate the risks of deploying untested features to production.

However, avoiding these seven common mistakes is crucial to fully leverage their capabilities and avoid potential pitfalls.

As mentioned in the previous article, while introducing feature flags can provide significant benefits, there is a potential drawback of increased complexity in code and flag management.

Feature Flags are a software development tool that ensures an efficient, low-risk release cycle by enabling or disabling features in real-time without deploying new code.