Marko here from Codaxy. For over two years, we have been working on CxReports, a low-code tool for creating user-facing PDF documents and reports.<p>We first saw the problem in wealth management, where reports are crucial for the user experience. Software vendors have customers who ask for customized reports with unique content, branding, and visuals. The solution was to build a tool that allows customization for each customer, which even customers themselves can use. Over time, this evolved to be a generic solution that works for various other use cases.<p>CxReports lets you build reports visually. You can connect to a database and get data using SQL queries. It supports scheduled report generation and delivery. The API enables accessing CxReports from other applications or workflows.<p><a href="https://cx-reports.com/" rel="nofollow">https://cx-reports.com/</a><p>You can easily try it out with our Docker image -
<a href="https://docs.cx-reports.com/getting-started/docker/" rel="nofollow">https://docs.cx-reports.com/getting-started/docker/</a>.<p>We offer a free tier for registered users.<p>How do you currently handle customized reporting? Are there specific challenges you face with generating user-facing reports? I’d love to hear your thoughts and feedback.<p>Looking forward to the discussion!
We’ve been struggling with custom PDF reports for a while—either hardcoding templates or juggling serverless functions and libraries. It’s a real pain when clients want tweaks and we have to redeploy.
The visual editing aspect of CxReports looks intriguing. If I can give non-technical team members control over layouts and styling that'd be great.
How flexible is the design tool? Can it handle complex data visualizations like nested tables, charts, or custom fonts easily?
My team is currently running with jsreports for about a year or so now. The biggest problem that we are having right now is the absurd amount of dev time that we need to allocate in order to produce anything meaningful. I wonder what's the least amount of technical literacy needed to produce a report? From the text I assume that the goal is to have wider selection of people who can work with the tool.