Izenda is a legacy product.
Here's where to go next.
Insightsoftware — Izenda's owner since 2021 — focuses its investment on Logi Symphony and promotes migration from Izenda to Symphony. Izenda still ships maintenance releases, but feature development is limited. If you're an ISV who embedded Izenda evaluating what comes next, this page covers what's actually happening and how Yurbi compares as an alternative.
What "legacy status" means for your product
If you embedded Izenda in your product, here's what Insightsoftware's decisions mean in practical terms for your business.
Limited feature development. The investment is in Symphony.
Izenda is still shipping releases — v2025.4.1, v2026.2.1, and v2026.3.1 (adding .NET 10) among them — but feature development is limited, and insightsoftware's investment is focused on Logi Symphony. Don't plan on the vendor closing the capability gaps you have today. Any significant feature you need going forward may be one you build yourself or do without.
Support keeps the lights on. The roadmap is elsewhere.
Support for a legacy product means someone helps you keep what you have running — not a team invested in where your product goes next. Insightsoftware's attention and investment are concentrated on Symphony. You're on the maintenance track, not the product roadmap.
The pricing leverage is gone. Renewals are negotiated.
Insightsoftware doesn't publish Izenda pricing. Renewals are negotiated — and when your product is embedded and dependent, the negotiation is not in your favor. Insightsoftware is a private equity-backed company that has grown through acquisitions, including Logi, Izenda, Exago, and Dundas.
The migration is coming. The question is whose timeline you're on.
Insightsoftware actively promotes migration from Izenda to Logi Symphony. They haven't published an end-of-life date, and maintenance releases continue — but a product Gartner lists as Legacy, with limited feature development while its owner promotes a successor, is a product to plan around. The difference between migrating now and migrating later is whether you do it on your schedule or theirs, and whether you choose your next vendor or are pushed toward one.
Izenda vs Yurbi — for ISVs evaluating a replacement
What migration from Izenda to Yurbi actually looks like
It's a real project — we won't pretend otherwise. But it's structured and has a definite end, unlike the indefinite cost of staying on a legacy platform.
Trial + data connection
Download the Yurbi trial and connect it to the same databases Izenda currently queries. No data migration — Yurbi queries your existing databases directly. This step takes hours, not weeks.
Semantic layer + tenant setup
Configure Yurbi's semantic layer to match your data model — table relationships, field naming, row-level security rules per tenant. If you had this configured in Izenda, most of the logic maps directly. This is the core of the migration effort and where our services team can help.
Rebuild your active report library
Yurbi's no-code builder recreates your existing reports and dashboards. In practice, most ISVs find they don't need to recreate everything — the reports customers actually use is a smaller set than the total library. We can assist through our done-for-you services offering.
Embed + white-label configuration
Update your application's embed code to point to Yurbi (iframe + API). Configure per-tenant branding — logo, colors, domain. Your customers see no disruption, just an improved analytics experience under their own brand.
Parallel run + cutover
Run Yurbi alongside Izenda during a validation period. When you're satisfied, cut over. At that point you have a predictable annual cost, a vendor who answers support directly, and a product being actively developed — not maintained into retirement.
Why ISVs leaving Izenda don't all go to Logi Symphony
Logi Symphony is Insightsoftware's answer for Izenda customers. For some organizations it may be the right call — particularly those already deep in the Insightsoftware ecosystem or with enterprise-scale requirements. But ISVs evaluating it should go in clear-eyed.
-
It's a re-implementation — not an upgrade path
Symphony is not Izenda with improvements. It's a migration to a different product built from four acquired codebases (Logi Composer, Dundas, Izenda, Exago). If you're doing that work anyway, you're choosing your next embedded analytics vendor — not updating your current one. That choice is worth making deliberately.
-
No published pricing — and a PE-backed negotiation dynamic
Logi Symphony pricing requires a sales call. Insightsoftware is a PE-backed company that has grown through acquisitions and explicitly targets enterprise customers. Factor in what renewal looks like once you're embedded and dependent — because you've already seen that movie with Izenda.
-
Their strategic direction is enterprise and cloud — not mid-market ISV
In November 2024, Insightsoftware launched Symphony on Google Cloud Marketplace and deepened their Vertex AI and BigQuery integrations. Their investment is clearly aimed at large enterprise and cloud-native buyers. If you're a mid-market ISV who needs embedded analytics that's self-hosted, predictably priced, and focused on your deployment model, that's not who Symphony is being built for.
-
You've been through this before
The situation you're in now — a vendor who's less responsive, pricing that's harder to predict, a roadmap that's not yours — is what happens when a small focused vendor gets absorbed into a large PE portfolio. The question is whether you want to rebuild that risk into your product again with the same parent company.
- Bootstrapped — no PE, no exit pressure
- One code lineage since 1999 — not acquisitions
- Published pricing from $10,000/year
- Same renewal rate — written into how we operate
- Weekly releases — not annual roadmaps
- You talk to engineers — not a support queue
- Free trial — test on your actual data today
Izenda replacement questions, answered directly
Insightsoftware hasn't published an end-of-life date, and Izenda is still shipping maintenance releases — v2026.3.1 (August 2026, adding .NET 10) and v2026.3.2 (October 2026) are the most recent. But the direction is clear. Gartner Peer Insights lists the product as "Izenda BI Platform (Legacy)." Feature development is limited, insightsoftware's investment is focused on Logi Symphony, and it promotes migration from Izenda to Symphony. That's a product to plan around, not one to build your next five years on.
You can, and for some organizations it may be right — especially if you have enterprise-scale requirements or are already in the Insightsoftware ecosystem. What's worth evaluating carefully: Symphony pricing requires a sales call and is positioned at the enterprise end of the market. The migration is a re-implementation to a different product, not an upgrade. Insightsoftware's 2024 investments — Google Cloud Marketplace, Vertex AI integration, BigQuery — signal their strategic focus is large enterprise and cloud-native buyers, not the mid-market ISV segment.
We're honest that Symphony exists and may fit some buyers. For most ISVs evaluating Izenda alternatives, the combination of published flat pricing, a single stable codebase, and a vendor whose business doesn't depend on acquisition-driven growth makes Yurbi the better fit — but make that call after seeing both options clearly.
It's a real project — we won't pretend otherwise. The data itself doesn't move — Yurbi queries your existing databases exactly as Izenda does. What you're recreating is the semantic layer configuration (table relationships, field naming, security rules per tenant) and your active report library. For most ISVs, the semantic layer maps fairly directly from Izenda's data model structure. The report rebuild depends on how many distinct reports are actively in use — in practice, most ISVs have fewer than they think.
Typical timeline is 4–8 weeks from trial to production cutover for a mid-size ISV deployment. We'll give you a more specific estimate after a demo where we understand your architecture and report volume.
Yurbi supports MS SQL Server, PostgreSQL, MySQL, Oracle, and other databases via ODBC (Snowflake, Redshift, BigQuery, MongoDB Atlas, and others). If your Izenda deployment runs against MS SQL or PostgreSQL — the most common Izenda databases — Yurbi connects natively with no additional driver setup. For other sources, check the integrations page or ask in a demo — we'll tell you directly if there's a gap before you invest evaluation time.
Yurbi publishes pricing: Starter at $10,000/year (up to 75 users), Growth at $18,000/year (up to 250 users), Scale at $24,000/year (up to 500 users), Unlimited at $30,000/year. Additional production deployments from $500/year each. All features included at every tier — no paywalls. See the pricing page for the full breakdown.
We don't know what you're paying Insightsoftware today because they don't publish it. What we do know: customers who've switched have found Yurbi's flat-rate model significantly more predictable — especially at scale where Izenda's negotiated renewal model becomes unpredictable.
A few things to evaluate honestly: Yurbi embeds via iframe and API — there's no JS SDK for deeply programmatic embedding (API docs at developers.yurbi.com). SSO is session-token based via our DoLogin API (plus Windows/AD and header-based SSO); native SAML/OIDC is in development. Sign-in security already includes two-factor sign-in (app, email, or text), Cisco Duo, breached-password screening, and account lockout. Dashboard interactivity is parameter and global filter driven — no associative click-through filtering between widgets. Mobile is functional but not a primary focus.
We'd rather you know these things now than discover them post-implementation. If any are hard requirements, tell us in a demo and we'll give you an honest assessment of fit rather than work around the question.
That's a real constraint — we're not going to dismiss it. The practical answer: start the evaluation now, before any contract clause becomes an active blocker. Migration timelines are measurable. If you begin today, you know when you'll be ready to cut over — and you can plan customer communications and contract renewals accordingly. Waiting until Insightsoftware's migration pressure increases means you're migrating under pressure instead of on your timeline.
All statements about Izenda and Insightsoftware are sourced from publicly available communications — press releases, Gartner Peer Insights listings, product pages, release notes, and official announcements. The "legacy" designation comes from Gartner Peer Insights, which lists the product as "Izenda BI Platform (Legacy)." Release dates come from Izenda's published release notes. Statements about insightsoftware's focus on Logi Symphony reflect its public migration messaging. Last reviewed October 2026. If something has changed, let us know and we'll update promptly.
