Logi Info (or the Logi Analytics Platform) is a developer-grade analytics platform designed for application teams needing to rapidly build, deploy, and maintain mission-critical applications. Logi serves the embedded model, so companies increase the
likelihood of building valuable, long lasting applications. The vendor focuses on enriching embedded analytics
capabilities so that their customers' applications become more valuable, faster. According to the vendor, Logi allows customers to…
N/A
Looker
Score 8.2 out of 10
N/A
Looker is a BI application with an analytics-oriented application server that sits on top of relational data stores. It includes an end-user interface for exploring data, a reusable development paradigm for data discovery, and an API for supporting data in other systems.
N/A
Pricing
Logi Info (Logi Analytics Platform)
Looker
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Logi Info (Logi Analytics Platform)
Looker
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
No setup fee
Required
Additional Details
Logi's pricing was developed with software vendors in mind and as such, we offer flexible, custom pricing aligned with your go-to-market approach and long-term growth plans. Our pricing objective is to ensure our partners can rapidly scale their analytics.
Well Suited - It's very easy for a non-developer to make clear/easily understood important data displays Great options for displaying data, UI provides great assistance helping you determine what chart, graph etc., to utilize for peak output. Saves tons of developer hours by allowing non-developers to be able to create and design things. Less Suited - It's not a big fan of displaying 1000 page PDFs but with adequate setup and drill downs, you can turn that huge PDF into 2 pages of what you actually need.
Quick dashboards from Google Sheets - Easier to do the graphs than in Google Sheets - Operational dashboards to be used in the day-to-day work - It is good both for retrospective data and to do a pulse check of the current status - Better for not giant amounts of data and not multiple data sources. - If you need a lot of graphs to be displayed on the same page, it can be a bit glitchy during configuration (then the use works fine).
The ability to easily integrate data across multiple data platforms
The product is easy to implement and learn
The elemental design allows for recycling of concepts and features across various reports and output
The security was easy to implement into our existing environment
The number of options available for data manipulation and presentation, including Scheduling and Caching data, makes it easy to solve any problem or create content for any request
Logi's Support Portal staff are absolutely top notch. They are responsive and knowledgeable. Due to the elemental design (see above), it is easy to communicate concepts to and from Logi Support via code samples and/or sample applications. The sample applications which we have received from Logi Support have formed some of the core concepts of our Logi Developer training!
Filtering - you can filter across different dimensions and metrics to get a more specific "cut" of data
Refreshing - data automatically ingests into Looker which allows reports to be updated and backfilled in real time
Conditional Reporting - you can leverage Looker's reporting features to flag when a given metric or KPI falls below or above a specified threshold. For example, if you had a daily sales benchmark in a SAAS organization, you could use Looker to flag whenever daily sales falls above or below the benchmark
Logi Studio is currently only available on Windows. I understand the backend is ASP.net but it would be nice to have more flexibility in this given their software can also be java-based (we run their software on a Linux server using java).
Logi Info keeps all files as XML, which is fine and actually helps in terms of scripting report creation. The issue is that the majority of settings can only live on a server instead of a database. They do allow reports to now live in a database, but other aspects (such as users saving bookmarks and reports) cannot be and are all saved directly on the server.
Looker is less graphical or pictorial which makes it less attractive
Consumes a lot of memory when there are multiple rows and columns, impacts performance too
At times when we download huge chunks of raw data from Looker dashbords, the time taken to prepare the file is enormous - The user fails to understand if Looker has frozen or if the data is getting prepared in the background for downloading. In turn, user ends up triggering multiple downloads
Logi Analytics is a great solution if you need just the user interface. However there are other tools stronger at the overall data flow which include a user interface as part of their product.
We've been very happy with Looker so far, and all teams in the organization are starting to see its value, and use it on a frequent basis. It has quickly become our accessible "source of truth" for all data/metrics.
I am giving 9 rating because the Logi Info still needs to improve on the tutorials part and make it easy for the beginners. Otherwise, it's a very good analytics tool which offers more than 20 types of visualization. It's predictive analysis feature and easy to embed with technologies make it stand out in the market.
Looker is relatively easy to use, even as it is set up. The customers for the front-end only have issues with the initial setup for looker ml creations. Other "looks" are relatively easy to set up, depending on the ETL and the data which is coming into Looker on a regular basis.
The support process is bit slow and has a good scope improvement but overall it's good as team is very supportive. They generally take 1-2 days time to respond emails sent to them but some times a delay is also expected. Overall, I did not face any major issues using the service.
Never had to work with support for issues. Any questions we had, they would respond promptly and clearly. The one-time setup was easy, by reading documentation. If the feature is not supported, they will add a feature request. In this case, LDAP support was requested over OKTA. They are looking into it.
It can be embedded on top of a website for direct analysis. I feel this is a way faster and a better solution. This is like an integrated solution. That's why the firm selected Logi Analytics for quick insights on customer behavior and data.
Looker is an off-the-shelf, free tool for Google business users. Other than the internal cost of time to build, we had no costs to set up what we needed to do. Knowledge sharing internally and using templates greatly reduced this cost, making the overall cost very low.
Our Chief Operations Officer has commented several times about how important LOGI has been in identifying opportunities for us to work on, and key areas to focus on to improve revenue generation
We have used LOGI to automate work processes that used to be paper-based.
We've filled in holes in work processes, and freed up work hours allowing people to focus on more important daily tasks.
Allowing others to self-serve their own analytics and connect it to Looker simply and easily has helped unblock the central data team so they can instead focus on validated dashboards whilst stakeholders manage their day-to-day analysis themselves. Countless engineering hours have been freed up by not having to manage every user permission for each BI tool; we have a BYOBI approach; Bring Your Own BI
Creation and management of a semantic layer (LookML =Looker Modeling Language ) allows peoples sandboxes and production databases to become clutter free. Minor adjustments, conditional fields, and even some modelling can all be done in LookML which doesn't need oversight or governance from the central data team.
LookML, specifying drilldown fields and their sub-queries, as well as generally creating dynamic parameters with Liquid are all great features, but can have a steep learning curve. it may take some time to understand how to create this middle layer correctly, or even pose a risk of inheriting complex code from another source which can be unmaintainable if it becomes too big. Some level of governance is recommended if Looker is used by a large number of editors.
