I’m thrilled to announce that Erik Hughes has joined Bucket as a Full Stack engineer!

I’m thrilled to welcome Alex Reid to Bucket.

In the SaaS industry, we’ve largely adopted agile development as our preferred methodology for releasing software. Scoping down and time-boxing features ensures that product teams release often and don’t waste months on a grand feature that ultimately doesn’t work.

I’m very pleased to announce that Peter Müller has joined Bucket!

A feature can be anything in your product, big and small. It can be user facing, like a key interaction in the UI, a minor preference-toggle or even a background job. Features are different and have varying usage patterns.

10 months ago, I released Bucket 1.0, which I was bootstrapping at the time. I got a handful of early customers (<3), but it quickly became obvious that my (somewhat dubious) code wouldn’t be able to handle the load and that Bucket had to mature in order to serve its customers going forward.

Building and shipping features is hard. Getting customers to use them is even harder. Bucket empowers software teams with a repeatable approach to shipping features that customers crave.

Please see our new Jobs page.

We’ve just moved to our new domain! 🥳 From now on, you can find us at bucket.co, on Twitter @bucketdotco, and on email at hello@bucket.co.

It’s been about six months since Bucket 1.0 was released. Back then, I was a solo founder trying to work my way towards a Minimum Viable Product, and my first customers. I did get customers, but, soon after launching, I found myself knee-deep in operations and maintenance. Bucket was suddenly receiving millions of events per day and the application was struggling to keep up with the load. I managed to fix the bottlenecks, but I didn’t have any time for new features or marketing efforts - and new issues kept bubbling up.