What do you like best about Jaspersoft?
Tenant-based architecture and reporting Multi-tenancy is a first-class citizen — not bolted on. Each organization gets its own isolated context, permissions, and report repository. Managing a large client base without report bleed-across between organizations would be significantly harder without this, and it scales well as you add tenants.
Intuitive organization and user management
Creating organizations, assigning roles, and controlling what each tenant can see or do is straightforward from both the UI and the API. Role mapping can be driven directly from SSO claims, which means less manual provisioning overhead as your user base grows.
Deep SSO and identity integration
The external auth extensibility is genuinely powerful. We run both an OIDC/OAuth 2.0 flow for interactive logins and a pre-authentication token flow for embedded/programmatic access — simultaneously, on the same server. That flexibility is rare in reporting platforms.
Highly configurable without forking core code
The customization surface is large and well-structured. We layer in Spring XML overrides, custom JARs, and JSP-level changes — all without touching upstream code. Most platforms force you to choose between upgrading and customizing. Jaspersoft lets you do both.
Fits naturally into existing infrastructure
Jaspersoft doesn't fight your deployment model. Installation integrates cleanly with cloud-native patterns (S3 for artifacts, IAM for credentials, infrastructure-as-code for provisioning). For teams already running on AWS, the operational overhead is low. Review collected by and hosted on G2.com.
What do you dislike about Jaspersoft?
High administrative complexity
Jaspersoft is not self-service friendly for application developers. Configuration lives across dozens of Spring XML files, properties files, and deployment descriptors — making it difficult to onboard engineers who aren't already familiar with the platform's internals.
Steep learning curve across the board
Both end users and administrators face a significant ramp-up period. The concepts around domains, topics, Ad Hoc views, and the repository hierarchy aren't intuitive out of the box, and the documentation doesn't always bridge that gap effectively.
Dated UI
The interface is functional but feels behind modern standards. For a reporting product where end users spend a lot of time, the UX doesn't inspire confidence and can be a friction point when onboarding less technical users.
Slow engineering turnaround
When bugs are escalated to the vendor, resolution timelines tend to run longer than we'd expect compared to other tools in this space. For a platform this configurable, a faster feedback loop with engineering would go a long way.
Unexplained behavior and edge-case bugs
There are occasional gremlins — behaviors that are difficult to reproduce consistently or trace to a root cause. Some quirks feel like longstanding issues that have never been fully resolved, which adds unpredictability to an otherwise stable platform.
No meaningful AI functionality
In an era where most analytics and reporting tools are integrating AI-assisted insights, natural language querying, or smart report generation, Jaspersoft lags noticeably behind. For teams looking to leverage AI in their reporting workflows, this is a meaningful gap. Review collected by and hosted on G2.com.