BI Trends

Looker Alternatives: 6 Considerations when Comparing Looker vs. Logi Analytics

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

Are you looking for the ability to add analytics to your application? If so, you’re in luck: Any Google search will return hundreds of options for embedded analytics vendors.

But the downside of all these choices is how difficult it’s become to parse through requirements and find the right solution. At Logi, we work with a lot of companies that want to either correct a wrong choice or avoid making a poor choice in the first place.

>> See Firsthand how Logi Analytics Compares to Looker: Start Your Free 15-Day Trial <<

Those companies that have worked with or considered Looker often find it to be a good choice for analysts who need to conduct data queries. But for product managers and application teams that need to rapidly embed analytics, Looker’s basic visualizations and poor extensibility often fall short.

Read on for key considerations when considering Looker alternatives and comparing Logi Analytics to Looker.

1. Cumbersome Security Requirements

Looker requires you to replicate your security model within its application, with security configured in a proprietary way. This makes it very difficult to create comprehensive row- or object-level security rules. The approach is not an issue if all your users are accessing the same reports and data, but that is rarely the case. Most application teams want to restrict access to things like HR and finance data to subsets of those authorized users. Doing this in Looker is quite difficult. Looker also has limited support for multi-tenant deployments.

2. Looker’s Data Drawbacks

Connecting to data sources in Looker is confusing. And that is just for the data sources you can work with. Looker only works with their predefined list of sources. The result is a difficult, time-consuming process to connect data before you can even begin building analytics to earn new insights.

3. Rigid Deployment

You can’t adapt from the Looker model of create/deploy/share. While that may sound like a perfectly fine pathway, it means you need to create all of your models and business rules upfront, as well as design your queries before you can start sharing and managing visualizations.

4. Limited Customization and White Labeling

With Looker, the options for extensibility or customization are extremely limited. In particular, software developers looking to embed analytics will encounter numerous obstacles and will find it very difficult to re-use existing code on which they already rely.

Looker’s top priority is their own brand—not yours. Looker strives to go along for the ride and advertise their own brand inside your application. Even if you pay to remove the “Powered by Looker” branding, you’re still stuck with limited capabilities to seamlessly customize the analytics for a consistent look and feel in your application. Looker’s style changes are very basic. You can change colors, fonts, and logos, but that’s about it.

5. Constrained Presentation Capabilities

The functionality of Looker is also limited to essentially co-presenting analytics. While this may be perfectly adequate for some uses cases, the fact is this eliminates the possibility for many advanced capabilities. In our experience, many software vendors choose to embed Logi because their needs outgrew the capabilities of their current analytics solution, whether they purchased a third-party tool or built their analytics in house. Because no one can perfectly predict the future, selecting a more full-featured application to embed analytics makes your choice more future-proof.

6. A Steep Learning Curve

Getting started with Looker requires extensive, lengthy training. Users must learn a proprietary language, LookML, in order to begin building models. Because it is proprietary, there’s no using it outside of Looker, and you’ll need to retain Looker experts to set it up and maintain it. Developers must also create a full model and business rules before they are able to build dashboards and visualizations.


Looker Alternative: Looking at Logi Instead

In stark contrast to Looker, Logi Analytics offers a developer-friendly environment with a robust set of capabilities ready for you to embed whenever you need them. Some benefits of Logi include:

  • Integrates with Your Security. Logi SecureKey doesn’t require you to replicate your security. Adaptive security leverages your existing security model, eliminating time-consuming and costly duplicative efforts. We also support multi-tenancy so you can manage all security settings in one place.
  • Seamlessly Embedded Analytics. With Logi’s flexible themes, you can embed analytics that look like your application without coding it all yourself. Logi Analytics empowers you to control the function, appearance, and location of every element and create a completely seamless user experience.
  • Scalable Pricing Terms. Analytics are aligned with your pricing model and don’t require additional licensing investments.



Originally published June 9, 2017; updated on August 3rd, 2017

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.