Developer

Auto Added by WPeMatico

Google Cloud launches Vertex AI, a new managed machine learning platform

At Google I/O today Google Cloud announced Vertex AI, a new managed machine learning platform that is meant to make it easier for developers to deploy and maintain their AI models. It’s a bit of an odd announcement at I/O, which tends to focus on mobile and web developers and doesn’t traditionally feature a lot of Google Cloud news, but the fact that Google decided to announce Vertex today goes to show how important it thinks this new service is for a wide range of developers.

The launch of Vertex is the result of quite a bit of introspection by the Google Cloud team. “Machine learning in the enterprise is in crisis, in my view,” Craig Wiley, the director of product management for Google Cloud’s AI Platform, told me. “As someone who has worked in that space for a number of years, if you look at the Harvard Business Review or analyst reviews, or what have you — every single one of them comes out saying that the vast majority of companies are either investing or are interested in investing in machine learning and are not getting value from it. That has to change. It has to change.”

Image Credits: Google

Wiley, who was also the general manager of AWS’s SageMaker AI service from 2016 to 2018 before coming to Google in 2019, noted that Google and others who were able to make machine learning work for themselves saw how it can have a transformational impact, but he also noted that the way the big clouds started offering these services was by launching dozens of services, “many of which were dead ends,” according to him (including some of Google’s own). “Ultimately, our goal with Vertex is to reduce the time to ROI for these enterprises, to make sure that they can not just build a model but get real value from the models they’re building.”

Vertex then is meant to be a very flexible platform that allows developers and data scientist across skill levels to quickly train models. Google says it takes about 80% fewer lines of code to train a model versus some of its competitors, for example, and then help them manage the entire lifecycle of these models.

Image Credits: Google

The service is also integrated with Vizier, Google’s AI optimizer that can automatically tune hyperparameters in machine learning models. This greatly reduces the time it takes to tune a model and allows engineers to run more experiments and do so faster.

Vertex also offers a “Feature Store” that helps its users serve, share and reuse the machine learning features and Vertex Experiments to help them accelerate the deployment of their models into producing with faster model selection.

Deployment is backed by a continuous monitoring service and Vertex Pipelines, a rebrand of Google Cloud’s AI Platform Pipelines that helps teams manage the workflows involved in preparing and analyzing data for the models, train them, evaluate them and deploy them to production.

To give a wide variety of developers the right entry points, the service provides three interfaces: a drag-and-drop tool, notebooks for advanced users and — and this may be a bit of a surprise — BigQuery ML, Google’s tool for using standard SQL queries to create and execute machine learning models in its BigQuery data warehouse.

We had two guiding lights while building Vertex AI: get data scientists and engineers out of the orchestration weeds, and create an industry-wide shift that would make everyone get serious about moving AI out of pilot purgatory and into full-scale production,” said Andrew Moore, vice president and general manager of Cloud AI and Industry Solutions at Google Cloud. “We are very proud of what we came up with in this platform, as it enables serious deployments for a new generation of AI that will empower data scientists and engineers to do fulfilling and creative work.”

Powered by WPeMatico

Watch Google I/O keynote live right here

After skipping a year, Google is holding a keynote for its developer conference Google I/O. While it’s going to be an all-virtual event, there should be plenty of announcements, new products and new features for Google’s ecosystem.

The conference starts at 10 AM Pacific Time (1 PM on the East Cost, 6 PM in London, 7 PM in Paris) and you can watch the livestream right here on this page.

Rumor has it that Google should give us a comprehensive preview of Android 12, the next major release of Google’s operating system. There could also be some news when it comes to Google Assistant, Home/Nest devices, Wear OS and more.

Powered by WPeMatico

Styra, the startup behind Open Policy Agent, nabs $40M to expand its cloud-native authorization tools

As cloud-native apps continue to become increasingly central to how organizations operate, a startup founded by the creators of a popular open-source tool to manage authorization for cloud-native application environments is announcing some funding to expand its efforts at commercializing the opportunity.

Styra, the startup behind Open Policy Agent, has picked up $40 million in a Series B round of funding led by Battery Ventures. Also participating are previous backers A. Capital, Unusual Ventures and Accel; and new backers CapitalOne Ventures, Citi Ventures and Cisco Investments. Styra has disclosed CapitalOne is also one of its customers, along with e-commerce site Zalando and the European Patent Office.

Styra is sitting on the classic opportunity of open source technology: scale and demand.

OPA — which can be used across Kubernetes, containerized and other environments — now has racked up some 75 million downloads and is adding some 1 million downloads weekly, with Netflix, Capital One, Atlassian and Pinterest among those that are using OPA for internal authorization purposes. The fact that OPA is open source is also important:

“Developers are at the top of the food chain right now,” CEO Bill Mann said in an interview, “They choose which technology on which to build the framework, and they want what satisfies their requirements, and that is open source. It’s a foundational change: if it isn’t open source it won’t pass the test.”

But while some of those adopting OPA have hefty engineering teams of their own to customize how OPA is used, the sheer number of downloads (and potential active users stemming from that) speak to the opportunity for a company to build tools to help manage that and customize it for specific use cases in cases where those wanting to use OPA may lack the resources (or appetite) to build and scale custom implementations themselves.

As with many of the enterprise startups getting funded at the moment, Styra has proven itself in particular over the last year, with the switch to remote work, workloads being managed across a number of environments, and the ever-persistent need for better security around what people can and should not be using. Authorization is a particularly acute issue when considering the many access points that need to be monitored: as networks continue to grow across multiple hubs and applications, having a single authorization tool for the whole stack becomes even more important.

Styra said that some of the funding will be used to continue evolving its product, specifically by creating better and more efficient ways to apply authorization policies by way of code; and by bringing in more partners to expand the scope of what can be covered by its technology.

“We are extremely impressed with the Styra team and the progress they’ve made in this dynamic market to date,” said Dharmesh Thakker, a general partner at Battery Ventures. “Everyone who is moving to cloud, and adopting containerized applications, needs Styra for authorization—and in the light of today’s new, remote-first work environment, every enterprise is now moving to the cloud.” Thakker is joining the board with this round.

Powered by WPeMatico

Merge raises $4.5M to help B2B companies build customer-facing integrations

Merge, a startup that helps its users build customer-facing integrations with third-party tools, today announced that it has raised a $4.5 million seed round led by NEA. Additional angel investors include former MuleSoft CEO Greg Schott, Cloudflare CEO Matthew Prince, Expanse co-founders Tim Junio and Matt Kraning, and Jumpstart CEO Ben Herman.

Launched in 2020, the core focus of Merge is to give B2B companies a unified API to access data from what is currently about 40 HR, payroll, recruiting and accounting platforms, with plans for expanding to additional areas soon. But Merge co-founders Shensi Ding and Gil Feig, who have been lifelong friends and previously worked at companies like Expanse and Jumpstart, stress that the service isn’t aiming to replace workflow tools Workato or Zapier.

Image Credits: Merge

“What we built is more similar to Plaid than MuleSoft or other things,” Feig said. “We built a unified API, so we’re fully embedded in a customer’s product and they build one integration with us and can automatically offer all these integrations to their customers. On top of that, we offer what we call integrations management, which is a suite of tools to automatically detect issues where the customer would have to get involved — automatically detect that stuff and handle it without ever having to involve engineering again.”

When Merge’s systems detect issues with an integration, maybe because a data schema in an API response has changed without notice (which happens with some regularity), Merge’s engineers can fix that within minutes, in part because the teams also built an internal no-code tool for building and managing these integrations.

Image Credits: Merge

As Ding also noted, B2B buyers today also simply expect their tools to feature integrations with the service they use. “Companies, when they purchase a vendor, they expect that vendor to have integrations with all the other vendors that they own,” she said. “They don’t want to have to purchase a vendor and then purchase a workflow product and then connect those products.”

And while Merge’s focus right now is squarely on a few verticals, the plan is to expand this to far more areas shortly, likely starting with CRM. “Salesforce has a pretty large market share, so we thought that it wasn’t going to be as interesting of a market,” Ding said. “But it turns out that their API is so complex that customers would still prefer to integrate with us instead if we simplify it for them.”

Ding and Feig tell me the company, which came out of stealth about two months ago, already has about 100 organizations on its platform, varying from seed-stage companies to publicly listed enterprises. The team credits its focus on security and reliability (and its SOC II compliance) with being able to bring on some of these larger companies despite being a seed-stage company itself.

To monetize the service, Merge offers a free tier (up to 10,000 API requests per month) and charges $0.01 per API request for additional usage. Unsurprisingly, the company also offers customized enterprise plans for its larger customers.

“The time and expense associated with building and maintaining myriad API integrations is a pain point we hear about consistently from our portfolio companies across all industries,” said NEA managing general partner Scott Sandell, who will join the company’s board. “Merge is tackling this ubiquitous problem head-on via their easy-to-use, unified API platform. Their platform has broad applicability and is a massive upgrade for any software company that needs to build, manage, and maintain multiple API integrations.”

Powered by WPeMatico

BluBracket nabs $12M Series A to expand source code security platform

BluBracket, an early-stage startup that focuses on keeping source code repositories secure, even in distributed environments, announced a $12 million Series A today.

Evolution Equity Partners led the round, with help from existing investors Unusual Ventures, Point72 Ventures, SignalFire and Firebolt Ventures. When combined with the $6.5 million seed round we reported on last year, the company has raised $19.5 million so far.

As you might imagine, being able to secure code in distributed environments came in quite handy when much of the technology world moved to work from home last year. BluBracket co-founder and COO Ajay Arora says that the pandemic forced many organizations to look carefully at how they secured their code base.

“So the anxiety organizations had about making sure their source code was secure and that it wasn’t leaking, from that standpoint that was a big tailwind for us. [With companies moving to a] completely remote development workforce, and with code being so important to their business as intellectual property, they needed to get that visibility into what vulnerabilities were there,” Arora explained.

Even prior to the pandemic, the company was finding they were gaining traction with developers and security pros by using a bottom up approach offering a free community version of the software. Having that free version as a top of the funnel for their sales motion was also helpful once COVID hit full force.

Today, Arora says the company has multiple thousands of developers, DevOps and SecOps users across dozens of organizations using the company’s suite of products. The big reference company right now is Priceline, but he says there are other big names that would prefer not to be public about it.

The company currently has 30 employees, with plans to double that by the end of the year, and he says that building diversity and inclusion into the hiring process is part of the company’s core values, and part of how the executive team gets measured.

“We’re big believers in putting our money where our mouth is and one of the OKRs for me and my co-founder [CEO Prakash Linga], or one of the things that we’re actually compensated for, is how well we are doing in building diversity and inclusion on the team,” he said. He adds that the recruiters that they are using are also being held to the same standard when it comes to providing a diverse set of candidates for open positions.

The company launched in 2018 and the founding team came from Vera, a startup that helped secure documents in motion. That company was sold to HelpSystems in December 2020 after Arora and Linga had left to start BluBracket.

Powered by WPeMatico

The truth about SDK integrations and their impact on developers

The digital media industry often talks about how much influence, dominance and power entities like Google and Facebook have. Generally, the focus is on the vast troves of data and audience reach these companies tout. However, there’s more beneath the surface that strengthens the grip these companies have on both app developers and publishers alike.

In reality, software development kit (SDK) integrations are a critical component of why these monolith companies have such a prominent presence. For reference, an SDK is a set of software development tools, libraries, code samples, processes and guides that help developers create or enhance the apps they’re building.

Through a digital marketing lens, SDKs provide in-app analytics, insights on campaign testing, attribution information, location details, monetization capabilities and more.

Through a digital marketing lens, SDKs provide in-app analytics, insights on campaign testing, attribution information, location details, monetization capabilities and more. In the case of companies like Google and Facebook, their ability to provide these insights dovetails with their data and reach.

While that does deliver useful capabilities to developers and publishers alike, it also perpetuates the factors contributing to their perceived monopolistic status — and the detriments a lack of competition fosters.

Almost all (90%) ad-monetized Android apps have Google’s Admob SDK integrated, data from Statista showed. Additionally, the Facebook Audience Network SDK is present in 19% of all global Android apps utilizing mobile ads. It’s worth noting that the large majority of alternative “leading” advertising SDKs outside these two players are used less than 13% of the time in Android apps.

As the app ecosystem rapidly expands beyond the borders of mobile, app developers and publishers would benefit immensely from identifying economical and secure ways of adopting more SDKs.

The state of SDK adoption

While there are many SDKs available in the market today, a few key factors contribute to Google and Facebook’s overall dominance. The most basic is around the respective organizations’ reach and industry notoriety. However, a larger component here is the lack of resources and time app developers have.

Powered by WPeMatico

Salesforce is bringing drag and drop interactive components to its low-code toolkit

Low-code and no-code tools abound these days, as the industry attempts to give nontechnical end users the ability to create applications without code (or very little anyway). Salesforce has been a big proponent of this approach to help reduce the complexity of working on its platform, and today the CRM giant announced a new wrinkle: drag and drop interactive components.

These new components allow users to create more sophisticated kinds of interactions, says Ryan Ellis, SVP for product management and platform at Salesforce. “We’re introducing this new feature called Dynamic Interactions and prior to their existence you had to have developers if you wanted to be able to build essentially truly interactive applications,” Ellis said.

What he means by this is if you have an application made up of multiple components such as a list of companies, a map and information about the company. You can click a company name and its location instantly appears on the map, and information about the company appears alongside it.

Salesforce will be providing about 150 such interactions like maps, lists, Einstein next best action and so forth. Developers can also create these for users as reusable building blocks that make sense to your organization or make them available in the AppExchange for others to use. Finally, you might have a systems integrator or consultant help build them for you.

“With dynamic interactions, we’re really dramatically simplifying the process of building apps with components that communicate with each other, pass data back and forth and react to user actions. It’s an entirely no-code tool so that developers write the code once for their component, and then that component can be reused by people who don’t have technical skills by dragging and dropping them onto the page, then configuring what should happen when a user takes an action,” Ellis explained.

An example of dynamic interactions from Salesforce. Clicking an item of the left causes its locations to appear in the center and information about the selected item on the right.

Image Credits: Salesforce

He says that this is part of a larger trend of digital transformation happening across the industry, one that was accelerated by the pandemic, something we hear frequently from tech companies like Salesforce.

“There’s really this big push to go digital faster than ever before, and this was happening for years as we were seeing businesses having to pivot much more rapidly as new business models were coming about. […] But then in this last year COVID really changed the game, and people just had to put on full gas in terms of actually being able to deliver those digital transformations in some instances overnight,” he said.

When you combine that with a shortage of developers, it makes sense that Salesforce and many other companies in the industry are developing these low-code tools that allow nontechnical business users to build some applications themselves, while freeing developers to concentrate on more sophisticated organizational requirements.

Dynamic Interactions will be available starting today from Salesforce (in beta). The product is expected to be generally available around Dreamforce in the fall.

Powered by WPeMatico

SaaS companies can grow to $20M+ ARR by selling exclusively to developers

With more than 200,000 customers, a market cap of nearly $56 billion, and the recent acquisition of Segment for $3.2 billion, Twilio is a SaaS behemoth.

It’s hard to imagine companies like Twilio as anything but a giant. But everybody starts out small, and you can usually trace success back to key decisions made in the early days.

First, you need to have a product that developers can actually sign up for. This means ditching demos for real-time free trials or freemium tools.

For Twilio, a big differentiator was being one of the first technology-focused SaaS organizations that focused on empowering and building for the end user (which in their case is developers) with a self-service function. Another differentiator was, the executive team designed the organization to create tight feedback loops between sales and product with national roadshows, during which CEO Jeff Lawson frequently met with users.

Moreover, Twilio’s “secret sauce” per their S-1 is a developer-focused model and a strong belief in the future of software. They encourage developers to explore and innovate with Twilio’s flexible offering, which led to an incredible 155% net-dollar expansion rate at the time of the IPO.

Most importantly, Twilio put the product in the hands of teams before the sale happened, standing by to answer hard questions about how Twilio would fit into their infrastructure. This was pretty rare at the time — sales engineering resources aren’t cheap — and it was a strong differentiating factor. So much so that when the company went public, they were growing at 106% annually.

Twilio sells to developers at large enterprises by solving a problem that developers come up against regularly: Getting in touch with customers.

But as more successful public software companies emerge, it’s clear that Twilio’s secret sauce can and will be replicated.

Why traditional marketing doesn’t work on developers

Before I started looking at successful developer-focused businesses, I understood the developer-focused playbook to look a little like this:
  1. Don’t hire marketing (or sales, either). If you do, hire someone super experienced from an enterprise sales background. And then fire them within three to six months.
  2. Just hire someone who’s passionate about the product to “manage the community.” What is community management? Lots of swag. Cool meetups. Publish 1–2 articles as a stab at content (bonus points if they’re listicles). Oh, wait. How can we show the ROI here? Make the community manager do that until she quits. Repeat.

Powered by WPeMatico

To buy time for a failing startup, recreate the engineering process

In non-aerobatic fixed-wing aviation, spins are an emergency. If you don’t have spin recovery training, you can easily make things worse, dramatically increasing your chances of crashing. Despite the life-and-death consequences, licensed amateur pilots in the United States are not required to train for this. Uncontrolled spins don’t happen often enough to warrant the training.

Startups can enter the equivalent of a spin as well. My startup, Kolide, entered a dangerous spin in early 2018, only a year after our Series A fundraise. We had little traction and we were quickly burning through our sizable cash reserves. We were spinning out of control, certain to hit the ground in no time.

Kolide had a lot going for it that enabled me to recover the company, but by far the most important was that we recognized we were in a spin very early, and we had enough cash remaining (and therefore sufficient time) to execute a recovery plan.

All spins start with a stall — a reduction in lift when either the aircraft is flying too slowly or the nose is pointed too high. In Kolide’s case, we were doing both.

First, we raised too much money too fast. In order to justify the post-money valuation that came with the raise, we set unattainable goals. To make matters worse, we lacked the confidence in our product and strategy, so we developed our solution with hesitancy, underspending in critical areas. As a result, we were flying too steep and too slow. We stalled.

If a stall isn’t corrected promptly, a spin can develop. Flat spins are one of the worst. Once the flat spin starts, there are a number of techniques experienced pilots should perform to recover the aircraft. Nearly all of these techniques require a critical resource, altitude — or, put another way, time.

Just like amateur pilots, startup CEOs don’t receive spin recovery training. When Kolide was spinning out of control, the vast majority of the advice I received was to cut our losses and sell the company or return the money to the investors.

At the time, I didn’t find any promising examples of companies with these same problems successfully recovering; I found only smoldering wreckage. By February 2019, my co-founders departed.

Despite this tell-tale sign of imminent demise, I was ultimately able to recover and put us on track for a great fundraise. Here’s how I recreated the engineering process.

Buying time

Kolide had a lot going for it that enabled me to recover the company, but by far the most important was that we recognized we were in a spin very early, and we had enough cash remaining (and therefore sufficient time) to execute a recovery plan. Even waiting just a few more months would have likely changed the outcome.

Powered by WPeMatico