Updated on by Hayley Brown
There has been an increase in embedded iPaaS options of late, designed to help with SaaS integration. Many have come from big iPaaS brands who imply their option is completely white-labelled.
We wanted to further discuss what embedded means as well as what white-label should look like.
What does embedded mean?
The word embedded means fixed firmly or deeply in a surrounding mass. For instance, mobile phones consist of many embedded systems such as GUI software, operating systems, cameras, microphones etc.
What does white-label mean?
A white-label SaaS is an unbranded product purchased by a company and rebranded as one’s own.
For instance, a SaaS decides to purchase, rent or lease a product and/or services of a software company. Based on a monthly subscription fee. This is then provided unbranded. It can then be customised according to the business’s style guides, and then sold and used by customers.
How is this applied to an integration service application?
In regards to integration platforms, an embedded iPaaS such as Cyclr is a white-label platform that sits within a SaaS unseen to SaaS customers. Whereas an iPaaS such as Zapier or Tray.io sits externally and can be seen by end-users.
Why is that? The goals of the two different iPaaS systems are different. An embedded iPaaS help SaaS vendors expand their integration functionality without adding to the developer backlog. As well as eliminating the need to build processes from scratch. This means features and integration functions can be added to a SaaS product easily and without expensive development resources.
Whereas an iPaaS allows users to connect to other SaaS applications they use and develop and deploy data workflows across these apps. In other words, they are designed to automate internal business processes that will reduce manual repetitive tasks and automate data flows.
Examples of what isn’t a white-label embedded application
It has become increasingly common for iPaaS applications to reengineer their platforms and offer an ‘embedded’ version of their original iPaaS. This means they should be white-labelled and invisible to customers of a SaaS.
However, we’ve noticed these embedded solutions aren’t as invisible as promised. Instead, they often require SaaS users to create a separate account with the iPaaS provider.
This is most obvious when users are authorising an application for data access. For example, if a user wants to integrate your SaaS with a sales tool like Salesloft they are required to not only have an account for Salesloft but with Tray or Zapier as well.
The image below is an example of this:
White-Label means White-Label
An embedded iPaaS should be a fully white-labelled platform with integration capabilities. These platforms are within a SaaS and the SaaS can use workflow automation tools to expand their native integration functionality for their end-users. During the authentication processes end-users don’t need to create a separate account with the embedded integration platform.
As a result, friction is reduced as well as exposure to potential competition.
The beauty of Cyclr is that we are first and foremost an embedded iPaaS and designed as so rather than being reengineered. As well as this, we are truly white-labelled, your customers won’t see us nestled in your SaaS. We serve you our customers and help you serve integrations to your customers, invisibly!
Want to learn more about Cyclr and Embedded iPaaS?
Get in touch and choose whether you want a demo, a free trial or just ask questions our team are ready and waiting to get your integration journey started!