For the first time in years we lost customer data, here's how it happened.

We've upgraded our GitHub integration to a new GitHub App.

We’ve been secretly using it ourselves on our staging servers for a while, but now we finally get to show you the updated user interface for AppSignal.com!

In order to tackle the battle between productivity and providing service to our customers, we invented "Koos": our weekly support rotation.

We started AppSignal four years ago as a side-project at a software development agency. At the time, we only had a vague idea of what AppSignal would become. Four years later we have learned a lot of things about becoming a product business.

At AppSignal, we love stroopwafels. We’ve shipped over 10,000 of them to customers, friends and conferences. If you work at a tech company and have had a stroopwafel at the office, chances are it came from us. Here's how to eat them.

The team behind AppSignal has been active in the Ruby on Rails community since 2005. We started AppSignal in 2012 to scratch our own itch, and these are our learnings.

The Ruby on Rails Podcast is adding a new segment, presented by AppSignal. It's called Shipped It! and is about managing and improving your application after it's shipped.

Like many services, we offer a 30 day free trial. A credit card is only needed after the trial ends, but we generally know within a week who will become a paying customer. Here’s what we’ve learned about recognizing a future customer.

read more

Last year we wrote about our approach to handling European VAT rules with Stripe. I’m happy to report that Stripe has now implemented a much better tax handling system. Meanwhile we also learned some more about properly filing VAT tax returns. Let’s see how we can use this new knowledge to achieve a better result with less code.

read more

Are you a European company offering subscription based services, while using Stripe to handle payments? Right… VAT. Here’s how we fixed it.

read more

Yesterday around 3pm CEST we had an issue with one of our API endpoints, resulting in 401 (“Unauthorized”) response codes, which in turn disabled the gems of some of our customers. We’re still investigating and will release an updated post-mortem once we know all the details. For now we would like to explain what happened and how sites were affected.

read more