Everything else in your stack has environments. Templates usually do not — which is why editing one so often means editing the thing production is using, live, and hoping.
A document template is code that customers see. It has logic, loops and conditionals, and getting it wrong sends the wrong number to the wrong person on company letterhead. Yet in most document tools there is exactly one copy of each template, and saving it is deploying it.
Dev, QA and Prod exist from the first day, and Enterprise plans add as many named ones as you want — UAT, Staging, a per-customer beta. A template version is published to an environment, so what production renders is a decision rather than a side effect of somebody saving.
Publishing to several at once is one action, because shipping everywhere is the common case in a small team. Production asks a second time, by name, because that is where the blast radius is.
The preview in the editor goes through the production render path — same engine, same browser, same fonts. It is not an HTML approximation that looks right until the PDF comes out different. That is the whole reason it is worth having: a preview you cannot trust is worse than none, because it moves the surprise later.
Non-production environments have no rate limit. Render a template five hundred times while you get a table alignment right; nothing counts against the quota you pay for and nothing stops you. Output carries a watermark so a test document can never be mistaken for a real one.
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].