Feature flags have become essential for modern software development, enabling teams to deploy code safely, test features with specific user segments, and roll out changes gradually. To address the challenge of vendor lock-in when switching between different feature flag providers, we're excited to announce OpenFeature support for the Bucketeer Go SDK.
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.
As feature flag management becomes increasingly crucial for modern software development, having quick access to comprehensive documentation can make the difference between smooth deployments and troubleshooting headaches. Today, I'm excited to share how I built a locally running Model Context Protocol (MCP) server that brings Bucketeer's entire documentation directly into AI assistants like Claude and Cursor.
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.
This blog post will show you how to build flag settings depending on other flags. It will also clarify the difference between "prerequisite" and "targeting with other flags," which will provide you with a more flexible and complex feature flag rollout strategy.
This blog post will guide you through the process of setting up a development environment for Bucketeer using a dev container. A dev container provides a consistent and isolated environment, ensuring that all developers have the necessary tools and dependencies to build and run the project.
Almost two years ago, we made our in-house product, Bucketeer, open-source, starting with version 0.1.0. Since then, through extensive use across multiple projects, we have established its stability and reliability, leading us to the milestone release of version 1.0.
Feature flags contain various elements such as ID, name, tag, etc., and managing them can be hard sometimes. As the number of feature flags increases, finding the desired information using a simple list display becomes challenging. Bucketer provides a search filter function that allows you to search based on ID, name, etc., and filter by tags, administrator, etc. However, there are many different ways to search for feature flags, and various patterns exist. Therefore, setting different search conditions each time to search for information can be tedious and waste time and effort. In this article, we will introduce a feature that allows you to save search condition shortcuts, which can be helpful in such situations.
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.