Aaaaaand breathe.

We launched last week, and it went quite a bit better than we expected!

We've been inundated with support, feedback, potential customers and ideas for what to focus on next. However, pride comes before a fall, so we're being careful to keep focussed on talking to customers and building.

We spent the week putting together the final polish on the website before we went live. We've also been preparing the product ready to put it in the hands of early access customers, so we've been dotting the i's, crossing the t's and wrangling the experience to make it "just so".

What we shipped

• 🆕 You can now create incidents directly from messages and alerts.
• 🆕 Don't like our #incidents channel and want to name it #hamsters instead? You can now do so.
• 💅 Slack messages are now more nicely presented in the timeline, especially for links and user references.
• 💅 Durations appear more nicely formatted for incidents that stay open over 24 hours.
• 💅 Dashboard buttons don't resize weirdly on smaller screens any more - we hear you, Macbook Air crowd!
• 👷🏽‍♀️ We sped up our build and deployment pipeline. We can deploy code to production automatically in less than 5 minutes from merging a pull request. We hope Charity Majors would be proud.
• 👷🏽‍♀️ We made sure that we'd get paged and a Sentry error raised whenever something went wrong.
• 👷🏽‍♀️ We did a full security review of our application and cloud infrastructure.
• 👷🏽‍♀️ We made sure that we'd get paged and a Sentry error raised whenever something went wrong.
• 🐛 The incident bot no longer shows up as a participant on the incident homepage (we prefer to stay in the background).
• 🐛 The timestamp for the last update to the summary formats the date correctly.
• 🐛 Slack pins show up on the timeline in the order they were sent, rather than the order they were pinned.
• 🐛 The Settings dropdown used to stay open even when politely asked to close. We no longer ask politely.