# Marcus Delgado, Senior Backend Engineer at Veridem Financial — read of typst-batch-rendering-service, June 18 2026

> Nine years backend, last four at a Series B fintech that generates roughly 2 million PDFs a year: client statements, tax docs, loan agreements, compliance certificates. Currently holding together a WeasyPrint pipeline with prayer and cron jobs.

## How I got here

Googled "weasyprint performance bottleneck batch rendering" on my lunch break because our statement job is now taking 40 minutes to run and someone in product wants us to cut that to under 5. Second result was a Reddit thread from 2024 that mentioned Typst. Clicked around, eventually landed here from a Typst community forum post. No ad, no newsletter, no LinkedIn. Pure desperation search.

## What I clicked first

"Batches of 100 PDFs in under 5 seconds." That's the only line on the whole page with an actual number in it that means something to me operationally. Everything else in the hero is vibes. "Generate hundreds of beautiful technical PDFs per second" sounds like someone asked a language model to write marketing copy. But 100 PDFs, 5 seconds, that's a benchmark I can put next to our current numbers and check.

I also noticed "No servers to manage" which, fair, that's the pitch for basically every managed API ever, but it's not wrong.

## Where I paused

The "Zero Lock-In" section. "Export templates as plain Typst files anytime. Run them locally with the open source compiler. Never trapped with our service." I stopped here because this is the thing I actually care about and almost nobody says it explicitly. Our current vendor has us in a proprietary template format that took 6 months to build out. Getting out would be a rewrite. So either this is a genuine architectural decision or it's marketing language that technically means something much narrower than I'm reading. I wanted a link to docs or a walkthrough that showed me what the export actually looks like.

## What I distrusted

Two things.

First: "SOC 2 Type II certified." No audit report link, no certification date, no auditor name. Every SaaS startup either claims SOC 2 or says it's "in progress." I've seen this on pages that were plainly not certified. It's one sentence with zero evidence attached.

Second, and this one is more interesting: I scrolled to the bottom and found this section -- "Honest disclosure: we don't have live customers on this idea yet. We shipped the strategy package; you ship the customer conversations." Then, one line later: "1 in 10 Meaningful-success odds (Fermi)."

So this isn't a product. It's a pitch deck someone turned into a landing page. The whole "Wishdeal Factory" thing, the 68/100 adoptability score, the "Adopt for $99" pricing -- this is a business idea marketplace, not a shipping API. The template page above the fold is a concept document. There's no API. There are no 50 templates. There may be no compiler running anywhere.

That's not necessarily a dealbreaker for what this page is trying to do, but for someone who landed here because they have a real production problem, finding that out in the footer is a bad experience.

## What would convince me

If this were a real product, I'd want a working sandbox. Not "render your first PDF in under 10 minutes" as a claim. A live demo where I paste JSON and get a PDF back in the browser, no account required. That's it. That single thing would tell me the infrastructure exists and the performance claim is real.

On the SOC 2 point: link to the Vanta or Drata page. Those are publicly shareable now. One click.

On templates: show me three of the 50. Let me see what "invoice template" actually looks like in Typst syntax versus rendered output. The words "50+ pre-built templates" are doing a lot of work without any evidence behind them.

## What I'd ask in an email reply

1. The page says "Batches of 100 PDFs in under 5 seconds." Is that p50, p95, or p99 latency? Our use case is 15,000 PDFs in a single overnight job, not 100 in a burst. What does that job look like on your infrastructure?

2. The "self-hosted option available" line under Enterprise -- what does that actually mean? A Docker image I run? A Helm chart? Guidance on running the Typst compiler myself, which I could already do? Because if I'm going to manage infrastructure anyway, the managed service value prop disappears.

3. What happens when a template compile fails at 8,000 of 15,000? Do I get a partial result with error details per document, or does the whole batch fail? Failure modes are never in the marketing copy and they're always what matters.

## Verdict: on-the-fence

If this were a real, shipped API I'd be emailing them today, because the problem description is accurate and the Typst lock-in angle is genuinely differentiated. But the footer reveals this is a business idea, not a product. I'm not on the fence about the idea, I'm on the fence about whether to check back in six months if someone actually builds it.

---
*Memo by skeptic persona, generated 2026-06-18T13:42Z. Studio breaks own self-grading loop.*