Define once. Deliver anywhere. Own it completely.

Sovereign forms.

Datum is forms infrastructure you run in your own environment. Define a form once, deliver it as a web form, a PDF or a printed page, and own it completely.

By the numbers

A thousand forms.
One file each.

Try the builder →

Most organizations do not have a form problem. They have form sprawl: the same form as a PDF, a web page and a printout, each kept its own way.

Overview

One form, every output,
nothing taken on trust.

All capabilities →

Try it

Build a form.
Watch it render.

The snippet →

The builder and the form below are the real elements, loaded from the same files you would host. Add a field, change a label, write a rule, and the form under the builder follows. Press Try it to use the form on the canvas, read every rule as a sentence in Logic, see where each answer is saved in Data, and find the journeys and PDF layouts in their own workspaces; Ctrl+K finds any command. Switch its theme, fill it in, send it, print it, preview the PDF, and read the data and the schema as JSON. Example 6 asks one form two ways: a journey a page at a time, and one with every question on a single page. Switch between them with View; either one fills the same form. To start from a fillable PDF of your own, open the builder's PDF workspace, press + New layout, then Load a PDF, and press Create form fields. Nothing leaves this page.

The live demo loads the bundles this site is built beside, and they are not here. The docs have the snippet and the files to host.

One definition

A form in the browser.
A contract on your server.

Server hosts →

A Datum form is one JSON document: fields, rules, translations and the PDF layout. The browser renders it. Your server holds the same document and accepts only what it describes, so the form is also the contract for every record that reaches you: from the rendered form, from a PDF filled elsewhere and imported, or from any client that sends the JSON.

One definition · two sides intake-v3.json
intake-v3.json Fields · rules · validation · translations · PDF layout
In the browser<datum-form> on any page

The rendered form

  • View and fill it on any page, in your theme, in the person's language.
  • Rules run as they type; a draft saves as they go.
  • Print it: the read-only rendition, through the browser's own dialog.
  • Generate the PDF from the designed layout, or fill an existing PDF, in the page.
  • Sign the PDF with a certificate of their own: a file, or a YubiKey.
  • Sign the submission with a passkey or security key.
  • Submit it to your server, or download the JSON or the PDF and send it by email.
  • To the server: record.json · signed
  • Back: receipt · JSON
  • Back: PDF · server-signed
On your serverany host that runs WASM

The API contract

  • Accept the record at POST /api/submissions: the fields the definition names, nothing else.
  • Validate it in the WASM sandbox: same rules, same verdict, byte for byte.
  • Verify the submission's signature, and every signature on a PDF, check by check.
  • Generate the PDF, PDF/A with the record inside, and sign it with the server's certificate, so the signature covers the record too.
  • Keep the record and answer with the receipt and the signed PDF.
  • Inspect any JSON or PDF without storing it.

From the browser alone a printed page · a PDF · a JSON record

Also into the server JSON from any client

Runs where you run
Browser Node.js Java .NET Python Air-gapped

The browser alone is enough. The builder, the renderer, the validation sandbox, PDF generation and the signature tooling all run in the page, so a team can build a complete form with no server, and a person can fill it in, download the signed PDF and send it by email. When submissions should be kept in one place, any host that runs WASM can be the server. Nothing is fetched from a third party, so all of it runs air-gapped.

Pricing

Free to run.
Support when you want it.

The docs →
Start with yours

Bring one form.
See it run.

Take one form you run today, a fillable PDF will do, and build it in the demo above: nothing leaves the page. When it is ready to run, the builder, the renderer, the sandbox, the PDF kernel, the signing agent and the server hosts are in one repository, to host wherever you need them.