I m building Open Reports around one integration boundary: the host application owns report JSON, authentication, business data, and when users can print; Open Reports edits the definition and renders the output. The host can send a definition and JSON data to the render API, or embed the designer and save edits back to its own store. I ve tested the embedded workflow in a second-origin Chromium host. Other browsers and restrictive production CSP setups still need validation. This is early v0.x, not a drop-in JasperReports or Crystal Reports replacement; JRXML import is partial and compiled .jasper files are not supported. If you build software that embeds reports, where would this model break for you? What would you need to see before trying it with one synthetic invoice or statement? Demo: https://open-reports-demo.onrend... Code and integration guides: https://github.com/varaprasadred... 10-minute workflow: https://youtu.be/MtQdFujBUV0
An MIT-licensed, self-hosted report designer and rendering engine. Design invoices, receipts, statements, and labels in the browser; render to PDF, DOCX, HTML, XLSX, CSV, ZPL, or ESC/POS. Embed the designer or send report JSON and data to the API. Early v0.x: not a drop-in JasperReports or Crystal Reports replacement; JRXML imports are partial drafts that need review.