In most companies the person who knows what a document should say is not the person who can safely change it. So the wording goes in a ticket, and a developer changes a paragraph.
Document copy changes constantly — a legal footer, a payment term, a new field finance wants on every statement. None of it is engineering work, and all of it becomes engineering work the moment the only editable copy lives in a repository. That is the tax this product exists to remove.
Developers author templates in a code editor with Liquid highlighting, and preview them against real sample data. The preview is a genuine render — the same engine and the same Chromium production uses, not an HTML approximation that diverges once it becomes a PDF.
Visual editing — click an element in the preview, change the text, hide a field, reorder a section — is in build and lands before general availability in October 2026. It is not available today, and we would rather say so here than have you discover it in a trial.
The design constraint is worth stating, because it is what makes visual editing safe rather than merely possible. Edits are applied as targeted patches to the Liquid source through its syntax tree, so everything the editor does not touch stays byte-for-byte identical. Anything the parser cannot map with confidence is locked rather than guessed at. A business user cannot break a template by editing the part they understand.
That is the opposite of a drag-and-drop page builder, which owns the document and hands you its own format back. Here the file stays a normal Liquid file that a developer can read, review and take elsewhere.
Freeform builders were considered and rejected. They store a proprietary JSON model, they fight template syntax like loops and conditionals, and they make the visual tool the source of truth — which means the developer loses the file. Constrained editing on top of a real file is slower to build and worth it.
Accounts are by invitation while we onboard a few teams at a time. Tell us where to reach you and roughly what you render.
Request an invitation on the home page, or write to [email protected].