Introduction
Datum is forms infrastructure you run in your own environment: your forms, your data, your keys. A form is designed once, as one JSON document, and rendered on any page. What comes out is the output you choose: a submission validated in a WASM sandbox on your own server, a PDF from a layout you designed or an existing PDF filled in, a printed page, a JSON record, a signature with a certificate or a passkey.
It is a set of packages you host, not a service you subscribe to. Nothing is fetched from a third party at runtime, so an air-gapped deployment works the same as any other.
The words on this site, such as definition, envelope, binding, journey and sandbox, each have one meaning. Concepts says how a form flows from the builder to the page, to your server and into a record, and defines every term in a line with a link to its page. Datum is pre-release: Questions says what that means for the contracts.
The pieces
| Piece | What it is | Where it runs |
|---|---|---|
| The form element | <datum-form>, a web component that renders a definition, validates the answers and raises the submission | Any page, any framework |
| The builder | <datum-form-builder>, the design surface: canvas, inspector, logic, data, journeys, PDF layouts, tests, languages | The browser |
| The definition | One JSON document: components, rules, journeys, layouts, translations, tests | Your repository, your storage |
| The sandbox | A WebAssembly runtime and the sandbox program in it, which validates a submission | Your server, and the page while you develop |
| The PDF program | Draws a layout from the answers or fills an existing PDF, with tagging, PDF/A and signatures | The browser or your server |
| A server host | Endpoints for definitions, submissions, PDFs, timestamps and passkeys, in your framework | Spring Boot, FastAPI; more planned |
Each piece stands on its own. A team can design, test and publish a complete form with the first two alone. The form element is the engine with a face on it: a page that wants the runtime, the rules and the validation without the element can use the engine on its own. A person filling it in can print it, or download a PDF or the answers as a file. When submissions should be kept in one place, signed with a server's key or verified centrally, a server host takes over without changing the form.
How a form flows
A form is designed in the builder, published on a page, filled in, submitted as a canonical envelope, checked again by your server in the sandbox, and kept as a record, with a PDF if you want one. Concepts walks the six steps and names what happens in each.
Where to go next
- Concepts defines every term the site uses.
- Getting started puts a form on a page in two ways.
- Building a form walks the builder's workspaces, and Components lists what a form is made of.
- The definition is the one file a form is, and The form element lists every attribute, property, event and method.
- Server hosts covers the Spring Boot and FastAPI packages, and what any other server needs.