Embedded iPaaS vs Enterprise iPaaS: What's the Difference?

An iPaaS (integration platform as a service) speeds up the process of building software integrations. The two types of iPaaS are enterprise iPaaS (sometimes called traditional iPaaS) and embedded iPaaS, but they are intended to solve fundamentally different issues.

Before we get into the details, let's look at two integration use cases.

• You have hundreds of customers in the service industry who use your SaaS app (an appointment manager) to drive their schedules. Each customer has its own billing and payroll systems. Your customers need your app needs to exchange data with those accounting systems.
• Your company intranet needs to display a combined calendar showing employee vacation/leave schedules for three different company offices. Each of those offices uses a separate calendar app.

We'll see which integration platform (embedded iPaaS or enterprise iPaaS) would be best for each of these, but let's first see why integration platforms have become so important.

Integration platforms are vital to increasing efficiency

Businesses are using more SaaS apps than ever. Blissfully, now Vendr, noted in a 2020 report that small businesses use an average of 102 apps, mid-market businesses use an average of 137 apps, and enterprises use an average of 288. That's a lot of different applications.

A recent study in the Harvard Business Review notes that:

"[O]n average, the cost of a switch is [a] little over two seconds and the average user in the dataset toggled between different apps and websites nearly 1,200 times each day. That means that people in these jobs spent just under four hours a week reorienting themselves after toggling to a new application. Over the course of a year, that adds up to five working weeks, or 9% of their annual time at work."

We could reduce the number of apps users need to switch between if the apps could share data. But building all those integrations from scratch requires a time investment that is off-putting to many companies. That's where an iPaaS or an embedded iPaaS come into play. Both platforms can significantly increase the efficiency of the integration-building process.

As more companies address their needs for internal integrations, the iPaaS market continues its rapid expansion. In its 2021 Magic Quadrant for Enterprise Integration Platform as a Service, Gartner estimated that iPaaS was a $3.47 billion market in 2019, growing by 38.7% from 2019, and expected to reach over $9 billion in revenue by 2025.

Since embedded iPaaS is a relatively new category, many analysts such as Gartner are still grouping embedded iPaaS products – and their revenue – under the iPaaS category.

Clearly, though, embedded iPaaS is a considerable part of the broader categories' growth. We have seen the number of embedded iPaaS vendors increase from a handful ten years ago to dozens today. At the same time, several of the enterprise iPaaS vendors (seeing the shift in the market) have attempted to pivot their products toward embedded iPaaS, with varying degrees of success.

What is enterprise iPaaS?

An enterprise iPaaS is a solution that enables the development, deployment, and support of integrations inside your company. This platform connects apps via integrations between internal business systems.

The platform has connectors and other tools to enable integrations among commonly available enterprise systems. It also allows developers to build integrations with niche and custom applications.

The important thing to remember about an enterprise iPaaS is that it is a general-purpose platform used by businesses to create integrations for internal use.

What is embedded iPaaS?

An embedded integration platform, or embedded iPaaS, is a set of tools that enables software companies to build reusable, configurable, native integrations and deliver them to your customers as features of your application.

In addition to the features of an enterprise iPaaS (integration designer, connectors, and infrastructure), an embedded iPaaS includes integration deployment and customer support tools, customer management, and an embedded integration marketplace.

The important thing to remember about an embedded iPaaS is that it is a purpose-built platform software companies use to create native product integrations for their customers.

Which platform is best for your integrations?

It comes down to whether you are building internal integrations (for your company) or external integrations (for your customers).

If you are solving for internal integrations, and sharing data between systems within your company, then an iPaaS is the right tool.

An enterprise iPaaS is ideal for the use case we mentioned, where you must combine several calendars for your company into one calendar that shows on your company intranet. You would be integrating data from several apps but doing so within your enterprise and for the benefit of your employees.

But if you need to address the integration question for your customers, sharing data from your SaaS app with the other apps your customers use, you should use an embedded iPaaS.

An embedded iPaaS is perfect for the use case we mentioned with your appointment scheduling app and multiple service industry customers. You would build these integrations to connect apps primarily for your customers' benefit.

Why you should consider an embedded iPaaS for your SaaS app

A traditional iPaaS does an excellent job of integrating systems within the enterprise, but it's not the right tool for B2B SaaS integrations. An embedded iPaaS is the only integration platform purpose-built for creating and managing customer integrations at scale.

You could try handling customer integrations with an enterprise iPaaS, but an iPaaS lacks the concept of customers. As a result, an iPaaS doesn't provide a way to efficiently build and deploy integrations for multiple customers (including customer-specific data management).

An enterprise iPaaS also tends to be a low-code/no-code environment. This works great to create workflow automation between internal apps but quickly reaches limitations with B2B SaaS apps. B2B SaaS companies often need to develop complex integrations that connect niche systems, and low-code/no-code isn't flexible enough to meet these requirements.

An embedded iPaaS includes low-code functionality and full development capabilities (including its API and code versioning in your existing dev ecosystem). This flexibility allows for low-code where it makes sense but doesn't box you in when custom code is required.

Finally, an enterprise iPaaS does not include tools for building reusable integration workflows and managing unique credentials and configurations for each customer.

An embedded iPaaS, on the other hand, is specifically designed for building and deploying integrations for your customers, including everything your teams need to manage and support each integration for each customer. An embedded iPaaS includes an integration marketplace where customers can view, select, and enable available integrations. They can also manage their integration configurations and perform first-level troubleshooting when there are problems.

Integration platforms help you do more with less

With businesses using more SaaS apps than ever before, data-sharing between those apps is essential for good business processes. Integrations are hard work, but integration platforms can significantly improve the efficiency of your integration-building process.

Be sure you are using the right platform for the job. An enterprise iPaaS is excellent for internal workflow automation within your enterprise. But an embedded iPaaS provides the additional functionality needed to build, deploy, and support integrations between your SaaS app and other apps in your customers' business ecosystems.

If an embedded iPaaS seems to support your use case, contact us for a custom demo showing you how Prismatic can supercharge your B2B SaaS integrations.