Robin van der Vleuten

Commented on quario · Nov 3, 2026

Good question. The definition is fully shared; nothing in it is per format. What differs is what each target does with a declaration, and that's explicit: every declaration is resolved, approximated or withdrawn per target. For example, column widths are exact in the PDF, but in the workbook the content sizes the column. Spacing and padding exist in PDF and Word, not in a grid. A group break is a new page in the PDF and a new worksheet in Excel. So the promise is the same structure and data, not the same pixels. plan() lists every approximation before you render, and marking a declaration required makes validation fail rather than quietly drop it. Full table: https://getquario.com/docs/reference/support-matrix

Commented on quario · Oct 27, 2026

Thanks Aditya, good question. Honest answer: it's early, so I can't point at a customer list yet. These are the two situations I built it for: 1. Replacing an existing setup. Usually a hand-maintained pdfmake or PDFKit script, or an HTML template pushed through Puppeteer, where every new report means more drawing code and a headless Chrome to run. The definition takes over the layout, and the same file also gives you the Excel and Word export that's usually a separate script. 2. Building reports for the first time, with an agent drafting them. That's where a JSON definition matters most: the model writes data, quario validates it and points at the exact path that's wrong, and nothing the model writes can execute. If you're in either camp, I'd love to hear which one. And thanks for the search check, that's fair. The site is a few months old, so I'm not expecting page 1 for the broad query yet. I've been writing comparison pages for the specific libraries people search for instead (pdfmake, PDFKit, Puppeteer, React-PDF, Gotenberg and a few more), which seemed a more realistic way in than the head term.

Commented on quario · Oct 14, 2026

Hi DevHunt 👋 I'm Robin, and I build quario on my own from the Netherlands. I kept seeing two ways teams generate invoices and reports: hand-written PDF drawing code, or HTML pushed through headless Chrome. Neither works well once an LLM writes the report. You either run code the model wrote, or let it type numbers. quario makes the report data instead: a JSON definition the model drafts, the engine validates, and your own data fills. The same definition renders to a page, a PDF, an Excel workbook and a Word document. The homepage shows a real agent loop, with two mistakes caught and fixed before anything renders. Happy to answer anything, especially "why not just use pdfmake/Puppeteer?"