[RadiozRadioz]

Looks nice, well done.

Though I worry about the narrowness and "whip-up-ability" for the price and target market. It's a small enough featureset in a domain that skews technical, many would be inclined to template an HTML table to wkhtml2pdf and call it a day. Maybe they'd open source it after. I suppose you're aiming for the people who wouldn't do that, but would still expend the effort of integrating with an external HTTP API (and paying monthly for it)

I know a measure of a project's usefulness is "if a HN commenter says they could make it in a weekend but haven't, you've got something!", so maybe I'm wrong.

P.s. 50 pages / 1Mb per PDF is ludicrously far too small for a business tier.

[patafemma]

Thanks for the feedback! You're right, many technical users could likely roll their own solution, and for one-off projects, that's a valid approach. However, after working on this for a while, I've found that building a more generic and flexible solution is definitely not a simple task. The goal with SnazzyPDF is to hide the more complicated bits like the layout and consistent formatting of deeply nested JSON, without the need for maintenance. It's aimed for the people who value saving time over building from scratch. I know, maybe it's not really for the most hacker-minded.

Regarding the page/file size limits, that's helpful input. I have set the current limits based on my own experience but haven't had much opportunity to validate them yet. I’ll definitely take another look and try to find a good balance.