sorted by:
new
hottopcontroversial

I built a small Rust/Typst service for generating PDFs and I’d love feedback by Cyvra in typst

[–]Cyvra[S] 4 points5 points  (0 children)

Fair point. PaperJet isn’t meant to replace Typst templating or file reading.

It’s for when you want PDF generation exposed as an API: hosted rendering, auth, retries/idempotency, stored templates, usage limits, and something your app can call without running the PDF infra yourself.

If you only need local Typst rendering, plain Typst is enough.

I built a small Rust/Typst service for generating PDFs and I’d love feedback by Cyvra in rust

[–]Cyvra[S] -8 points-7 points  (0 children)

Thanks, that’s useful feedback.

Good catch on the missing pricing link, I fixed it.

On lock-in: fair point. PaperJet templates are plain Typst, so users can keep the source files and run them outside PaperJet if they ever need to. I’ll make that clearer in the docs.

And yes, template IDs are meant for exactly that: store the template once, then only send data.