Today we announced our official Beta Launch and Series A $6.5M financing round.
Back in December of last year we set out to build a revolutionary platform for DevOps teams. We envisioned a platform where team members were always connected, could use any device they brought to the party, and most importantly help each other solve problems regardless of physical location or time of day. In short, we wanted to give some life back to the people that give up huge chunks of their lives to keep the business running.
People asked me when pitching the company back in December, why hasn’t this problem been solved before? Other parts of the business have been using synchronous and asynchronous collaborations systems for years. Salesforces use Salesforce.com, and Software Engineers use Rally or Jira. So what is different about DevOps?
It’s a great question, and the answer is deceivingly obvious once you think about it. As InfoWorld defines it, DevOps is a software development method that stresses collaboration and integration between developers and operations professionals. Unofficially, DevOps is a 24x7x365 days a year job. While other groups can work together through available platforms during business hours, DevOps needs to leverage team members at night and on the weekend, regardless of physical location.
Obviously, the platform for these teams has to be inherently mobile. Not add-on mobile, but mobile from day one. The problem has never changed. The reason the problem has not been solved before now is simply because a constant in the equation has changed: mobile devices are now ubiquitous and powerful. Now different team members can participate and help from their desktop, their Android Phone, or their iOS device. Leveraging a team requires symmetric access to information by all team members. That could not exist before now.
Over the last 9 months we have built exactly the platform we envisioned back in December, but more importantly, the platform we wished we had back in 2001 when our first company Raindance Communications went public. Simply put, we were inundated by the reality of supporting a service that ran in three datacenters, had thousands of servers and not enough people (is there ever enough people?). Any problem that happened after 10pm at night took all night to solve. GigaOm recently addressed this issue and concluded that DevOps success relied on effective communications and small teams.
As it turns out, being alerted to the problem was only one aspect of a much larger problem. PagerDuty is already hard at work on solving this one. But being connected and being aware of the state of things were as big an issue. When a new team member gets involved in a firefight, you want that team member to hit the ground running. That does not happen with alert-only solutions.
We are super excited to remove the veil from what we have been working on. Over the coming weeks, we will keep you up to date on the progress of the open beta as well as describe what we learned about the way DevOps teams are solving problems in our Alpha Program.