Logi Symphony is four acquired products still being integrated.
Yurbi is one codebase.
Logi Symphony combines Logi Composer, Dundas BI, Izenda, and Exago under the insightsoftware brand. For two of those four products — Izenda and Exago — insightsoftware promotes migration to Symphony, and Gartner lists Izenda as Legacy. Symphony itself is actively developed, but independent analysts confirm integration work remains ongoing. If you're an ISV evaluating Symphony for your product, that context matters before you commit.
Four things ISVs need to know before embedding Logi Symphony
Symphony is actively developed and has real capabilities. These are the structural questions worth asking before you commit to embedding it in a product your customers depend on.
Integration is still ongoing — confirmed by independent analysts
Symphony launched in October 2023, combining Logi Composer and Dundas BI. A Ventana Research analyst noted directly after launch: "There will be additional work required to integrate more of the capabilities of the various products that have been acquired." Izenda and Exago remain separate products, with insightsoftware promoting migration to Symphony in parallel. When you embed Symphony today, you're embedding a platform that is still being stitched together — and the seams surface at support time, not at demo time.
Izenda and Exago users are being migrated now — the pattern is established
insightsoftware promotes migration from Izenda and Exago to Symphony — with migration webinars and dedicated onboarding — and Gartner lists Izenda as Legacy. ISVs who embedded Izenda believing it was stable lived through exactly this cycle. The same PE-backed acquisition model that produced Izenda's sunset applies directly to Symphony: insightsoftware has made 25+ acquisitions and their roadmap reflects their full portfolio and their investors' exit timeline, not your product's embedding requirements.
No published pricing — and a PE structure built for exit, not long-term ISV stability
Logi Symphony pricing requires a sales engagement. insightsoftware is backed by Hg Capital and TA Associates in a joint-control transaction valued at approximately $4 billion (July 2021). PE-backed software companies optimize for the exit event. For ISVs who embed and become dependent, that creates a structural leverage problem at every renewal: you can't leave easily, and they know it. Izenda customers facing a migration decision are in exactly that position today.
Support spans a 25+ product portfolio — ISV embedding is one voice among many
insightsoftware supports more than 25 products across financial reporting, EPM, ERP integrations, analytics, and data management. Symphony's roadmap serves enterprise internal BI teams, regulated-industry buyers, Dundas customers, migrating Izenda customers, and ISVs embedding analytics — all with different requirements. When you submit a support ticket or request an enhancement, your urgency competes with all of them. At Yurbi, you talk to the engineers who built the product. Feature requests have a realistic path to your version in weeks, not quarters.
Logi Symphony vs Yurbi — for ISVs embedding analytics in their product
Logi Symphony pricing not published — contact insightsoftware directly for a quote. Competitor information based on publicly available sources as of October 2026. Yurbi pricing is published here.
Being pushed from Izenda to Symphony?
You have a choice.
insightsoftware is actively running Izenda-to-Symphony migration programs. Before you begin that work, it's worth knowing: the migration effort itself is comparable to switching to any other embedded analytics platform.
The migration math works both ways
Moving from Izenda to Symphony means rebuilding your semantic layer, your report library, and your embedding integration — regardless of which platform you land on. That work is largely the same whether you go to Symphony or to Yurbi. The difference is the vendor relationship you're building into for the next 5–10 years.
If you migrate to Symphony, you're moving from one insightsoftware product to another within the same PE-backed portfolio — with the same unpublished pricing, the same renewal leverage dynamic, and the same acquisition-driven roadmap. Izenda customers who evaluated Yurbi at the point of forced migration found the published pricing, bootstrapped ownership, and ISV-specific multi-tenant architecture made a meaningful difference to their long-term cost model and vendor risk profile.
Download the Yurbi trial and run a parallel evaluation before you commit to the Symphony migration path. A few hours of setup gives you a working embed, published pricing you can compare directly, and real data — before you're locked in.
Logi Symphony vs Yurbi — questions answered directly
The Dresner recognition is real and worth acknowledging — with the nuance that the eleven-year run belongs to the insightsoftware/Logi lineage, not to Symphony itself, which launched October 10, 2023. Symphony scored well on embedded BI capabilities in Q3–Q4 2025, and the platform has genuine technical depth — particularly for regulated-industry buyers who need on-premises AI, and for teams who want API-first component embedding rather than iframes. Those are real differentiators.
The question worth separating is: "Is Symphony a capable platform?" versus "Is it the right vendor relationship for my ISV product over the next decade?" The first question is yes. The second depends on whether unpublished pricing, PE-backed ownership at $4B valuation, and an ongoing integration program fit your specific risk tolerance. Dresner evaluates the technology — it doesn't evaluate what happens to ISVs at renewal when they're captive to a PE-backed portfolio company.
For ISVs currently on Izenda or Exago, it means pressure to migrate on insightsoftware's timeline: insightsoftware promotes migration from both to Symphony, and Gartner lists Izenda as Legacy. The migration programs are real — webinars and dedicated onboarding — and they're running now.
For ISVs evaluating Symphony as a new platform, it's relevant context about the pattern: insightsoftware acquired four analytics products in roughly 18 months, built Symphony around two of them, and is steering customers of the other two toward migration. There is no structural reason Symphony couldn't go through the same cycle if insightsoftware acquires a more strategically valuable product or if the PE exit timeline shifts priorities. The platform you embed is a long-term commitment — the vendor's acquisition history is the most direct evidence of how they treat their existing products over time.
Yes. The migration effort is comparable in both directions — you're rebuilding the semantic layer, the report library, and the embedding integration regardless of where you land. The technical work itself is similar. The decision that differs is the vendor relationship and pricing model you're committing to for the next several years.
Yurbi is built specifically for the ISV embedding use case: multi-tenant isolation, dynamic data source routing, per-tenant white-label branding, and flat published pricing from $10,000/year are all included in every plan. The Yurbi vs Izenda page covers what the migration path looks like in practice — with realistic timelines and what the technical work actually involves.
Yes — specifically because you're in a sales process. Symphony pricing is negotiated; having a credible published alternative on the table improves your negotiating position regardless of which product you ultimately choose. A parallel Yurbi trial costs a few hours of setup.
Download the trial, connect it to your database, and you'll have a working embedded dashboard before the next sales call. That gives you something insightsoftware can't give you before a signed contract: actual platform experience and a real, non-negotiated price to compare against their quote.
For the core ISV embedding use case — multi-tenant data isolation, per-customer white-label branding, dynamic data source routing, no-code report building, and performance caching — Yurbi covers the critical capabilities well. For most mid-market ISVs (11–250 people), Yurbi's feature set handles the embedding requirements their products actually need.
Where Symphony has genuine advantages: API-first component embedding without iframes, Logi AI for on-premises natural language analytics and LLM integration, a broader visualization library, and broader SSO support. Yurbi's known gaps: embedding is iframe and API only with no JS SDK; SSO is session-token via our DoLogin API rather than SAML or OIDC (native SAML/OIDC is in development; sign-in does include two-factor by app, email, or text, Cisco Duo, breached-password screening, and lockout); dashboard interactivity is parameter and global-filter driven rather than associative click-through; no AI analytics currently. See the features page for the full breakdown, or ask in a demo for an honest fit assessment.
Three concrete implications. Predictable upgrade behavior: a code lineage built incrementally over 25+ years has known failure modes that have been addressed. A codebase assembled from four acquisitions has integration points still being discovered — and your production upgrade is when you find them, not when the vendor does.
Support depth: Yurbi's engineers have worked on the same codebase throughout its history. When you open a ticket, the person responding has context going back years. At a company assembled from four separate products in 18 months, that institutional knowledge is fractured across teams that used to be separate companies with separate cultures and separate tools. Release cadence: weekly releases are only possible with a single coherent codebase. Coordinating releases across merged legacy architectures is exactly why enterprise vendors ship quarterly at best.
Annual flat tiers: Starter at $10,000/year (up to 75 named users), Growth at $18,000/year (250 users), Scale at $24,000/year (500 users), Unlimited at $30,000/year. Each plan includes one development and one production deployment. Additional production deployments are $500/year each at list rate, with volume discounts beginning after 10 additional deployments and decreasing significantly at scale. All features are included in every plan with no feature paywalls between tiers.
For large-scale or startup deployments, contact us — volume pricing applies for large deployment counts, and startup pricing exists for early-stage ISVs. See the pricing page and full deployment calculator for specifics.
