ReportShell™ vs JasperReports® Server

A detailed comparison.

JasperReports® Server is a full reporting platform. It runs as a standalone service with its own repository, user management, scheduling, portal UI and ad-hoc report designer. Users log in to it, browse reports, and run them.

ReportShell™ is an embedded framework. You integrate it directly into your Spring Boot application, so your own app serves reports with your own UI, your own security, your own data sources, and your own URL structure.

JasperReports® and Jaspersoft® are trademarks or registered trademarks of Cloud Software Group, Inc. and/or its subsidiaries. ReportShell is not affiliated with, endorsed by, sponsored by, or otherwise associated with the owners of the JasperReports® or Jaspersoft® marks. Statements about JasperReports® Server reflect our understanding of its publicly available documentation and are offered for comparison only.

When ReportShell is a good choice

  • You want reporting inside your own Spring Boot app as a lightweight feature,
  • You don't need built-in scheduling, ad-hoc design, compilation and repository management of resources such as reports, data sources, queries, input controls etc.
  • Your primary goal is to let users view and export precompiled reports without advanced reporting server features.

Side-by-side

Aspect JasperReports® Server ReportShell
Deployment model Standalone server you deploy and operate Spring Boot dependency embedded in your app
Report storage Built-in server repository Your filesystem, classpath, or a custom report store you implement
User management Built-in, with roles and organizations. Integrates with external identity providers via LDAP, SSO, etc. Your app's existing user model
Authentication & authorization Built-in, pluggable Your Spring Security setup, with per-report access control via a pluggable authorization service
Data sources First-class persistent resources managed in the server, plus pluggable services for custom sources Pluggable services you implement, with conventions that resolve Spring JDBC data sources automatically
Input controls First-class managed resources defined in the server, plus any defined in JRXML Parsed from JRXML out of the box. The metadata resolution layer is pluggable, so you can implement a managed-resource model if you need one.
REST APIs for viewer functionality Yes Yes. ReportShell intentionally mimics parts of the JasperReports® Server REST surface to ease integration for developers familiar with it, with a smaller, focused API tailored to embedded viewer use cases.
Report design & compilation Design reports in the server UI or Jaspersoft® Studio; the server supports compilation Expects precompiled .jasper files. Design in Jaspersoft® Studio and ship the compiled output with your app.
Viewer UI Built-in portal Your app's pages, a ready-to-use React viewer, or your own custom viewer
Ad-hoc report design Yes, via the Ad Hoc Editor No. Reports are designed in Jaspersoft® Studio and shipped with your app
Interactive Reports Supports interactive HTML features including hyperlinks, drill-down and interactive charts Renders static HTML with static charts by default. Interactive behaviors can be added through custom exporters or exporter configurations
Scheduling & distribution Yes Not built-in. Use your app's existing job scheduler or integrations

What ReportShell intentionally does not do

ReportShell focuses on being a great embedded viewer and execution layer. It deliberately leaves the following to your application or to other tools:

  • A built-in portal UI for end users to browse and run reports
  • A browser-based ad-hoc report designer
  • A central report repository with folders and permissions
  • User, role and organization management
  • Scheduled report runs and delivery

If you need any of these, JasperReports Server is designed for exactly that job. ReportShell stays focused on embedded reporting so that it can do that job well.

A shorter way to put it

JasperReports Server is a complete reporting platform. ReportShell is an integration layer embeddable as a seamless feature within Spring web applications across any business vertical.

Continue to Stripe

You'll be redirected to Stripe for payment. Before that, please make sure you've carefully read our End-User License Agreement .