About Protocol Enterprise

‘It’s not OK’: Elastic takes aim at AWS, at the risk of major collateral damage

Elastic's long-running dispute with AWS entered a new chapter last week with big changes to two of its open-source projects. AWS now plans to take those projects under its wing.

‘It’s not OK’: Elastic takes aim at AWS, at the risk of major collateral damage

"I don't know why this is surprising to people," Elastic CEO Shay Banon said in an interview with Protocol.

Photo: Michael Nagle/Getty Images

Fed up with what he sees as unfair competition from AWS, Elastic CEO Shay Banon felt he had no choice but to restrict the way third parties can use two important open-source projects developed by his company. Yet much of enterprise tech thinks he just threw the baby out with the bathwater.

Last Thursday, Elastic published a blog post — curiously titled "Doubling down on open, Part II" — announcing that Elasticsearch and Kibana, two widely used open-source projects in enterprise tech, would no longer be available under the permissive Apache 2.0 license. Instead, all subsequent releases to those projects will only be available under either a controversial new license known as the SSPL, or the Elastic License, both of which were designed to make it difficult for cloud companies to sell managed versions of the open-source projects they're applied to.

Elastic has never tried to hide its disdain for AWS, a feud that dates back to the 2015 launch of Amazon Elasticsearch Service. The introduction of that AWS service, a managed version of the Elasticsearch open-source project, was arguably the low point in the strained history between enterprise tech companies based around open-source projects and AWS.

It is, of course, completely legal for AWS — or any company — to build its own service around any permissively licensed open-source project. In fact, AWS reacted to Elastic's decision Thursday afternoon by announcing plans to fork the two projects, or to take them in a new AWS-led direction, under the same permissive Apache 2.0 license.

But a generation of open-source enterprise companies (and their venture capitalist backers) see AWS as an anticompetitive gorilla stomping on their opportunity to monetize innovative software, and Elastic took particular offense to AWS' use of the Elasticsearch trademark.

"I don't know why this is surprising to people," Banon said in an interview with Protocol. "I'm making a stand here. I'm drawing a line and saying this is not OK."

However, critics argued Banon's decision paved the way for Amazon to turn its open-source distribution of the Elasticsearch project, the Open Distro for Elasticsearch, into a proper fork. The move had enormous potential to disappoint contributors to the Elasticsearch and Kibana projects who expected their work would be freely available to the community, only for that promise to be discarded once it was no longer economically comfortable for its corporate backer.

"Choosing to fork a project is not a decision to be taken lightly, but it can be the right path forward when the needs of a community diverge — as they have here. An important benefit of open-source software is that when something like this happens, developers already have all the rights they need to pick up the work themselves, if they are sufficiently motivated," AWS said in the post announcing its decision.

After AWS published its decision, Banon issued an additional statement: "When we announced the change, we sadly expected this. This what made it so hard. But I am also relieved. Relieved we are free to focus on products vs. battle abuse. Relieved that I can trust our community will see through this misinformation & confusion."

While legal experts believe Banon has a solid trademark case against AWS, the licensing changes clearly did not deter AWS, and they have no effect on companies like Microsoft and Google Cloud, which have signed deals with Elastic.

"They are aiming to hit Amazon, but what they are doing is throwing a boulder at Amazon floating peacefully in a pond of an ecosystem," said VM (Vicky) Brasseur, a corporate strategist and former vice president of the Open Source Initiative. "I don't think it's worth it. They are going to destroy their ecosystem."

Quite a stretch

Elasticsearch is an open-source search engine first released in 2010 by Banon, who would go on to co-found Elastic in 2012. It is often used alongside two other Elastic open-source projects, Logstash and Kibana, to form the "ELK stack," which is well known in enterprise tech circles among companies that want to build search capabilities for their websites while also using those search capabilities to pursue their system logs for events such as errors.

Customers can buy a managed version of this stack called Elastic Cloud, which runs on all three major U.S. cloud providers, or manage it themselves on either their own hardware or clouds. But there are also some companies and individual users that are happy to take on the burden of managing the open-source version.

The new licensing changes, however, mean that companies using this open-source version must now agree that they won't use Elasticsearch and Kibana as part of their own cloud service, and that has raised questions. The changes are directed at big cloud providers, but there are many small and medium businesses that could be using the open-source projects as part of their own software stack in a way that may or may not be infringing on the new licenses, depending on the quality of the lawyers involved in any dispute.

"If you're using them, please look at how they fit into your software supply chain, look at how this is going to impact your product and your projects. Don't just overlook it and assume it's nothing," Brasseur said.

Banon said "the vast majority" of Elasticsearch and Kibana users will not be affected by these licensing changes, but he acknowledged there will be valid concerns felt inside the Elasticsearch community.

"I'm very worried about [alienating community members]; this is why we didn't make this change lightly," Banon said. "Regardless of how much we try to relax our user base, some people will end up being alienated, and others, which I'm more worried about, might be fed by FUD," the tried-and-true "fear, uncertainty and doubt" campaigns that have been part of enterprise tech marketing for decades.

Brasseur agreed that the licensing move comes with significant risks to Elastic's goodwill inside its community of contributors.

"They're now taking these contributions, which were given by external contributors freely and openly with the assumption that their contributions would be freely and openly available, and now they're locking them up behind a non-open license," she said. "It's perfectly fine to do that. But you better be talking to your community up front and telling them how and why, and then I think it's probably wise for you to be then compensating people for the value that they have provided to your company. Otherwise, you're just using them."

Off the mark

The root cause of the dispute between Elastic and AWS mostly centers on the trademark issue, which prompted a lawsuit from Elastic in 2019 that continues to work its way through the court system.

The use of that trademark caused a great deal of confusion among Elastic's customers, according to Banon, who believed that the AWS service was the result of collaboration between the two companies when it was really just a repackaging of the open-source Elasticsearch project. A tweet from Amazon CTO Werner Vogels calling the new service a "partnership" certainly did not help.

"To modify Elastic's product and call it Amazon Elasticsearch is, in my view, a pretty clear trademark infringement," said Pamela Chestek, a trademark attorney and former intellectual property attorney at IBM's Red Hat.

But when AWS launched the Open Distro for Elasticsearch in 2019, the trademark dispute also turned into a dispute over code.

AWS charged that Elastic was co-mingling open-source code with proprietary code, making it hard for users to know if they required a paid subscription or not to use certain features. The Open Distro was pitched as a way to get the benefits of open-source Elasticsearch with the features needed to make it work properly, and it was released under the Apache 2.0 license.

Elastic denied that it was trying to confuse its users, and alleged that AWS was using third-party code in that distribution that was a copy of its own work.

"Recently, we found more examples of what we consider to be ethically challenged behavior. We have differentiated with proprietary features, and now we see these feature designs serving as 'inspiration' for Amazon, telling us their behavior continues and is more brazen," Banon said in a blog post Tuesday.

License to print money

As with all disputes in enterprise software, this one really comes down to money. Elastic doesn't make money when people use the open-source versions of its software, and all things considered, would prefer they pay for the licensed versions.

From the outside it's hard to pinpoint exactly how much money AWS has made from its Elasticsearch services, but it's a non-zero amount: AWS likely recorded more than $12 billion in overall cloud revenue during the fourth quarter of 2020. At the same time, Elastic's own cloud services are growing quite strongly as the world shifts to cloud-based software.

Elastic revenue rose 43% in its most recent quarter, with SaaS subscription revenue for Elastic Cloud driving much of that growth. Over the course of 2020, Banon wasn't worried enough about the competitive threat from AWS to mention it during the quarterly conversations with the financial community.

In fact, in answering a question about competition with the cloud providers from a financial analyst during Elastic's December earnings conference, Banon said: "We feel like we're ahead of the pack on all three when it comes to the maturity and the future readiness of our products, and that's reflected, I think, by the usage of it." Elastic's stock has more than doubled in the last 12 months.

"We're doing well as a business, and I'm not going to sit here and apologize for it," Banon said. "It's not about doing well or not doing well as a business, it's about doing what's right."

In the aftermath of the licensing changes, however, what's "right" for Elasticsearch users, open-source contributors, and Elastic shareholders takes on different meanings, depending on where you sit.

"I would have been a lot more sympathetic to Elastic if they said, 'look, these choices we made when we were very young, they aren't working out for us anymore. They aren't working out with our business plan,'" Chestek said. "A lot of people would be unhappy with that, but it would be honest."

Update: This article was updated at 3:45 p.m. PT to include a statement from Elastic following the release of AWS' blog post.

Entertainment

The (gaming) clones never stopped attacking

Clones keep getting through app review despite App Store rules about copying. It's a sign of the weaknesses in mobile app stores — and the weakness in Big Tech’s after-the-fact moderation approach.

Clones aren't always illegal, but they are widely despised.

Image: Disney

Two of the most fundamental tenets of the mobile gaming market:

  1. Free always wins.
  2. No good gaming idea is safe from copycats.

In combination, these two rules help produce what the industry calls a clone. Most often, clones are low-effort, ripped-off versions of popular games that monetize in not-so-savory fashion while drawing in players with a price tag of zero.

Keep Reading Show less
Nick Statt
Nick Statt is Protocol's video game reporter. Prior to joining Protocol, he was news editor at The Verge covering the gaming industry, mobile apps and antitrust out of San Francisco, in addition to managing coverage of Silicon Valley tech giants and startups. He now resides in Rochester, New York, home of the garbage plate and, completely coincidentally, the World Video Game Hall of Fame. He can be reached at nstatt@protocol.com.
Sponsored Content

A CCO’s viewpoint on top enterprise priorities in 2022

The 2022 non-predictions guide to what your enterprise is working on starting this week

As Honeywell’s global chief commercial officer, I am privileged to have the vantage point of seeing the demands, challenges and dynamics that customers across the many sectors we cater to are experiencing and sharing.

This past year has brought upon all businesses and enterprises an unparalleled change and challenge. This was the case at Honeywell, for example, a company with a legacy in innovation and technology for over a century. When I joined the company just months before the pandemic hit we were already in the midst of an intense transformation under the leadership of CEO Darius Adamczyk. This transformation spanned our portfolio and business units. We were already actively working on products and solutions in advanced phases of rollouts that the world has shown a need and demand for pre-pandemic. Those included solutions in edge intelligence, remote operations, quantum computing, warehouse automation, building technologies, safety and health monitoring and of course ESG and climate tech which was based on our exceptional success over the previous decade.

Keep Reading Show less
Jeff Kimbell
Jeff Kimbell is Senior Vice President and Chief Commercial Officer at Honeywell. In this role, he has broad responsibilities to drive organic growth by enhancing global sales and marketing capabilities. Jeff has nearly three decades of leadership experience. Prior to joining Honeywell in 2019, Jeff served as a Partner in the Transformation Practice at McKinsey & Company, where he worked with companies facing operational and financial challenges and undergoing “good to great” transformations. Before that, he was an Operating Partner at Silver Lake Partners, a global leader in technology and held a similar position at Cerberus Capital LP. Jeff started his career as a Manufacturing Team Manager and Engineering Project Manager at Procter & Gamble before becoming a strategy consultant at Bain & Company and holding executive roles at Dell EMC and Transamerica Corporation. Jeff earned a B.S. in electrical engineering at Kansas State University and an M.B.A. at Dartmouth College.
Entertainment

Beat Saber, Bored Apes and more: What to do this weekend

Don't know what to do this weekend? We've got you covered.

Images: Ross Belot/Flickr; IGBD; BAYC

This week we’re listening to “Harvest Moon” on repeat; burning some calories playing Beat Saber; and learning all about the artist behind the goofy ape pics that everyone (including Gwyneth Paltrow?) is talking about.

Neil Young: Off Spotify? No problem.

Neil Young removed his music from Spotify this week, but countless recordings are still available on YouTube, including this 1971 video of him performing “Heart of Gold” in front of a live studio audience, complete with some charming impromptu banter. And while you’re there, scroll down and read a few of the top-rated comments. I promise you won’t be disappointed.

'Archive 81': Not based on a book, but on a podcast!

Netflix’s latest hit show is a supernatural mystery horror mini-series, and I have to admit that I was on the fence about it many times, in part because the plot just often didn’t add up. But then the main character, Dan the film buff and archivist, would put on his gloves, get in the zone, and meticulously restore a severely damaged, decades old video tape, and proceed to look for some meaning beyond the images. That ritual, and the sentiment that we produce, consume and collect media for something more than meets the eye, ultimately saved the show, despite some shortcomings.

'Secrets of Sulphur Springs': Season 2 is out now

If you’re looking for a mystery that's a little more family-friendly, give this show about a haunted hotel, time travel, and kids growing up in a world that their parents don’t fully understand a try. Season 2 dropped on Disney+ this month, and it not only includes a lot more time travel mysteries, but even uses the show’s time machine to tackle subjects as serious as reparations.

The artist behind those Bored Apes

Remember how NFTs are supposed to generate royalties with every resale, and thus support artists better than any of their existing revenue streams? Seneca, the artist who was instrumental in creating those iconic apes for the Bored Ape Yacht Club, wasn’t able to share details about her compensation in this Rolling Stone profile, but it sure sounds like she is not getting her fair share.

Beat Saber: Update incoming

Years later, Beat Saber remains my favorite VR game, which is why I was very excited to see a teaser video for cascading blocks, which could be arriving any day now. Time to bust out the Quest for some practice time this weekend!

Correction: Story has been updated to correct the spelling of Gwyneth Paltrow's name. This story was updated Jan. 28, 2022.


Janko Roettgers

Janko Roettgers (@jank0) is a senior reporter at Protocol, reporting on the shifting power dynamics between tech, media, and entertainment, including the impact of new technologies. Previously, Janko was Variety's first-ever technology writer in San Francisco, where he covered big tech and emerging technologies. He has reported for Gigaom, Frankfurter Rundschau, Berliner Zeitung, and ORF, among others. He has written three books on consumer cord-cutting and online music and co-edited an anthology on internet subcultures. He lives with his family in Oakland.

Boost 2

Can Matt Mullenweg save the internet?

He's turning Automattic into a different kind of tech giant. But can he take on the trillion-dollar walled gardens and give the internet back to the people?

Matt Mullenweg, CEO of Automattic and founder of WordPress, poses for Protocol at his home in Houston, Texas.
Photo: Arturo Olmos for Protocol

In the early days of the pandemic, Matt Mullenweg didn't move to a compound in Hawaii, bug out to a bunker in New Zealand or head to Miami and start shilling for crypto. No, in the early days of the pandemic, Mullenweg bought an RV. He drove it all over the country, bouncing between Houston and San Francisco and Jackson Hole with plenty of stops in national parks. In between, he started doing some tinkering.

The tinkering is a part-time gig: Most of Mullenweg’s time is spent as CEO of Automattic, one of the web’s largest platforms. It’s best known as the company that runs WordPress.com, the hosted version of the blogging platform that powers about 43% of the websites on the internet. Since WordPress is open-source software, no company technically owns it, but Automattic provides tools and services and oversees most of the WordPress-powered internet. It’s also the owner of the booming ecommerce platform WooCommerce, Day One, the analytics tool Parse.ly and the podcast app Pocket Casts. Oh, and Tumblr. And Simplenote. And many others. That makes Mullenweg one of the most powerful CEOs in tech, and one of the most important voices in the debate over the future of the internet.

Keep Reading Show less
David Pierce

David Pierce ( @pierce) is Protocol's editorial director. Prior to joining Protocol, he was a columnist at The Wall Street Journal, a senior writer with Wired, and deputy editor at The Verge. He owns all the phones.

Workplace

Mental health at work is still taboo. Here's how to make it easier.

Tech leaders, HR experts and organizational psychologists share tips for how to destigmatize mental health at work.

How to de-stigmatize mental health at work, according to experts.

Illustration: Christopher T. Fong/Protocol

When the pandemic started, HR software startup Phenom knew that its employees were going to need mental health support. So it started offering a meditation program, as well as a counselor available for therapy sessions.

To Chief People Officer Brad Goldoor’s surprise, utilization of these benefits was very low, starting at about a 10% take rate and eventually weaning off. His diagnosis: People still aren’t fully comfortable opening up about mental health, and they’re especially not comfortable engaging with their employer on the topic.

Keep Reading Show less
Michelle Ma

Michelle Ma (@himichellema) is a reporter at Protocol, where she writes about management, leadership and workplace issues in tech. Previously, she was a news editor of live journalism and special coverage for The Wall Street Journal. Prior to that, she worked as a staff writer at Wirecutter. She can be reached at mma@protocol.com.

Fintech

Robinhood's regulatory troubles are just the tip of the iceberg

It’s easiest to blame Robinhood’s troubles on regulatory fallout, but its those troubles have obscured the larger issue: The company lacks an enduring competitive edge.

A crypto comeback might go a long way to help Robinhood’s revenue

Image: Olena Panasovska / Alex Muravev / Protocol

It’s been a full year since Robinhood weathered the memestock storm, and the company is now in much worse shape than many of us would have guessed back in January 2021. After announcing its Q4 earnings last night, Robinhood’s stock plunged into the single digits — just below $10 — down from a recent high of $70 in August 2021. That means Robinhood’s valuation dropped more than 84% in less than six months.

Investor confidence won’t be bolstered much by yesterday’s earnings results. Total net revenues dropped to $363 million from $365 million in the preceding quarter. In the quarter before that, Robinhood reported a much better $565 million in net revenue. Net losses were bad but not quite as bad as before: Robinhood reported a $423 million net loss in Q4, an improvement from the $1.3 billion net loss in Q3 2021. One of the most shocking data points: Average revenue per user dropped to $64, down from a recent high of $137 in Q1 2021. At the same time, Robinhood actually reported a decrease in monthly active users, from 18.9 million in Q3 2021 to 17.3 million in Q4 2021.

Keep Reading Show less
Hirsh Chitkara

Hirsh Chitkara ( @HirshChitkara) is a is a reporter at Protocol focused on the intersection of politics, technology and society. Before joining Protocol, he helped write a daily newsletter at Insider that covered all things Big Tech. He's based in New York and can be reached at hchitkara@protocol.com.

Latest Stories
Bulletins