Unreleased documentation. These pages follow the main branch and can change before the next release. For supported guidance, use v0.46.0.
If your registry hands people printed letters, receipts, or certificates, Registry Render turns record data into those PDFs, and the same inputs always give the same bytes.
What a caller gets
Section titled “What a caller gets”A caller sends the document’s data and its issuance time, and receives the PDF with two hashes: one for the file, one for the exact input it was rendered from. Store both with the record. A re-render from the same inputs months later is byte for byte the same file, so a hash in an audit log still matches the paper in the folder, and a retry never yields a different document.
What you define
Section titled “What you define”You write a bundle: plain Typst templates, a JSON Schema for each document’s data, label tables
for each language, and the fonts the templates use. registry-render check checks it offline,
and registry-render package turns it into a package whose digest names its exact files.
What runs
Section titled “What runs”registry-render compile renders one document at a terminal, for authoring and for printing at a
counter without a service. registry-render serve is a small HTTP service that admits callers by
OIDC access token, or by a legacy API key, and renders from one package in supervised worker
processes. For every call it appends an audit entry that carries hashes and versions, never the
document’s data. It keeps no database and makes no outbound call while rendering; a timestamped
seal calls the timestamp authority you configure.
What Render refuses
Section titled “What Render refuses”Render refuses data its schema rejects, a request without an issuance time, a package whose files changed, a caller whose token or API key it does not accept, and a public listening address. A render never reads the host’s clock, fonts, or network; a seal takes its signing time from the host’s clock. How Registry Render works explains each boundary.
When it is not the right product
Section titled “When it is not the right product”Render does not store documents, issue credentials, or decide who may see a field: what a template prints is the template author’s disclosure decision, and paper leaves every access control behind. Records stay in your registry; Render only lays them out. It can add an optional PAdES seal to a document it just rendered, as described in Deploy Registry Render, but it makes no qualified-signature claim.
Where to start
Section titled “Where to start”Render your first document renders one letter offline and over HTTP in about 15 minutes. Deploy Registry Render runs the service for real callers.
Cookies on Registry Stack
We use optional cookies to understand how you use the main Registry Stack website and this documentation. If you contact us, we may link this activity to your enquiry. You can change your choice at any time. Read the privacy policy.
Your browser asks sites not to track you, so optional tracking stays off.
We could not use or save that choice. Optional tracking remains off.