Bucket 2025-02 Update - Event log, Secret features, Beta Remote Config & Product Hunt

by

Meow there! The team has been hard at work this month to help you build better products with feature flags.


Here's a recap of what we recently shipped at . Note: We'll be live here on March 18 —


# What Bucket shipped in February 2025

  • Improved Event log

  • Secret features

  • Custom feature key naming convention

  • Custom avatar support

  • Beta Remote Config

## Improved Event log


We've revamped the debugger: introducing the Event log.


You can now see event data sent to Bucket – evaluate, check, user, company, and track – and slice it with filters. This makes it easier to get started and debug data issues.


## Secret features


We've made it possible to mark features as "secret" on Bucket.


This means you can use a feature on your backend and ensure that the feature key is never revealed to any users.


## Custom feature key naming convention


You can now define your feature key naming convention when creating a new feature.

SNAKE_UPPER_CASE, camelCase, kebab-lower-case (default), or else... You decide.


## Custom avatar support


Quality-of-life improvement: We now display company logos and user avatars in the UI.


## Beta Remote Config


Last but not least, we’ve shipped a beta release, introducing remote feature configuration to Bucket — a dynamic and flexible approach to configuring feature behaviour outside of your app without redeployments.


# One more thing


That's almost it for this month. There's one more thing.


We'll run our first-ever launch week on March 17-21. Follow us for the latest updates. We'll be live here on March 18 —


We're crafting the feature management tool purpose-built for B2B SaaS companies.


Happy shipping!

106 views

Add a comment

Replies

Best

Cool updates. I'm curious / not super familiar with Bucket - what do intend people to use secret features for?

Excited to see what y'all launch on Launch Week!

 thank you, Rajiv — your words made our day!

re: secret features. Good question! When creating a feature in Bucket, it becomes available through SDKs and public API using a publishable key. In some cases, you may want to limit the feature access and keep it backend-only. This adds a layer of security when working on the next big thing :)

Better with the constant updates and keep all of us aware about the main features of the product, thanks.

thanks!

Congrats on the updates, great work

thank you! This team is cooking