cloud
Auto Added by WPeMatico
Box unwraps its answer to the $3.8B e-signature market: Box Sign
Box released its new native e-signature product Box Sign on Monday, providing e-signature capability and unlimited signatures as part of Box’s business and enterprise plans at no additional cost.
The launch comes five months after the Redwood City, California-based company agreed to acquire e-signature startup SignRequest for $55 million.
Box CEO Aaron Levie told TechCrunch the company is already securing content management for 100,000 businesses, and Box Sign represents “a breakthrough product for the company” — a new category in which Box can help customers with business processes.
“We are building out a content cloud that powers the lifecycle of content so customers can retain and manage it,” Levie said. “Everyday, there are more transactions around onboarding a customer, closing a deal or an audit, but these are still done manually. We are moving that to digital and enabling the request of signatures around the content.”
Here’s how it works: Users can send documents for e-signature directly from Box to anyone, even those without a Box account. Places for signature requests and approvals can be created anywhere on the document. All of this integrates across popular apps like Salesforce and includes email reminders and deadline notifications. As with Box’s offerings, the signatures are also secure and compliant.
The global e-signature software market was estimated to be around $1.8 billion in 2020, according to Prescient & Strategic Intelligence, while IDC expects it to grow to $3.8 billion by 2023.
Levie considers the market still early as less than one-third of organizations use e-signature due to legacy tool limitations and cost barriers, revealing massive future opportunities. However, that may be changing: Box worked with banks during the pandemic that were still relying on mailing, scanning and faxing documents to help them adapt to digital processes. It also surveyed its customers last year around product capabilities, and the No. 1 “ask” was e-signature, he said.
He mentioned major players DocuSign and Adobe Sign — two products it will continue to integrate with — among the array of technology within the space. He said that Box is not trying to compete with any player, but saw a need from customers and wanted to proceed with an option for them.
The e-signature offering also follows the hiring of Diego Dugatkin in June as Box’s new chief product officer. Prior to joining, Dugatkin was vice president of product management for Adobe Document Cloud and led strategy and execution for Adobe’s suite of products, including Adobe Sign.
“Our strategy has been for many years to expand our portfolio and power more advanced use cases, as well as a vision to have one platform to manage everything,” Levie said. “Diego has two decades of tremendous domain experience, and he will make a massive dent in powering this for us.”
In addition to the e-signature product, Box also introduced its Enterprise Plus plan that includes all of the company’s major add-ons, as well as advanced e-signature capabilities that will be available later this summer, the company said.
Powered by WPeMatico
Serverless Stack raises $1M for open-source application framework
Open-source framework startup Serverless Stack announced Friday that it raised $1 million in seed funding from a group of investors that includes Greylock Partners, SV Angel and Y Combinator.
The company was founded in 2017 by Jay V and Frank Wang in San Francisco, and they were part of Y Combinator’s 2021 winter batch.
Serverless Stack’s technology enables engineers to more easily build full-stack serverless apps. CEO V said he and Wang were working in this space for years with the aim of exposing it to a broader group of people.
While tooling around in the space, they determined that the ability to build serverless apps was not getting better, so they joined Y Combinator to hone their idea on how to make the process easier.
Here’s how the technology works: The open-source framework allows developers to test and make changes to their applications by directly connecting their local machines to the cloud. The problem with what V called an “old-school process” is that developers would upload their apps to the cloud, wait for it to run and then make any changes. Instead, Serverless Stack connects directly to the cloud for the ability to debug applications locally, he added.
Since its launch six months ago, Serverless Stack has grown to over 2,000 stars on GitHub and was downloaded more than 60,000 times.
Dalton Caldwell, managing director of YC, met V and Wang at the cohort and said he was “super impressed” because the pair were working in the space for a long time.
“These folks are experts — there are probably just half a dozen people who know as much as they do, as there aren’t that many people working on this technology,” Caldwell told TechCrunch. “The proof is in the pudding, and if they can get people to adopt it, like they did on GitHub so far, and keep that community engagement, that is my strongest signal of staying power.”
V has earmarked the new funding to expand the team, including hiring engineers to support new use cases.
Serverless initially gravitated toward specific use cases — APIs are now allowing its community to chime in and it is using that as a guide, V said. It recently announced more of a full-stack use case for building out APIs with a database and also building out the front end frameworks.
Ultimately, V’s roadmap includes building out more tools with a vision of getting Serverless Stack to the point where a developer can come on with an idea and take it all the way to an IPO using his platform.
“That’s why we want the community to drive the roadmap,” V told TechCrunch. “We are focused on what they are building and when they are in production, how they are managing it. Eventually, we will build out a dashboard to make it easier for them to manage all of their applications.”
Powered by WPeMatico
ServiceMax promises accelerating growth as key to $1.4B SPAC deal
ServiceMax, a company that builds software for the field-service industry, announced yesterday that it will go public via a special purpose acquisition company, or SPAC, in a deal valued at $1.4 billion. The transaction comes after ServiceMax was sold to GE for $915 million in 2016, before being spun out in late 2018. The company most recently raised $80 million from Salesforce Ventures, a key partner.
Broadly, ServiceMax’s business has a history of modest growth and cash consumption.
ServiceMax competes in the growing field-service industry primarily with ServiceNow, and interestingly enough given Salesforce Ventures’ recent investment, Salesforce Service Cloud. Other large enterprise vendors like Microsoft, SAP and Oracle also have similar products. The market looks at helping digitize traditional field service, but also touches on in-house service like IT and HR giving it a broader market in which to play.
GE originally bought the company as part of a growing industrial Internet of Things (IoT) strategy at the time, hoping to have a software service that could work hand in glove with the automated machine maintenance it was looking to implement. When that strategy failed to materialize, the company spun out ServiceMax and until now it remained part of Silver Lake Partners thanks to a deal that was finalized in 2019.
TechCrunch was curious why that was the case, so we dug into the company’s investor presentation for more hints about its financial performance. Broadly, ServiceMax’s business has a history of modest growth and cash consumption. It promises a big change to that storyline, though. Here’s how.
A look at the data
The company’s pitch to investors is that with new capital it can accelerate its growth rate and begin to generate free cash flow. To get there, the company will pursue organic (in-house) and inorganic (acquisition-based) growth. The company’s blank-check combination will provide what the company described as “$335 million of gross proceeds,” a hefty sum for the company compared to its most recent funding round.
Powered by WPeMatico
“Developers, as you know, do not like to pay for things”
In the previous part of this EC-1, we looked at the technical details of CockroachDB and how it provides accurate data instantaneously anywhere on the planet. In this installment, we’re going to take a look at the product side of Cockroach, with a particular focus on developer relations.
As a business, Cockroach Labs has many things going for it. The company’s approach to distributed database technology is novel. And, as more companies operate on a global level, CockroachDB has the potential to gain some significant market share internationally. The company is seven years into a typical 10-year maturity model for databases, has raised $355 million, and holds a $2 billion market value. It’s considered a double unicorn. Few database companies can say this.
The company is now aggressively expanding into the database-as-a-service space, offering its own technology in a fully managed package, expanding the spectrum of clients who can take immediate advantage of its products.
But its growth depends upon securing the love of developers while also making its product easier to use for new customers. To that end, I’m going to analyze the company’s pivot to the cloud as well as its extensive outreach to developers as it works to set itself up for long-term, sustainable success.
Cockroach Labs looks to the cloud
These days, just about any company of consequence provides services via the internet, and a growing number of these services are powered by products and services from native cloud providers. Gartner forecasted in 2019 that cloud services are growing at an annual rate of 17.5%, and there’s no sign that the growth has abated at all.
Its founders’ history with Google back in the mid-2000s has meant that Cockroach Labs has always been aware of the impact of cloud services on the commercial web. Unsurprisingly, CockroachDB could run cloud native right from its first release, given that its architecture presupposes the cloud in its operation — as we saw in part 2 of this EC-1.
Powered by WPeMatico
Scaling CockroachDB in the red ocean of relational databases
Most database startups avoid building relational databases, since that market is dominated by a few goliaths. Oracle, MySQL and Microsoft SQL Server have embedded themselves into the technical fabric of large- and medium-size companies going back decades. These established companies have a lot of market share and a lot of money to quash the competition.
So rather than trying to compete in the relational database market, over the past decade, many database startups focused on alternative architectures such as document-centric databases (like MongoDB), key-value stores (like Redis) and graph databases (like Neo4J). But Cockroach Labs went against conventional wisdom with CockroachDB: It intentionally competed in the relational database market with its relational database product.
While it did face an uphill battle to penetrate the market, Cockroach Labs saw a surprising benefit: It didn’t have to invent a market. All it needed to do was grab a share of a market that also happened to be growing rapidly.
Cockroach Labs has a bright future, compelling technology, a lot of money in the bank and has an experienced, technically astute executive team.
In previous parts of this EC-1, I looked at the origins of CockroachDB, presented an in-depth technical description of its product as well as an analysis of the company’s developer relations and cloud service, CockroachCloud. In this final installment, we’ll look at the future of the company, the competitive landscape within the relational database market, its ability to retain talent as it looks toward a potential IPO or acquisition, and the risks it faces.
CockroachDB’s success is not guaranteed. It has to overcome significant hurdles to secure a profitable place for itself among a set of well-established database technologies that are owned by companies with very deep pockets.
It’s not impossible, though. We’ll first look at MongoDB as an example of how a company can break through the barriers for database startups competing with incumbents.
When life gives you Mongos, make MongoDB
Dev Ittycheria, MongoDB CEO, rings the Nasdaq Stock Market Opening Bell. Image Credits: Nasdaq, Inc
MongoDB is a good example of the risks that come with trying to invent a new database market. The company started out as a purely document-centric database at a time when that approach was the exception rather than the rule.
Web developers like document-centric databases because they address a number of common use cases in their work. For example, a document-centric database works well for storing comments to a blog post or a customer’s entire order history and profile.
Powered by WPeMatico
Former Nutanix execs launch new startup with $50M seed round
Today a new software company from two former Nutanix executives called DevRev emerged from stealth with a $50 million seed round from Mayfield Fund, Khosla Ventures and several industry luminaries. The company, which aims to bring the coding and revenue processes closer together, already has 75 employees working on the new software platform, which they hope to have ready to launch later this year.
It’s not every day you see a $50 million seed round, but perhaps the fact that former Nutanix co-founder and CEO Dheeraj Pandey and his former SVP of engineering Manoj Agarwal are involved, could help explain the investor enthusiasm for the new project.
Pandey says that he has seen a gap between developers and the revenue the applications they create are supposed to generate. The idea behind the new company is to break down the silos that exist between the front of the office and the back of the office and give developers a deeper understanding of the customers using their products, or at least that’s the theory.
“Dev and rev are yin and yang to each other. In today’s world they are really far apart with tons of bureaucracy between these two parties. Our goal to bring dev and rev to get rid of the bureaucracy,” Pandey told me
The company intends to build an API to help developers pull this information from existing systems for companies already working with a CRM tool like Salesforce, while helping gather that customer information for younger companies who might lack a tool. Regardless, the idea is to bring that info where the developer can see it to help build better products.
The way it works in most companies is customer service or sales hears complaints or suggestions about the product, and tickets get generated, but putting these issues in front of the people building the software isn’t always easy or direct. DevRev hopes to change that.
Navin Chaddha, managing director at Mayfield, whose firm is investing in DevRev, sees a need to bring these different parts of the company together in a more direct way. “The code that developers work on today is used by support as well as marketing and sales. By bringing the world of issues and tickets closer to the world of revenue and growth, DevRev’s unified platform bridges the gap between developer and customer and elevates the developer to a business leader,” Chaddha said.
With 75 employees working on the problem, DevRev is already a substantial startup. As experienced founders Pandey and Agarwal certainly understand the importance of building a diverse and inclusive company. Pandey sees the top of the employment funnel really being focused on engineering, design and business schools and the company is working to bring in a diverse group of young employees.
“[We are looking at ways] to search for talent and to promote talent, to make them into leaders. I think we have an empty canvas by the way, and we have this idea of COVID, and being able to do remote work has really grown the top of the funnel, the mouth of the funnel now can be anything and everything. […] [Colleges and universities] are I would say the real source of all diversity at the end of the day. We have seen how engineering schools, design schools and business schools are actually getting so diverse,” he said.
The company is working to build the product now and reaching out to developer communities on Discord, GitHub and other places that developers gather online to get their input, while testing and improving the product in-house and with design partners.
Nutanix, the founders’ previous company, launched in 2009 and raised over a $1 billion before going public in 2016. Pandey and Agarwal left Nutanix at the end of last year to launch the new company.
Powered by WPeMatico
Cloud security platform Netskope boosts valuation to $7.5B following $300M raise
Netskope, focused on Secure Access Service Edge architecture, announced Friday a $300 million investment round on a post-money valuation of $7.5 billion.
The oversubscribed insider investment was led by ICONIQ Growth, which was joined by other existing investors, including Lightspeed Venture Partners, Accel, Sequoia Capital Global Equities, Base Partners, Sapphire Ventures and Geodesic Capital.
Netskope co-founder and CEO Sanjay Beri told TechCrunch that since its founding in 2012, the company’s mission has been to guide companies through their digital transformation by finding what is most valuable to them — sensitive data — and protecting it.
“What we had before in the market didn’t work for that world,” he said. “The theory is that digital transformation is inevitable, so our vision is to transform that market so people could do that, and that is what we are building nearly a decade later.”
With this new round, Netskope continues to rack up large rounds: it raised $340 million last February, which gave it a valuation of nearly $3 billion. Prior to that, it was a $168.7 million round at the end of 2018.
Similar to other rounds, the company was not actively seeking new capital, but that it was “an inside round with people who know everything about us,” Beri said.
“The reality is we could have raised $1 billion, but we don’t need more capital,” he added. “However, having a continued strong balance sheet isn’t a bad thing. We are fortunate to be in that situation, and our destination is to be the most impactful cybersecurity company in the world.
Beri said the company just completed a “three-year journey building the largest cloud network that is 15 milliseconds from anyone in the world,” and intends to invest the new funds into continued R&D, expanding its platform and Netskope’s go-to-market strategy to meet demand for a market it estimated would be valued at $30 billion by 2024, he said.
Even pre-pandemic the company had strong hypergrowth over the past year, surpassing the market average annual growth of 50%, he added.
Today’s investment brings the total raised by Santa Clara-based Netskope to just over $1 billion, according to Crunchbase data.
With the company racking up that kind of capital, the next natural step would be to become a public company. Beri admits that Netskope could be public now, though it doesn’t have to do it for the traditional reasons of raising capital or marketing.
“Going public is one day on our path, but you probably won’t see us raise another private round,” Beri said.
Powered by WPeMatico
Rootly nabs $3.2M seed to build SRE incident management solution inside Slack
As companies look for ways to respond to incidents in their complex microservices-driven software stacks, SREs — site reliability engineers — are left to deal with the issues involved in making everything work and keeping the application up and running. Rootly, a new early-stage startup wants to help by building an incident-response solution inside of Slack.
Today the company emerged from stealth with a $3.2 million seed investment. XYZ Venture Capital led the round with participation from 8VC, Y Combinator and several individual tech executives.
Rootly co-founder and CEO Quentin Rousseau says that he cut his SRE teeth working at Instacart. When he joined in 2015, the company was processing hundreds of orders a day, and when he left in 2018 it was processing thousands. It was his job to make sure the app was up and running for shoppers, consumers and stores even as it scaled.
He said that while he was at Instacart, he learned to see patterns in the way people responded to an issue and he had begun working on a side project after he left looking to bring the incident response process under control inside of Slack. He connected with co-founder JJ Tang, who had started at Instacart after Rousseau left in 2018, and the two of them decided to start Rootly to help solve these unique problems that SREs face around incident response.
“Basically we want people to manage and resolve incidents directly in Slack. We don’t want to add another layer of complexity on top of that. We feel like there are already so many tools out there and when things are chaotic and things are on fire, you really want to focus quickly on the resolution part of it. So we’re really trying to be focused on the Slack experience,” Rousseau explained.
The Rootly solution helps SREs connect quickly to their various tools inside Slack, whether that’s Jira or Zendesk or DataDog or PagerDuty, and it compiles an incident report in the background based on the conversation that’s happening inside of Slack around resolving the incident. That will help when the team meets for an incident post-mortem after the issue is resolved.
The company is small at the moment with fewer than 10 employees, but it plans to hire some engineers and sales people over the next year as they put this capital to work.
Tang says that they have built diversity as a core component of the company culture, and it helps that they are working with investor Ross Fubini, managing partner at lead investor XYZ Venture Capital. “That’s also one of the reasons why we picked Ross as our lead investor. [His firm] has probably one of the deepest focuses around [diversity], not only as a fund, but also how they influence their portfolio companies,” he said.
Fubini says there are two main focuses in building diverse companies including building a system to look for diverse pools of talent, and then building an environment to help people from underrepresented groups feel welcome once they are hired.
“One of our early conversations we had with Rootly was how do we both bring a diverse group in and benefit from a diverse set of people, and what’s going to both attract them, and when they come in make them feel like this is a place that they belong,” Fubini explained.
The company is fully remote right now with Rousseau in San Francisco and Tang in Toronto, and the plan is to remain remote whenever offices can fully reopen. It’s worth noting that Rousseau and Tang are members of the current Y Combinator batch.
Powered by WPeMatico
Dropbox is reimagining the workplace with Dropbox Studios
The pandemic has been a time for a lot of reflection on both a personal and business level. Tech companies in particular are assessing whether they will ever again return to a full-time, in-office approach. Some are considering a hybrid approach and some may not go back to a building at all. Amidst all this, Dropbox has decided to reimagine the office with a new concept they are introducing this week called Dropbox Studios.
Dropbox CEO and co-founder Drew Houston sees the pandemic as a forcing event, one that pushes companies to rethink work through a distributed lens. He doesn’t think that many businesses will simply go back to the old way of working. As a result, he wanted his company to rethink the office design with one that did away with cube farms with workers spread across a landscape of cubicles. Instead, he wants to create a new approach that takes into account that people don’t necessarily need a permanent space in the building.
“We’re soft launching or opening our Dropbox Studios [this] week in the U.S., including the one in San Francisco. And we took the opportunity as part of our focus to reimagine the office into a collaborative space that we call a studio,” Houston told me.
Houston says that the company really wanted to think about how to incorporate the best of working at home with the best of working at the office collaborating with colleagues. “We focused on having really great curated in-person experiences, some of which we coordinate at the company level and then some of which you can go into our studios, which have been refitted to support more collaboration,” he said.
Dropbox Studio coffee shop. Image Credits: Dropbox
To that end, they have created a lot of soft spaces with a coffee shop to create a casual feel, conference rooms for teams to have what Houston called “on-site off-sites” and classrooms for organized group learning. The idea is to create purpose-built spaces for what would work best in an office environment and what people have been missing from in-person interactions since they were forced to work at home by the pandemic, while letting people accomplish more individual work at home.
The company is planning on dedicated studios in major cities like San Francisco, Seattle, Tokyo and Tel Aviv with smaller on-demand spaces operated by partners like WeWork in other locations.
Dropbox Studio classroom space. Image Credits: Dropbox
As Houston said when he appeared at TechCrunch Disrupt last year, his company sees this as an opportunity to be on the forefront of distributed work and act as an example and a guide to help other companies as they undertake similar journeys.
“When you think more broadly about the effects of the shift to distributed work, it will be felt well beyond when we go back to the office. So we’ve gone through a one-way door. This is maybe one of the biggest changes to knowledge work since that term was invented in 1959,” Houston said last year.
He recognizes that they have to evaluate how this is going to work and iterate on the design as needed, just as the company iterates on its products and they will be evaluating the new spaces and the impact on collaborative work and making adjustments when needed. To help others, Dropbox is releasing an open-source project plan called the Virtual First Toolkit.
The company is going all-in with this approach and will be subletting much of its existing office space as it moves to this new way of working and its space requirements change dramatically. It’s a bold step, but one that Houston believes his company is uniquely positioned to undertake, and he wants Dropbox to be an example to others on how to reinvent the way we work.
Powered by WPeMatico
The single vendor requirement ultimately doomed the DoD’s $10B JEDI cloud contract
When the Pentagon killed the JEDI cloud program yesterday, it was the end of a long and bitter road for a project that never seemed to have a chance. The question is why it didn’t work out in the end, and ultimately I think you can blame the DoD’s stubborn adherence to a single vendor requirement, a condition that never made sense to anyone, even the vendor that ostensibly won the deal.
In March 2018, the Pentagon announced a mega $10 billion, decade-long cloud contract to build the next generation of cloud infrastructure for the Department of Defense. It was dubbed JEDI, which aside from the Star Wars reference, was short for Joint Enterprise Defense Infrastructure.
The idea was a 10-year contract with a single vendor that started with an initial two-year option. If all was going well, a five-year option would kick in and finally a three-year option would close things out with earnings of $1 billion a year.
While the total value of the contract had it been completed was quite large, a billion a year for companies the size of Amazon, Oracle or Microsoft is not a ton of money in the scheme of things. It was more about the prestige of winning such a high-profile contract and what it would mean for sales bragging rights. After all, if you passed muster with the DoD, you could probably handle just about anyone’s sensitive data, right?
Regardless, the idea of a single-vendor contract went against conventional wisdom that the cloud gives you the option of working with the best-in-class vendors. Microsoft, the eventual winner of the ill-fated deal acknowledged that the single vendor approach was flawed in an interview in April 2018:
Leigh Madden, who heads up Microsoft’s defense effort, says he believes Microsoft can win such a contract, but it isn’t necessarily the best approach for the DoD. “If the DoD goes with a single award path, we are in it to win, but having said that, it’s counter to what we are seeing across the globe where 80% of customers are adopting a multicloud solution,” Madden told TechCrunch.
Perhaps it was doomed from the start because of that. Yet even before the requirements were fully known there were complaints that it would favor Amazon, the market share leader in the cloud infrastructure market. Oracle was particularly vocal, taking its complaints directly to the former president before the RFP was even published. It would later file a complaint with the Government Accountability Office and file a couple of lawsuits alleging that the entire process was unfair and designed to favor Amazon. It lost every time — and of course, Amazon wasn’t ultimately the winner.
While there was a lot of drama along the way, in April 2019 the Pentagon named two finalists, and it was probably not too surprising that they were the two cloud infrastructure market leaders: Microsoft and Amazon. Game on.
The former president interjected himself directly in the process in August that year, when he ordered the Defense Secretary to review the matter over concerns that the process favored Amazon, a complaint which to that point had been refuted several times over by the DoD, the Government Accountability Office and the courts. To further complicate matters, a book by former defense secretary Jim Mattis claimed the president told him to “screw Amazon out of the $10 billion contract.” His goal appeared to be to get back at Bezos, who also owns the Washington Post newspaper.
In spite of all these claims that the process favored Amazon, when the winner was finally announced in October 2019, late on a Friday afternoon no less, the winner was not in fact Amazon. Instead, Microsoft won the deal, or at least it seemed that way. It wouldn’t be long before Amazon would dispute the decision in court.
By the time AWS re:Invent hit a couple of months after the announcement, former AWS CEO Andy Jassy was already pushing the idea that the president had unduly influenced the process.
“I think that we ended up with a situation where there was political interference. When you have a sitting president, who has shared openly his disdain for a company, and the leader of that company, it makes it really difficult for government agencies, including the DoD, to make objective decisions without fear of reprisal,” Jassy said at that time.
Then came the litigation. In November the company indicated it would be challenging the decision to choose Microsoft charging that it was was driven by politics and not technical merit. In January 2020, Amazon filed a request with the court that the project should stop until the legal challenges were settled. In February, a federal judge agreed with Amazon and stopped the project. It would never restart.
In April the DoD completed its own internal investigation of the contract procurement process and found no wrongdoing. As I wrote at the time:
While controversy has dogged the $10-billion, decade-long JEDI contract since its earliest days, a report by the DoD’s inspector general’s office concluded today that, while there were some funky bits and potential conflicts, overall the contract procurement process was fair and legal and the president did not unduly influence the process in spite of public comments.
Last September the DoD completed a review of the selection process and it once again concluded that Microsoft was the winner, but it didn’t really matter as the litigation was still in motion and the project remained stalled.
The legal wrangling continued into this year, and yesterday the Pentagon finally pulled the plug on the project once and for all, saying it was time to move on as times have changed since 2018 when it announced its vision for JEDI.
The DoD finally came to the conclusion that a single-vendor approach wasn’t the best way to go, and not because it could never get the project off the ground, but because it makes more sense from a technology and business perspective to work with multiple vendors and not get locked into any particular one.
“JEDI was developed at a time when the Department’s needs were different and both the CSPs’ (cloud service providers) technology and our cloud conversancy was less mature. In light of new initiatives like JADC2 (the Pentagon’s initiative to build a network of connected sensors) and AI and Data Acceleration (ADA), the evolution of the cloud ecosystem within DoD, and changes in user requirements to leverage multiple cloud environments to execute mission, our landscape has advanced and a new way ahead is warranted to achieve dominance in both traditional and nontraditional warfighting domains,” said John Sherman, acting DoD chief information officer in a statement.
In other words, the DoD would benefit more from adopting a multicloud, multivendor approach like pretty much the rest of the world. That said, the department also indicated it would limit the vendor selection to Microsoft and Amazon.
“The Department intends to seek proposals from a limited number of sources, namely the Microsoft Corporation (Microsoft) and Amazon Web Services (AWS), as available market research indicates that these two vendors are the only Cloud Service Providers (CSPs) capable of meeting the Department’s requirements,” the department said in a statement.
That’s not going to sit well with Google, Oracle or IBM, but the department further indicated it would continue to monitor the market to see if other CSPs had the chops to handle their requirements in the future.
In the end, the single vendor requirement contributed greatly to an overly competitive and politically charged atmosphere that resulted in the project never coming to fruition. Now the DoD has to play technology catch-up, having lost three years to the histrionics of the entire JEDI procurement process and that could be the most lamentable part of this long, sordid technology tale.
Powered by WPeMatico