Roadmap

From Spring Boot reporting library to enterprise reporting platform.

Report Boot is being built in phases: first as a clean embedded reporting library for Spring Boot, then as a provider-neutral framework for SQL exports, secure report lifecycle, enterprise controls, visual template design, and platform-level governance.

Roadmap shape

01Available now
02Contracts available
03Enterprise runtime
04Platform roadmap
05Designer + AI
Roadmap philosophy

Built in practical layers.

Report Boot is not trying to become a platform before the library is solid. The roadmap starts with the repeated pain backend teams face today: generating, securing, and maintaining reports inside Spring Boot applications.

available library capabilities

reviewed annotation contracts

provider-neutral report engines

SQL and Excel intelligence

secure lifecycle and tenant safety

performance and operations

platform capabilities when teams are ready

Available now

01 / Core Reporting Foundation

Build reports inside Spring Boot without rebuilding the pipeline.

Report Boot already provides the foundation needed to generate, secure, store, and download reports through one Spring Boot reporting pipeline.

  • Annotation-first report generation
  • Core ReportService API
  • Provider-neutral renderer architecture
  • Spring Boot auto-configuration
  • Report template resolution
  • Report order lifecycle
  • Secure UUID downloads
  • Expiry handling
  • In-memory report storage
  • Root-cause-first error handling
  • YAML-based defaults and overrides
  • Per-library docs and Postman examples
Available now

02 / Annotation And Metadata Model

Make report behavior visible in code review.

Report Boot gives reports a reviewed, code-first contract through annotations and metadata instead of hidden controller and template behavior.

  • Template annotations
  • Engine selection annotations
  • Output selection
  • Field mapping
  • Table mapping
  • Request parameters
  • Required field validation
  • File naming
  • Formatting metadata
  • Currency, locale, and date formatting metadata
  • Security metadata
  • Access role metadata
  • Sensitive field metadata
  • Retention and checksum metadata
  • Engine property metadata
  • Preview metadata
Available now

03 / Supported Report Engines

Use the right engine without changing the reporting pattern.

Report Boot supports multiple report engines through the same service contract, so teams can choose by report type instead of rebuilding integration code.

  • JasperReports for PDF
  • JXLS for designed Excel templates
  • BIRT for PDF
  • Thymeleaf for HTML and print-ready HTML
  • Dynamic Excel for template-free XLSX
  • Dynamic CSV for CSV and ZIP exports
Available now

04 / SQL Dynamic Reporting

Export trusted SQL without hand-built controllers.

Report Boot supports SQL-driven reports without requiring large DTOs or custom export endpoints for every query.

  • SQL Dynamic Excel
  • SQL Dynamic CSV
  • Direct SqlReportDefinition API
  • Catalog-based SQL report registry
  • Multi-sheet SQL reports
  • Parallel sheet loading
  • Named SQL worker threads
  • Tenant-aware SQL parameters
  • JWT-based tenant detection
  • Named parameter binding
  • SQL safety validation
  • Query timeout, fetch size, and max row controls
  • Streaming SQL result handling
Available now

05 / Excel Intelligence

Generate business-ready workbooks from data definitions.

Report Boot can generate useful Excel reports without requiring a pre-designed template or hand-written Apache POI workbook logic.

  • Template-free XLSX generation
  • Multi-sheet workbooks
  • Formula columns
  • Formula references by column name
  • Excel function passthrough
  • Formula validation
  • Summary footers
  • Conditional formatting
  • Header and column styling
  • Font, size, bold, italic, alignment, and format controls
  • Freeze headers
  • Auto filters
  • Metadata sheets
  • SXSSF streaming for large workbooks
  • Row limits, overflow policy, and auto-size controls
Available now

06 / Security And Tenant Safety

Treat generated reports as secured artifacts.

Report access, expiry, user context, and tenant protection are handled consistently instead of being rewritten per endpoint.

  • UUID-based report access
  • Expiry enforcement
  • Requested-by tracking
  • Anonymous fallback
  • Role access check with @ReportAccess
  • Tenant-aware SQL reports
  • Tenant value from request parameters
  • Tenant value from JWT claims
  • Checksum creation
  • Sensitive field metadata
  • Root-cause-safe error logging
Available now

07 / Performance And Large Data

Tune large reports before they become production incidents.

Large exports need predictable memory and runtime behavior. Report Boot exposes tuning points instead of hiding performance problems in custom code.

  • Jasper startup precompilation
  • BIRT startup precompilation
  • Java 21 virtual threads where available
  • Platform-thread fallback
  • Parallel SQL sheet generation
  • JDBC fetch-size tuning
  • Query timeout controls
  • Max row enforcement
  • SXSSF Excel streaming
  • Excel window-size configuration
  • Compressed Excel temp files
  • Large demo dataset testing
Available now

08 / Developer Experience And Documentation

Evaluate, run, and copy working patterns quickly.

Report Boot is documented as a library, not only as source code, so developers can test endpoints and understand provider behavior quickly.

  • Organized documentation structure
  • Per-library README files
  • Per-library Postman Markdown files
  • Full Postman collection guide
  • Provider documentation
  • SQL reporting docs
  • Dynamic Excel docs
  • Configuration properties documentation
  • Demo controllers and examples
  • Website-ready technical content
Contracts available

09 / Enterprise Annotation Contracts

Express governance direction in reviewed code.

Report Boot already defines enterprise metadata annotations that prepare reports for future governance behavior while runtime engines are added over time.

  • Audit annotation contract
  • Storage and archive annotation contracts
  • Retention metadata
  • Checksum metadata
  • Schedule annotation contract
  • Email annotation contract
  • Async annotation contract
  • Webhook annotation contract
  • Datasource annotation contract
  • Cache and metrics annotation contracts
  • Tenant field annotation contract
  • Watermark metadata contract
  • Policy metadata contract
Planned

10 / Enterprise Runtime Roadmap

Turn metadata contracts into runtime capabilities.

Teams can start with the embedded library now and grow toward governed enterprise reporting without changing the core reporting model.

  • Scheduler engine
  • Scheduled report emails
  • Audit log persistence
  • Storage adapters
  • S3 and MinIO support
  • Database archive storage
  • Webhook delivery
  • Async queue execution
  • Metrics collection
  • Advanced watermark rendering
  • Role and permission policy enforcement
  • Export policy enforcement
  • Report ownership and catalog metadata
Planned

11 / Microservice And Platform Roadmap

Standardize reporting across services.

Report Boot is designed to grow from embedded library mode into shared reporting infrastructure for platform teams.

  • Dedicated reporting service mode
  • Central report API
  • Report catalog API
  • Report routing by code, domain, tenant, provider, and output
  • Cross-service report registration patterns
  • API gateway integration guidance
  • Request metadata propagation
  • JWT and tenant propagation patterns
  • Report lifecycle events
  • Kafka or messaging integration
  • Operational monitoring patterns
Exploration

12 / Visual Designer And AI Roadmap

Make report authoring faster and easier to standardize.

Report Boot is exploring tooling that helps developers and business users create reports while keeping the framework contract predictable.

  • Visual JXLS Excel Designer
  • Excel-like design canvas
  • Drag-and-drop report components
  • Automatic JXLS note/comment generation
  • Template metadata JSON
  • Template validation
  • Reopen and edit designed templates
  • AI-friendly documentation
  • Prompt-ready examples
  • AI-generated report definitions
  • AI-generated SQL Dynamic Excel reports
  • Guardrails so AI builds on Report Boot instead of generating one-off export code
What will stay true

The principles will not change.

The platform can grow, but the contract should remain boring in the best possible way: Spring Boot first, code-reviewable, secure, tenant-aware, and understandable by developers.

Spring Boot first
Developer-friendly API
Provider-neutral architecture
Secure report lifecycle
Tenant-aware enterprise design
Local-first and code-reviewable
Performance-conscious for large data
Documentation-first adoption
AI-friendly examples and predictable contracts
Help shape Report Boot

Built from real backend reporting pain.

If your team struggles with repeated export code, SQL reporting, tenant-safe downloads, report governance, or enterprise reporting workflows, the roadmap is open to real-world feedback.

embedded today
SQL exports
observable tomorrow
platform-ready