devops

Auto Added by WPeMatico

GitLab hauls in $268M Series E on 2.75B valuation

GitLab is a company that doesn’t pull any punches or try to be coy. It actually has had a page on its website for some time stating it intends to go public on November 18, 2020. You don’t see that level of transparency from late-stage startups all that often. Today, the company announced a huge $268 million Series E on a tidy $2.75 billion valuation.

Investors include Adage Capital Management, Alkeon Capital, Altimeter Capital, Capital Group, Coatue Management, D1 Capital Partners, Franklin Templeton, Light Street Capital, Tiger Management Corp. and Two Sigma Investments.

The company seems to be primed and ready for that eventual IPO. Last year, GitLab co-founder and CEO Sid Sijbrandij said that his CFO Paul Machle told him he wanted to begin planning to go public, and he would need two years in advance to prepare the company. As Sijbrandij tells it, he told him to pick a date.

“He said, I’ll pick the 16th of November because that’s the birthday of my twins. It’s also the last week before Thanksgiving, and after Thanksgiving, the stock market is less active, so that’s a good time to go out,” Sijbrandij told TechCrunch.

He said that he considered it a done deal and put the date on the GitLab Strategy page, a page that outlines the company’s plans for everything it intends to do. It turned out that he was a bit too quick on the draw. Machle had checked the date in the interim and realized that it was a Monday, which is not traditionally a great day to go out, so they decided to do it two days later. Now the target date is officially November 18, 2020.

Screenshot 2019 09 17 08.35.33 2

GitLab has the date it’s planning to go public listed on its Strategy page.

As for that $268 million, it gives the company considerable runway ahead of that planned event, but Sijbrandij says it also gives him flexibility in how to take the company public. “One other consideration is that there are two options to go public. You can do an IPO or direct listing. We wanted to preserve the optionality of doing a direct listing next year. So if we do a direct listing, we’re not going to raise any additional money, and we wanted to make sure that this is enough in that case,” he explained.

Sijbrandij says that the company made a deliberate decision to be transparent early on. Being based on an open-source project, it’s sometimes tricky to make that transition to a commercial company, and sometimes that has a negative impact on the community and the number of contributions. Transparency was a way to combat that, and it seems to be working.

He reports that the community contributes 200 improvements to the GitLab open-source product every month, and that’s double the amount of just a year ago, so the community is still highly active in spite of the parent company’s commercial success.

It did not escape his notice that Microsoft acquired GitHub last year for $7.5 billion. It’s worth noting that GitLab is a similar kind of company that helps developers manage and distribute code in a DevOps environment. He claims in spite of that eye-popping number, his goal is to remain an independent company and take this through to the next phase.

“Our ambition is to stay an independent company. And that’s why we put out the ambition early to become a listed company. That’s not totally in our control as the majority of the company is owned by investors, but as long as we’re more positive about the future than the people around us, I think we can we have a shot at not getting acquired,” he said.

The company was founded in 2014 and was a member of Y Combinator in 2015. It has been on a steady growth trajectory ever since, hauling in more than $426 million. The last round before today’s announcement was a $100 million Series D last September.

Powered by WPeMatico

Praqma puts Atlassian’s Data Center products into containers

It’s KubeCon + CloudNativeCon this week and in the slew of announcements, one name stood out: Atlassian . The company is best known as the maker of tools that allow developers to work more efficiently, and now as a cloud infrastructure provider. In this age of containerization, though, even Atlassian can bask in the glory that is Kubernetes, because the company today announced that its channel partner Praqma is launching Atlassian Software in Kubernetes (ASK), a new solution that allows enterprises to run and manage as containers its on-premise applications like Jira Data Center, with the help of Kubernetes.

Praqma is now making ASK available as open source.

As the company notes in today’s announcement, running a Data Center application and ensuring high availability can be a lot of work using today’s methods. With AKS and by containerizing the applications, scaling and management should become easier — and downtime more avoidable.

“Availability is key with ASK. Automation keeps mission-critical applications running whatever happens,” Praqma’s team explains. “If a Jira server fails, Data Center will automatically redirect traffic to healthy servers. If an application or server crashes Kubernetes automatically reconciles by bringing up a new application. There’s also zero downtime upgrades for Jira.”

AKS handles the scaling and most admin tasks, in addition to offering a monitoring solution based on the open-source Grafana and Prometheus projects.

Containers are slowly becoming the distribution medium of choice for a number of vendors. As enterprises move their existing applications to containers, it makes sense for them to also expect that they can manage their existing on-premises applications from third-party vendors in the same systems. For some vendors, that may mean a shift away from pre-server licensing to per-seat licensing, so there are business implications to this, but in general, it’s a logical move for most.

Powered by WPeMatico

Talk key takeaways from KubeCon 2019 with TechCrunch writers

The Linux Foundation’s annual KubeCon conference is going down at the Fira Gran Via exhibition center in Barcelona, Spain this week and TechCrunch is on the scene covering all the latest announcements.

The KubeCon/CloudNativeCon conference is the world’s largest gathering for the topics of Kubernetes, DevOps and cloud-native applications. TechCrunch’s Frederic Lardinois and Ron Miller will be on the ground at the event. Wednesday at 9:00 am PT, Frederic and Ron will be sharing with Extra Crunch members via a conference call what they saw and what it all means.

Tune in to dig into what happened onstage and off and ask Frederic and Ron any and all things Kubernetes, open-source development or dev tools.

To listen to this and all future conference calls, become a member of Extra Crunch. Learn more and try it for free.

Powered by WPeMatico

Harness hauls in $60M Series B investment on $500M valuation

Series B rounds used to be about establishing a product-market fit, but for some startups the whole process seems to be accelerating. Harness, the startup founded by AppDynamics co-founder and CEO Jyoti Bansal is one of those companies that is putting the pedal the metal with his second startup, taking his learnings and a $60 million round to build the company much more quickly.

Harness already has an eye-popping half billion dollar valuation. It’s not terribly often I hear valuations in a Series B discussion. More typically CEOs want to talk growth rates, but Bansal volunteered the information, excited by the startup’s rapid development.

The round was led by IVP, GV (formerly Google Ventures) and ServiceNow Ventures. Existing investors Big Labs, Menlo Ventures and Unusual Ventures also participated. Today’s investment brings the total raised to $80 million, according to Crunchbase data.

Bansal obviously made a fair bit of money when he sold AppDynamics to Cisco in 2017 for $3.7 billion and he could have rested after his great success. Instead he turned his attention almost immediately to a new challenge, helping companies move to a new continuous delivery model more rapidly by offering Continuous Delivery as a Service.

As companies move to containers and the cloud, they face challenges implementing new software delivery models. As is often the case, large web scale companies like Facebook, Google and Netflix have the resources to deliver these kinds of solutions quickly, but it’s much more difficult for most other companies.

Bansal saw an opportunity here to package continuous delivery approaches as a service. “Our approach in the market is Continuous Delivery as a Service, and instead of you trying to engineer this, you get this platform that can solve this problem and bring you the best tooling that a Google or Facebook or Netflix would have,” Basal explained.

The approach has gained traction quickly. The company has grown from 25 employees at launch in 2017 to 100 today. It boasts 50 enterprise customers including Home Depot, Santander Bank and McAfee.

He says that the continuous delivery piece could just be a starting point, and the money from the round will be plowed back into engineering efforts to expand the platform and solve other problems DevOps teams face with a modern software delivery approach.

Bansal admits that it’s unusual to have this kind of traction this early, and he says that his growth is much faster than it was at AppDynamics at the same stage, but he believes the opportunity here is huge as companies look for more efficient ways to deliver software. “I’m a little bit surprised. I thought this was a big problem when I started, but it’s an even bigger problem than I thought and how much pain was out there and how ready the market was to look at a very different way of solving this problem,” he said.

Powered by WPeMatico

CEO Jennifer Tejada just took PagerDuty public; we talked about the roadshow, the IPO and what comes next

PagerDuty debuted on the New York Stock Exchange today, and as we type, shares of the nine-year-old, San Francisco-based incident response software company are trading at nearly $39.

That’s up more than 60 percent above their IPO range of $24 per share, which was itself adjusted from the range of $21 to $23 that had been expected earlier and gives the company a valuation of close to $3 billion. That’s an awful lot for a company whose software helps technical teams at 11,000 companies spot problems with applications and respond to incidents. Though it’s growing quickly — revenue was up 48 percent last year — it still pulled in just $117.8 million in 2018. Meanwhile, its net loss widened last year, to $40.7 million from $38.1 million in 2017.

Certainly, its performance has to make the company’s investors — who last assigned the company a valuation of $1.3 billion back in September — very happy. Some of the VCs poised to win big if PagerDuty’s shares continue flying high include Andreessen Horowitz, which owned 18.4 percent of PagerDuty’s shares sailing into the IPO; Accel, which owned 12.3 percent; and Bessemer, which owned 12.2 percent. Other winners include Baseline Ventures (6.7 percent) and Harrison Metal (5.3 percent).

It’s also exciting for CEO Jennifer Tejada, a proven operator who was brought in to lead PagerDuty in 2016 and now becomes part of a small — but growing — club of women CEOs to take their tech companies public, including Katrina Lake of Stitch Fix and Julia Hartz of Eventbrite.

We talked with Tejada earlier today about the company’s big day. In addition to crediting company co-founders (and shareholders) Andrew Miklas and Baskar Puvanathasan, both of whom have since left the company, Tejada thanked PagerDuty co-founder Alex Solomon, who remains the company’s CTO. She also told us a little bit about what today has been like, and how the IPO changes things — and doesn’t. Our chat has been edited for length.

TC: First and foremost, how are you feeling?

JT: It’s been an incredible day. It’s been an incredible several months. You have to enjoy it when it’s going well.

TC: How does the vision for the company change now that it’s public? Have you been thinking ahead to possible acquisitions?

JT:  The vision doesn’t change. We intend to do exactly what we’ve been doing, which is to provide the best real-time operations platform available to companies as they undergo digital transformation to meet the growing demands of their customers. We think we’re [facing] an early and very large opportunity that will be available to us for a long time. So our job continues to be to build great products, stay close to our customers, expand regionally and continue doing what has allowed us to be a successful private company.

TC: You and I had talked about the challenges of retaining employees in San Francisco when we sat down together in November. It’s a battle for every local company. How do you keep employees beyond the lock-up period? How do you ensure they stay focused on performance and not your share price?

JT: I think that mindset of, ‘It’s all over when you go public,’ is kind of a Silicon Valley fable. If you look at the most successful SaaS companies on the planet, they’ve gained 10x, 20x, 30x their value post their IPO. I also think what employees look for ahead of their financial success is career success. Am I being developed and recognized and can I build my career at this company? And we’ve worked really hard to create those career opportunities for our employees who [I think see, as I do] the IPO like a racing boat pushing off the dock, across the starting line, and into the open ocean, where the next adventure awaits.

In the meantime, we’ve already lessened our reliance on [overheated job markets] by opening offices in Toronto and Atlanta and Seattle and London and Sydney, even while we’re still hiring in San Francisco and Seattle.

TC: Obviously, Lyft’s shares have been up and down, owing to short sellers. Have you been monitoring short interest? Are you at all concerned about investors driving the price sky high, then selling it on the way down?

JT: I haven’t even looked at the stock price in the last several hours .  .  . There are a lot of things outside of my control, and the free market is one of them.

TC: PagerDuty is rare in that is doesn’t have a dual-class structure, which can greatly empower leaders over everyone else associated with a company. Presumably, this is a great relief to your investors; I just wonder whether it was ever a consideration?

JT: I’m a little bit of a traditionalist. I’ve been around long enough to know how checks and balances work, and a single-class structure made sense for PagerDuty. Also, dual-class structures tend to emerge more when you have deeply involved founders, and though Alex is still very much a part of the business, PagerDuty’s other two founders have worked outside of the business for some time.

TC: You have plenty of operating experience, including previously running Keynote Systems, but you’ve never taken a company public. Were there ways in which you found the roadshow experience surprising?

JT: I was surprised by how fun it was! [Laughs.] When you have a great story, and a great partner helping you tell it — in my case that’s [PagerDuty CFO] Howard Wilson, who I’ve worked with for 10 years — it’s great. We had a great reception from investors. I loved our IPO team; our Top were both led by women and whenever I had a question, they [had the answer]. I also had this cocoon of experience surrounding me thanks to our board. If anyone tells you that [in this position] they are super comfortable, they’re either lying or [clueless] but I was very lucky. I also have a whole bunch of buddies who are CEOs [and other executives] in SaaS and I’ve been shaking them down for advice for months, so I felt well-prepared.

TC: What was some of the advice you received from those friends about how your life is about to change?

JT: Some of it was about the need to keep people focused and not get distracted, to remind everyone that this is a milestone, not the goal. [Some centered on] surrounding yourself with a great team and the importance of great investor relations, a function you don’t have as a private company but that can create huge value and provide support and understanding of the market.

One CEO said to just make sure you keep having fun, to try and stay “you,” to find joy in the same things as before. There will be stressful moments and tough questions — that’s true of any company that’s scaling — but I heard a lot of advice about just taking care of myself, including on the roadshow. In fact, there were a lot of really supportive notes and private tweets that, in a job that can feel lonely, made me feel not alone, and I’m very appreciative of that.

TC: People call IPOs just another funding event, but that’s kind of baloney, isn’t it? If you had to list the most meaningful moments in your life on a scale from 1 to 10, 1 being the most important, where might today fall? Would today be up there on that list?

JT: When I think of most meaningful moments, I think of the day my daughter was born, and my wedding. Another day that was very meaningful to me was when I approved our pledge to donate one percent [of PagerDuty’s equity, one percent of its product and one percent of employees’ time] to social impact. We did it a lot later in the game than some companies; our equity was already valuable. But we knew that it was going to create meaningful impact over time.

But yes, it is a gratifying day, especially for the co-founders who were pulling the idea together for PagerDuty a couple of years before they even launched it, and for employees who’ve been with the company for nearly as long and who turned down safer and higher-paying jobs along the way. Seeing their joy today — that is a memory that will be in my top 10 for sure.

Powered by WPeMatico

JFrog acquires Shippable, adding continuous integration and delivery to its DevOps platform

JFrog, the popular DevOps startup now valued at more than $1 billion after raising $165 million last October, is making a move to expand the tools and services it provides to developers on its software operations platform: it has acquired Shippable, a cloud-based continuous integration and delivery platform (CI/CD) that developers use to ship code and deliver app and microservices updates, and plans to integrate it into its Enterprise+ platform.

Terms of the deal — JFrog’s fifth acquisition — are not being disclosed, said Shlomi Ben Haim, JFrog’s co-founder and CEO, in an interview. From what I understand, though, it was in the ballpark of Shippable’s most recent valuation, which was $42.6 million back in 2014 when it raised $8 million, according to PitchBook data.  (And that was the last time it raised money.)

Shippable employees are joining JFrog and plan to release the first integrations with Enterprise+ this coming summer, and a full integration by Q3 of this year.

Shippable, founded in 2013, made its name early on as a provider of a containerized continuous integration and delivery platform based on Docker containers, but as Kubernetes has overtaken Docker in containerized deployments, the startup had also shifted its focus beyond Docker containers.

The acquisition speaks to the consolidation that is afoot in the world of DevOps, where developers and organizations are looking for more end-to-end toolkits, not just to help develop, update and run their apps and microservices, but to provide security and more — or at least, makers of DevOps tools hope they will be, as they themselves look to grow their margins and business.

As more organizations run ever more of their operations as apps and microservices, DevOps have risen in prominence and are offered both toolkits from standalone businesses as well as those whose infrastructure is touched and used by DevOps tools. That means a company like JFrog has an expanding pool of competitors that include not just the likes of Docker, Sonatype and GitLab, but also AWS, Google Cloud Platform and Azure and “the Red Hats of the world,” in the words of Ben Haim.

For Shippable customers, the integration will give them access to security, binary management and other enterprise development tools.

“We’re thrilled to join the JFrog family and further the vision around Liquid Software,” said Avi Cavale, founder and CEO of Shippable, in a statement. “Shippable users and customers have long enjoyed our next-generation technology, but now will have access to leading security, binary management and other high-powered enterprise tools in the end-to-end JFrog Platform. This is truly exciting, as the combined forces of JFrog and Shippable can make full DevOps automation from code to production a reality.”

On the part of JFrog, the company will be using Shippable to provide a native CI/CD tool directly within JFrog.

“Before most of our users would use Jenkins, Circle CI and other CI/CD automation tools,” Ben Haim said. “But what you are starting to see in the wider market is a gradual consolidation of CI tools into code repository.”

He emphasized that this will not mean any changes for developers who are already happy using Jenkins or other integrations: just that it will now be offering a native solution that will be offered alongside these (presumably both with easier functionality and with competitive pricing).

JFrog today has 5,000 paying customers, up from 4,500 in October, including “most of the Fortune 500,” with marquee customers including the likes of Apple and Adobe, but also banks, healthcare organizations and insurance companies — “conservative businesses,” said Ben Haim, that are also now realizing the importance of using DevOps.

Powered by WPeMatico

Idera acquires Travis CI

Travis CI, the popular Berlin-based open-source continuous integration service, has been acquired by Idera, a company that offers a number of SQL database management and administration tools for both on-premises and cloud applications. The move comes at a time when other continuous integration services, including the likes of Circle CI, seem to be taking market share away from Travis CI.

Idera, which itself is owned by private equity firm TA Associates, says that Travis is complementary to its current testing tools business and that the acquisition will benefit its current customers. Idera’s other tools in its Testing Tools division are TestRail, Ranorex and Kiuwan. “We admire the business value driven by Travis CI and look forward to helping more customers achieve better and faster results,” said Suhail Malhotra, Idera’s General Manager for Travis CI .

Idera clearly wants to move into the DevOps business, and continuous integration is obviously a major building block. This still feels like a bit of an odd acquisition, given that Idera isn’t exactly known for being on the leading edge of today’s technology (if it’s known at all). But Travis CI also brings 700,000 users to Idera, and customers like IBM and Zendesk, so while we don’t know the cost of the acquisition, this is a big deal in the CI ecosystem.

“We are excited about our next chapter of growth with the Idera team,” said Konstantin Haase, a founder of Travis CI, in today’s announcement. “Our customers and partners will benefit from Idera’s highly complementary portfolio and ability to scale software businesses to the next level. Our goal is to attract as many users to Travis CI as possible, while staying true to our open source roots and community.”

That’s pretty much what all founders write (or what the acquiring company’s PR team writes for them), so we’ll have to see how Idera will steer Travis CI going forward.

In his blog post, Haase says that nothing will change for Travis CI users. “With the support from our new partners, we will be able to invest in expanding and improving our core product, to have Travis CI be the best Continuous Integration and Development solution for software projects out there,” he writes and also notes that the Travis CI will stay open source. “This is who we are, this is what made us successful.”

Powered by WPeMatico

Why Blissfully decided to go all in on serverless

Serverless has become a big buzzword of late, and with good reason. It has the potential to completely alter how developers write code. They can simply write a series of event triggers, while letting the cloud vendor worry about providing whatever amount of compute resources are required to complete the job. It represents a huge shift in how programs are developed, but it’s been difficult to find companies who were built from the ground up using this methodology because it’s fairly new.

Blissfully, a startup that helps customers manage their Software-as-a-Service usage inside their companies, is one company that decided to do just that. Aaron White, co-founder and CTO, says that when he was building early versions of Blissfully, he found he needed quick bursts of compute power to deliver a list of all the SaaS products an organization is using.

He figured he could set aside a bunch of servers to provide that burst of power as needed, but that would have required a ton of overhead on his part to manage. At this point, he was a lone programmer trying to prove his SaaS management idea was even possible. As he looked at the pros and cons of serverless versus traditional virtual machines, he began to see serverless as a viable approach.

What he learned along the way was that serverless offers many advantages to a company with a bursty approach like Blissfully, scaling up and down as needed. But it isn’t perfect and there are issues around management and tooling and handling the pros and cons of that scaling ability that he had to learn about on the fly, especially coming in as early as he did with this approach.

Serverless makes sense

Blissfully is a service where serverless made a lot of sense. It wouldn’t have to manage or pay for servers it wasn’t using. Nor would it have to worry about the underlying infrastructure at all. That would be up to the cloud provider, and it would only pay for the bursts as they happened.

Serverless is actually a misnomer, in that it doesn’t mean there are no servers. It actually means you don’t have to set up servers in order to run your program, which is a pretty mind-blowing transformation. In traditional programming you have to write your code and set up all the underlying hardware ahead of time, whether it’s in your data center or in the cloud. With serverless, you just write the code and the cloud provider handles all of that for you.

The way it works in practice is that programmers set up a series of event triggers, so when a certain thing happens, the cloud provider sees this and provides the necessary resources on demand. Most of the cloud vendors are offering this type of service, whether AWS Lambda, Azure Functions or Google Functions.

At this point, White began to think about serverless as a way of freeing him from thinking about managing and maintaining infrastructure and all that entailed. “I started thinking, let’s see how far we can take this. Can we really do absolutely everything serverless, and if so that reduces a ton of traditional DevOps-style work you have to do in practice. There’s still plenty, but that was the thinking at the beginning,” he said.

Overcoming obstacles

But there were issues, especially getting into serverless as early as he did. For starters, White needed to find developers who could work in this fashion, and in 2016 when it launched there weren’t a large number of people out there with serverless skills. White said he wasn’t looking for direct experience so much as people who were curious to learn and were flexible enough to deal with new technology, regardless of how Blissfully implemented that.

Once he figured out the basics, he needed to think about how this would work structurally. “Part of the challenge is figuring out where do you draw the boundaries between different serverless functions? How do you think about how much you want to overload the capability of one function versus another? How do you want to split it up? You could go way too specific, and you can of course, go way too broad. So there’s a lot of judgement calls to be made in terms of how you want to split your code base to work in this way,” he said.

The other challenge he faced going with a serverless approach so early was a dearth of tooling around it. White found Serverless, Inc. right way, which helped him with a basic framework for developing, but he lacked good logging tools and says that the company still struggles with this even now. “DevOps doesn’t go away. This is still running on a server somewhere (even if you don’t control that) and you will run into issues.” One such issue he calls a “cold start issue.”

Getting the resources right

Blissfully uses AWS Lambda, and as their customers require resources, it isn’t as though Amazon has a set of dedicated resources set aside waiting for such an event. If it needs to start servers cold, that could result in latency. To compensate for that, Blissfully runs a job that pings Lambda continually, so that it’s always ready to run the actual application, and there isn’t a lag time related to starting from scratch.

The other issue could be the opposite problem. You can scale much faster than you’re ready to deal with and that can be a problem for a small team. He says in that case, you want to put a limiter on the speed of the calls so you don’t end up spending more than you can afford, and it doesn’t scale beyond your team’s ability to manage it, “I think, in some ways, this actually accelerates you running into problems where you would normally be larger scale before you really had to think about them,” White said.

The other piece is that once Lambda gets everything going, it can move data faster than your external APIs can handle, and that could require limiters to actually slow things down. “I never had that problem in the past where I was provisioning so many computational resources that Google was yelling at me for being too fast. Being too fast for Google takes a lot of effort, but it doesn’t take a lot of effort with Lambda. When it does decide to spool up whatever resources, you can do some serious outbound damage to other APIs.” That meant he and his team actually had to think very early on about building sophisticated rate-limiting schemes.

As for costs, White estimates that his costs are much lower now that he has the service built and in place. “Our costs are so low right now, and far lower than if we had server-based infrastructure. Our computational pattern is very bursty.” That’s because it re-parses the SaaS database once a day or when the customer first signs up, and in between, usage is fairly low beyond interacting with the data.

“So for us that was perfect for serverless because I don’t really need to keep capacity around that would be pure waste.”

Powered by WPeMatico

Sonatype raises $80 million to build out Nexus platform

Sonatype, a cybersecurity-focused open-source company, has raised $80 million from investment firm TPG.

The company said the financing will help extend its Nexus platform, which it touts as an enterprise ready repository manager and library, which among other things tracks code and helps to keep everything in the devops pipeline up-to-date and secure.

It’s that kind of technology that Sonatype says can prevent another Equifax -style breach of over 147 million consumers’ data. Earlier this year, the company found over dozens of Fortune Global 100 companies that downloaded outdated and vulnerable versions of Apache Struts, which Equifax failed to patch or update.

Sonatype’s chief executive Wayne Jackson his company can help prevent those type of breaches.

“We monitor literally millions of open source commits per day,” he told TechCrunch. “Last year hundreds of billions of components were downloaded by software developers, 12 percent of which had known security defects.”

The funding will go to extend the company’s Nexus platform, Jackson said.

The company said it’s had an 81 percent increase in year-over-year sales in the first-half of the year, and 1.5 million users added to its flagship Nexus platform since January. In all, the company has more than 10 million software developers and 1,000 enterprises on Nexus worldwide.

Sonatype’s last round of funding was in 2016, led by Goldman Sachs, snagging $30 million.

Powered by WPeMatico

Atlassian acquires OpsGenie, launches Jira Ops for managing incidents

Atlassian today announced the first beta of a new edition of its flagship Jira project and issue tracking tool that is meant to help ops teams handle incidents faster and more efficiently.

Jira Ops integrates with tools like OpsGenie, PagerDuty, xMatters, Statuspage, Slack and others. Many teams already use these tools when their services go down, but Atlassian argues that most companies currently use a rather ad hoc approach to working with them. Jira Ops aims to be the glue that keeps everybody on the same page and provides visibility into ongoing incidents.

Update: after Atlassian announced Jira Ops, it also announced that it has acquired OpsGenie for $295 million.

This is obviously not the first time Atlassian is using Jira to branch out from its core developer audience. Jira Service Desk and Jira Core, for example, aim at a far broader audience. Ops, however, goes after a very specific vertical.

“Service Desk was the first step,” Jens Schumacher, Head of Software Teams at Atlassian, told me. And we were looking at what are the other verticals that we can attack with Jira.” Schumacher also noted that Atlassian built a lot of tools for its internal ops teams over the years to glue together all the different pieces that are necessary to track and manage incidents. With Jira Ops, the company is essentially turning its own playbook into a product.

In a way, though, using Jira Ops adds yet another piece to the puzzle. Schumacher, however, argues that the idea here is to have a single place to manage the process. “The is that when an incident happens, you have a central place where you can go, where you can find out everything about the incident,” he said. “You can see who has been paged and alerted; you can alert more people if you need to right from there; you know what Slack channel the incident is being discussed in.”

Unlike some of Atlassian’s other products, the company doesn’t currently have any plans to launch a self-hosted version of Jira Ops. The argument here is pretty straightforward: if your infrastructure goes down, then Jira Opes could also go do down — and then you don’t have a tool for managing that downtime.

Jira Ops is now available for free for early access beta users. The company expects to launch version 1.0 in early 2019. By then Atlassian will surely also have figured out a pricing plan, something it didn’t announce today.

Powered by WPeMatico