Bucket 2025-02 Update — Event log, Secret features & Beta Remote Config
At Bucket, we're on a mission to help you build better products with feature flags. Here's a recap of what we shipped this month. 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. Learn more about Event log in this changelog post 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. Learn more about Secret features in this changelog post 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. Learn more about feature key naming conventions in this changelog post Custom avatar support Quality-of-life improvement: We now display company logos and user avatars in the UI. Learn more about this improvement in this changelog post 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. Learn more about Remote Config in this changelog post Join the beta on bucket.co Resources On trunk-based development (TBD): Following up on this introduction to TBD, Bucket's CTO and co-founder, Ron '@roncohen' Cohen, wrote a follow-up post to answer frequently asked questions on the topic. Why we use Clerk for auth: We prioritize craftsmanship at Bucket and, when we started building the auth feature — the first interaction you have with the product — we wanted to make it a great first-time experience. This is why we decided to use Clerk. How Bucket uses GitBook to deliver developer-first documentation: We recently sat down with Addison Schultz, Developer Relations Lead at GitBook, to discuss how it helps us create and maintain high-quality developer docs. 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 @bucketdotco on X for the latest updates. We'll be live on Product Hunt on March 18 — Get notified here We're crafting the feature management tool purpose-built for B2B SaaS companies. Happy shipping!

At Bucket, we're on a mission to help you build better products with feature flags.
Here's a recap of what we shipped this month.
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.
- Learn more about Event log in this changelog post
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.
- Learn more about Secret features in this changelog post
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.
- Learn more about feature key naming conventions in this changelog post
Custom avatar support
Quality-of-life improvement: We now display company logos and user avatars in the UI.
- Learn more about this improvement in this changelog post
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.
- Learn more about Remote Config in this changelog post
- Join the beta on bucket.co
Resources
- On trunk-based development (TBD): Following up on this introduction to TBD, Bucket's CTO and co-founder, Ron '@roncohen' Cohen, wrote a follow-up post to answer frequently asked questions on the topic.
-
Why we use Clerk for auth: We prioritize craftsmanship at Bucket and, when we started building the
auth
feature — the first interaction you have with the product — we wanted to make it a great first-time experience. This is why we decided to use Clerk. - How Bucket uses GitBook to deliver developer-first documentation: We recently sat down with Addison Schultz, Developer Relations Lead at GitBook, to discuss how it helps us create and maintain high-quality developer docs.
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 @bucketdotco on X for the latest updates. We'll be live on Product Hunt on March 18 — Get notified here
We're crafting the feature management tool purpose-built for B2B SaaS companies.
Happy shipping!