Jaspersoft commercial edition is an embedded business intelligence suite designed to be built-into SaaS products as an integrated reporting engine. It provides reports and dashboards for customer-facing applications without requiring app developers to build their own reporting engine.
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
Jaspersoft
Looker
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Jaspersoft
Looker
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
No setup fee
Required
Additional Details
Jaspersoft offers flexible pricing for ISVs and SaaS per customer or by CPU core.
Very cost-effective and was easy to work with. However as I’ve said before, when your data volumes grow significantly over the years it’s important to plan what your needs will be. Twice in my career, we chose Jaspersoft Enterprise Edition and both times outgrew it in under 6 …
Looker was easier to use, better integration with non-standard datastores, such as Prestodb, and Snowflake, and BigTable. Ease of manageability. Creation of reports faster and easier compared to QlikView. Tableau has better heat maps, however, Looker has better drill down in …
Looker was, hands down, better than any other products we looked at. It was far easier to get started and keep moving because of Looker's internal programming language and data definition language, LookML. We were up and going in just a few days and were creating advanced …
It is well suited for the fact of scalability itself and the breadth of features this application has in order to make the migration from legacy systems to the newer different versions more seamless and effective. Data integrity and security are the main aspects of this tool which does not lose their value when doing day-to-day operations for data mapping.
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).
TIBCO Jaspersoft allows you to embed reports into your own application, which gives users the feeling they are using a single product.
TIBCO Jaspersoft Studio allows for more advanced report development, such as adding subreports, drilldown to detail reports, images, page headers, page footers, maps, and more.
TIBCO's Jaspersoft Domain Designer is very easy to use and navigate.
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
One of the issues we found during our implementation was that the reporting software would work faster for certain data sources and not the others. Extracting CSVs and XML was slower in comparison to JSON in our experience.
Jaspersoft Studio was the main IDE we used for development. Built atop the Eclipse IDE, we found that the tool was really resource intensive and generally take long time to initialize.
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
JasperSoft has been amazing. It is well documented, fast, and transparent in how it functions. We have been very confident in JasperSoft in every aspect of our business and offerings where we've used it. On top of that, their improvements to the product have been fantastic. I am really looking forward to seeing where they take their product and how we can leverage that to please our clients
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 think it's a tool well suited for a software developer. Others with less coding skills could struggle somewhat with the tool. I find java a little unforgiving as a language for expressions and not very user friendly for the technically dis-inclined. Sometimes the numeric conversions cause issues (who knew that 0 and 0.0 would cause different things to happen). Previous experience with a reporting tool that used visual basic for its' expressions that I found much simpler to use. On the other hand, java is so widespread, you can easily google the syntax to accomplish what you need to do.
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.
They have a great customer support ticketing system in which they always respond same-day. They offer conference calls with srcreensharing as well in order to better understand your issues.
I wish that the lower level support access came with more than just 12 cases per year though as this makes us less likely to reach out for questions on things that we then instead try to solve ourselves which results in loss of time in trying to acquire new features and or solve a problem.
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 did the job of getting us to our deadline we set for ourselves for initial launch. The customer we launched the product for was also there to learn about it at the same in order to better understand the capabilities. This helped greatly so that the customer was on the same page on what was possible when using jaspersoft. I think most people would not want their customers aware the product they are using is third-party but in this case it was a new experience for us both and so as we learned more about jaspersoft, we both had better communication on what the future road map was for their business needs in BI.
Resources available in the TIBCO Knowledge Base are covering almost everything. They are well organized, and covering almost every possibility. There is always the change to get back to the TIBCO support or to the dedicated Customer Success Manager whenever something very specific or bound to a customization is not covered.
Having just completed an upgrade to the latest version of Jaspersoft, I am happy to say their support was very good. There were a couple of small challenges which were not easily resolved, but they were primarily related to the fact that we had skipped updates for a couple of versions. The current update procedures assumed we were upgrading from the prior latest version (6.4) to to the new version (7.1).
When looking at the different features of these reporting engines, and what we were going to be using it for, the answer seemed clear. Jasper offered exactly what we were looking for, and did so for a price that we were happy with. For a scalable, feature-rich reporting engine that doesn't break the bank, Jaspersoft is the way to go.
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.
When we demo our Jaspersoft environment to potential clients, their eyes light up and they sit up in their chairs a bit more. A lot of our meetings have ended with with the client very interested in our product due to Jaspersoft.
Our existing clients have been very satisfied with the adhoc features of Jaspersoft. We've been able to provide them better access to their data on their terms instead of ours. Of course this turns into a huge win for us.
We've always used SQL Server Reporting Services to deliver our reports to our clients. Converting to Jaspersoft has allowed us to generate the reporting layer that our clients demand. They no longer feel like they are settling for what we offer.
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.
