See how you can create, deploy and maintain analytic applications that engage users and drive revenue. See a Logi demo

Buying BI

3 Izenda Limitations to Keep in Mind

By Josh Martin
Share on LinkedIn Tweet about this on Twitter Share on Facebook

Izenda has a reputation as an option for software companies that have basic BI requirements. However, its focus on bare-bones capabilities has limited its offering in several key areas, including customization, security, and future-proofing your embedded analytics.

Initially, you may think basic analytics capabilities from a low-cost provider will satisfy your customer demand for analytics. However, over thousands of engagements and years of research, we have learned that in order to use analytics as a competitive differentiator and revenue driver, these basic features simply don’t cut it.

Application teams facing demands for more mature analytics capabilities will need to consider some Izenda alternatives. Consider these three Izenda limitations and how the product compares to other BI vendors.

1. Izenda Takes a Long Time to Deploy

Izenda makes it easy for developers of all skill levels to change an application’s look with easy access to fonts and color modification. But for companies that need more granular customization (a necessity for creating competitive differentiation), they’ll need to first become familiar with the Izenda programming language and then begin hand-coding these customizations into the system. Some features—including the authoring page, scheduler, and email—cannot be customized and are restricted to their out-of-the-box functionality and layout.

By requiring coding for all but the most basic customization, Izenda’s platform demands three things: First, more skilled developers to leverage its offering. Second, more time to write, check, and document what code has been written. And third, extra ongoing maintenance to ensure custom code doesn’t break after every software update. The long-term result is more expense, longer implementation, and higher ongoing costs for a less capable end-product.

2. Your Application Becomes a Dumb Pipe

Izenda is great for embedding basic self-service analytics, aimed at satisfying customers that have ad-hoc analytics requests. However, application teams realize that to engage today’s sophisticated user, they must offer a more complete experience.

Some of this complete experience comes from capabilities such as write-back and workflow—both of which help keep users in your application. Database write-back, for example, allows a sales manager to preview the impact of reassigning a territory on a map and then make those changes permanent in the database. Workflows allow users to send an email alert at a certain threshold or kick off a custom marketing automation campaign for a segment of users—all without leaving the application.

Unfortunately, Izenda fails to support advanced features like these. And without them, users tend to export data to Excel or elsewhere to perform analysis, share findings, and act on the results. This turns your application into a dumb pipe: It can provide numbers, but not the high-value activities required to immediate act on the data.

Sophisticated analytics capabilities are made even more powerful through tailored experiences, powered by the ability to control every facet of an application based on users’ roles and rights. Izenda’s limited customization options mean your users get their singular experience instead of a tailored application that drives ongoing engagement.

3. Limited Data and Platform Support

Izenda only offers the most basic connectivity to databases, excluding out-of-the-box support for sources such as Redshift, Vertica, and Teradata. Additionally, while Izenda has supported .NET for years, its recent claims to also support Windows and Java appear unsubstantiated by market evidence and product documentation.

To compensate for this, Izenda allows its customers to write custom code to connect to different databases. However, this approach means customers need to hire experienced developers to staff their Izenda implementation. It will take a long time to create custom experiences that end users want and will require developers spend significant time checking and updating their code with every service pack or dot release, distracting them from working on the core application.

Izenda Alternatives: High Stakes Require Long-Term Reliability

When you develop mission-critical applications, you need an embedded analytics vendor that supports modern capabilities and offers ongoing professional support. Your users’ needs will inevitably shift and expand over time. If you embed a solution that isn’t designed to meet future needs, you’ll be forced to rip it out and start all over very quickly.

If you require customized embedded analytics and BI solutions that offer more than a short-term solution, consider partnering with an embedded analytics platform such as Logi Analytics. Logi has been recognized repeatedly as a leader in embedded by independent analyst firms such as Dresner Advisory Services. Logi has grown steadily for over 17 years and has helped thousands of application teams create more valuable applications, engage users, and differentiate their software products.



Originally published September 28, 2017; updated on January 18th, 2020

About the Author

Josh Martin is the Director of Product Marketing at Logi Analytics. Prior to joining Logi he was an industry analyst covering bleeding edge distribution channels and their impact on the consumer market. In this role he was a thought leader and advised clients on how to successfully benefit from market shifts while positioning products and services for long-term success. Josh holds a Bachelor degree in Business from Babson College.

Subscribe to the latest articles, videos, and webinars from Logi.