Decision FrameworkDecision layer

Yurbi: Buy vs Skip (Self-Hosted Embedded Analytics for ISV Clients)

IF your client base includes at least one ISV or SaaS team that needs white-label dashboards inside their own product, can host the instance on their own infrastructure, and will commit to a named-user count that fits a tier, THEN buy Yurbi at Starter ($833.33 monthly, billed annually, up to 75 named users) or Growth ($1500 monthly, up to 250 named users) and resell it as a deployment plus retainer engagement. IF the client needs a vendor-hosted cloud product, has no server staff, or sits below roughly 75 named users with no growth path, THEN skip Yurbi and defer until a self-hosted ISV engagement actually appears in the pipeline.

By InnovaAI ResearchPublished

Embedded Analytics
Decision Frame

Yurbi: Buy vs Skip (Self-Hosted Embedded Analytics for ISV Clients)

“IF your client base includes at least one ISV or SaaS team that needs white-label dashboards inside their own product, can host the instance on their own infrastructure, and will commit to a named-user count that fits a tier, THEN buy Yurbi at Starter ($833.33 monthly, billed annually, up to 75 named users) or Growth ($1500 monthly, up to 250 named users) and resell it as a deployment plus retainer engagement. IF the client needs a vendor-hosted cloud product, has no server staff, or sits below roughly 75 named users with no growth path, THEN skip Yurbi and defer until a self-hosted ISV engagement actually appears in the pipeline.”

When is it the right choice?
  • Client runs SQL Server, PostgreSQL, MySQL, Oracle, or ODBC and wants reporting read directly from that database with no ETL layer built by your delivery team
  • The engagement requires on-premises or air-gapped deployment, which rules out cloud-only embedded analytics vendors
  • Client is replacing Crystal Reports or SSRS and needs end customers to build ad-hoc reports without SQL knowledge
  • Named-user count lands inside a published tier (75 users at Starter, 250 at Growth) so the annual commitment is predictable across the retainer
  • Client product needs tenant isolation enforced at the query layer via App Shield rather than application-side filtering you would have to maintain
When should you skip it?
  • Client expects a fully managed cloud service; Yurbi is self-hosted only, so your agency absorbs deployment and server management
  • Account sits well under 75 named users with no expansion plan, making the Starter annual commitment hard to justify against the client's budget
  • Your agency has no one who can configure database connections, App Shield tenant policies, and server infrastructure for the client
  • Prospect wants AI-native analytics or an SDK-first embed model, which is where the category's other platforms position themselves
  • Client needs analytics live in days with no infrastructure review; Yurbi's medium setup complexity will not fit that timeline
embedded-analytics
Open the Yurbi courseYurbi decision recordBrowse the Academy

More on Yurbi

More for Embedded Analytics