The five challenges in this guide aren't five separate problems — they're five dimensions of the same decision: whether the platform you're evaluating is actually built for ISVs, or whether it was built for a different use case and adapted. Platforms that solve all five are rare. Knowing exactly what to look for and verify makes the evaluation faster and the decision more confident.
This chapter consolidates the evaluation criteria from the previous five into a single checklist — organized by what to confirm before you trial, what to test during the trial, and what to ask vendors directly.
The Pre-Trial Checklist — Eliminate Before You Invest Time
These are the questions to answer before you start a trial. A "no" on any of them is an architectural disqualifier — no amount of feature richness elsewhere compensates for a fundamental mismatch with your deployment requirements.
| Question | What you need | Challenge area |
|---|---|---|
| Can it run on your infrastructure? | Self-hosted on Windows, Linux, or Docker — or cloud-only is acceptable for your customer base | Architecture fit |
| Does it support your application database? | Native connector confirmed for your DB type and version | Architecture fit |
| Does it support dynamic data source routing? | Per-tenant DB connection resolved at query time, not static configuration | Multi-tenant isolation |
| Is tenant isolation enforced at the platform layer? | Platform enforces isolation independently — not reliant solely on your application filtering | Multi-tenant isolation |
| Is SSO documented and self-implementable? | API-based token exchange, documented — no professional services required | Architecture fit |
| Is the pricing published? | Full pricing visible without a sales call | Vendor stability |
| Is the OEM license included? | Permitted to embed in products you sell — no separate agreement required | White-label branding |
The Trial Checklist — What to Test Against Your Real Data
The trial environment should use a copy of your actual database, not sample data. These tests only produce meaningful results against realistic data volumes and schema complexity.
| Test | Pass condition | Challenge area |
|---|---|---|
| Cross-tenant isolation test | User from Tenant A cannot access Tenant B's data via any path — UI, export, API, URL manipulation | Multi-tenant isolation |
| Row-level security export test | CSV export for a restricted user contains only permitted rows — no restricted data in the file | Multi-tenant isolation |
| Per-tenant branding test | Switching tenant context changes logo and color scheme correctly — no manual reconfiguration required | White-label branding |
| Scheduled export email test | Delivered email shows no vendor branding — sender domain and email template are configurable | White-label branding |
| SSO integration test | Authenticated user in your application passes through to analytics without a second login — implemented by your developer without vendor assistance | Architecture fit |
| Performance test against real data | Dashboard load time is acceptable against your largest customer's actual data volume | Performance |
| Cache validation test | Second load of the same report is meaningfully faster than first — cache is working | Performance |
| Support response test | A non-trivial technical question gets a substantive answer within your expected SLA — from someone with real product knowledge | Vendor stability |
The Vendor Conversation Checklist — What to Ask Directly
"What happens to my price at renewal?" The right answer is either "same rate, auto-renews" or a specific formula. Vague answers about market-rate adjustments are a signal.
"Who answers my support tickets in production?" The right answer names a team with specific product depth. "Our support team" without further specificity usually means a tiered queue.
"Is this one codebase or multiple acquired products merged?" The right answer for a stable, supportable platform is one coherent codebase. Multiple acquired products mean integration complexity and support specialization gaps.
"What's on your roadmap and how often do you ship?" Ask for a changelog. Frequency and substance of releases tells you how responsive the platform will be to your product's evolving requirements.
"What does the company's ownership structure look like?" Bootstrapped, profitable, and independent is the most stable long-term answer. VC or PE-backed means exit pressure that can change the product direction, pricing, or support model at any time.
What a Platform That Solves All Five Looks Like
The platform that solves all five challenges without requiring significant custom engineering from your team:
Enforces multi-tenant isolation at the platform layer — dynamic data source routing, query-level row security, per-tenant cache namespacing. Supports per-tenant branding with unlimited configurations, including scheduled export email customization. Runs self-hosted on your infrastructure in any environment your customers require. Includes in-memory caching for performance at scale, with configurable invalidation per report. Has published pricing that doesn't change at renewal, an OEM license included in every plan, and support from the engineers who built it.
That's what Yurbi is built to be. Whether it's the right fit for your specific deployment depends on your architecture, your data model, and your requirements — which is exactly what a trial is for.
The trial includes a full sandboxed environment. Connect your data, run the security tests from this chapter, test the SSO integration, and evaluate the performance against your real data volumes. No consultants, no guided setup — just the platform and your developer.
Where to Go From Here
Still deciding whether to build or buy? The Build vs. Buy guide covers the full cost breakdown, multi-tenant technical requirements, and a weighted scorecard to work through with your team.
Ready to evaluate vendors? The Embedded Analytics Buyer's Guide covers pricing models, architecture evaluation, the vendor assessment process, and what a meaningful trial looks like.
Want to run the cost numbers first? The build vs. buy calculator takes your team size, time allocation, and salary inputs and gives you a specific comparison against Yurbi's published flat pricing.
Stop rebuilding your reporting layer.
Embed Yurbi into your product and ship analytics to your customers in weeks — not quarters. Self-hosted, white-labeled, flat annual pricing.
Download Free Trial