We’re constantly speaking with software vendors that are searching for white label analytics, embedded analytics, OEM analytics dashboards to integrate with their existing web-based or non-web-based applications. Many of these companies are deciding whether to build their own reporting solution or buy one. Others have decided that they need more robust interactive dashboard and reporting in their product, and they don’t have the resources to build their own.
In both cases, the companies we speak to often have complex use cases and requirements for a white label analytics solution. By the time most companies discover Yurbi, they are frustrated and have expressed the shortcomings of other products. Thankfully, in many of these use case scenarios, Yurbi ends up being a great fit. In this article, we’ll dive deeper into four of the most complex white label analytics scenarios we have run into and helped solve:
When you think about SaaS or web application databases, many would conclude that all of the vendor’s data is stored in a single multi-tenant database within the cloud. We find this model to be less common than expected. Many of the SaaS and web-based application vendors who have approached us have multiple databases, designed for each customer. This type of situation can be challenging from a white label dashboard perspective, both in technology and pricing. In these use cases, security at the tenant level can easily be handled since all customer data is stored in a separate database. But when there is a requirement for multiple security roles per each individual customer, security configuration can be a technical nightmare. The other challenge is trying to create a core set of reports and dashboards that can dynamically pull from the right database per tenant. Many solutions require a hard-coded view per database.
How Yurbi Helps: Yurbi solves this challenge by employing a flexible approach via Yurbi Apps to multiple databases, and through App Shield that accomplishes multi-role security. Yurbi is also able to package content to distribute among multiple databases, and Yurbi’s API allows for user provisioning and updates that span all of the user instances.
In the ideal world, every customer looks exactly alike and many software companies enforce rules that outlaw customer customization. However, we encounter software vendors every day that allow custom database schemas per customer that either add new fields entirely or relabel fields within the database for specific customers while keeping the database architecture the same. (For example, for helpdesk customers, one customer may use the field name “ticket,” while the other might use the field name “request.”) In all custom database schema scenarios, whether at the database or customer-facing level, challenges arise because the white label analytics solution must display dashboards that are relevant to each customer.
How Yurbi Helps: Yurbi tackles this complex scenario through the personalization available within the Yurbi App, which allows for schema customization. In this instance, a company would create different Yurbi Apps and assign the appropriate Yurbi App to each customer through Yurbi’s API.
We have a lot of software vendors who come to us because they want to ease their users into BI by offering different levels of reporting to their customers. For example, one level may be very basic, easy-to-read dashboards provided at no cost, and another level may contain more complex reports and dashboards at an additional cost for power users.This type of scenario is challenging from a licensing standpoint because it adds complexity to BI provider contracts. Another challenge arises because many white label analytics solutions do not have the ability to limit access to specific features and reports, and it becomes an all-or-nothing reporting scenario.
How Yurbi Helps: Luckily, Yurbi has a great solution for these environments because Yurbi uses a user tier-pricing model instead of a per-user pricing model. This allows software vendors to customize the distribution of their BI offerings without the confusion of variable BI pricing. Yurbi’s clear, transparent, fixed price per year OEM pricing makes cost modeling much easier. Yurbi also offers features that support tiered offerings such as allowing vendors to package premium content which can be licensed and allocated to specific users or tenants. Additionally, Yurbi’s CustomJS allows vendors to modify Yurbi’s interface and customize the areas of the product to which customers should have access to based on their subscribed tier.
It’s easy to assume that most software vendors are developing SaaS applications and moving all of their data and business activities to a single place in the cloud. However, we see many companies that are still deploying on-premise solutions, like Yurbi. These vendors need an on-premise white label analytics solution. In these scenarios, vendors are often limited to traditional BI solutions, such as Business Objects or IBM Cognos. These solutions are often a poor fit for software vendors because the traditional BI solutions don’t have the ease of use and features the vendor’s customers expect, such as ad-hoc reporting and interactive dashboards. Most of the BI products on the market that have these features primarily support SaaS vendors, and do not work well with on-premise software vendors.
How Yurbi Helps: Yurbi is a great fit for on-premise software vendors because Yurbi itself is an on-premise solution that gives vendors the ability to integrate Yurbi into their servers and databases. Secondly, Yurbi requires a lightweight server versus heavier system requirements set by traditional BI companies, which allows for faster and easier installation.
Yurbi was designed to be a platform that can be configured and customized for numerous use cases. When we speak to customers and partners who express the complexity of their use cases and the limitations of other white label analytics vendors, they begin to see how dynamic Yurbi is as it’s able to fit both their needs and their budget requirements. We also enjoy these conversations because as we hear about new use cases and challenges, we incorporate them into our product roadmap so that we are able to resolve even more complex white label and OEM analytics scenarios.