A beautifully composed, interactive artefact — authored from your Avira workspace by describing what you want, not by writing code or wrestling a builder. Real typography, real interactions, the weight of a finished product. The operator running the program ships it; the artefact looks like a designer made it. The Google Form is the wrong shape; the PDF is too dead.
Typeform is a form. Notion is a document. A PDF is dead. Neither of the three has the production value of a real artefact — multi-step, deliberately typeset, with interactions that feel composed rather than assembled. The kind of thing the recipient opens and pauses on, because someone clearly cared about it.
We built Folio because every program we run produces artefacts that deserve that level of finish, and every adjacent tool dilutes them into something forgettable. Forms are too thin. Documents are too passive. A CMS is too public. Folio is the missing middle: an artefact that ships at production quality, under your name, with a recipient list and an audit trail behind it.
The operator describes the artefact in writing — three sections, four prompts, this feel, that tone — and your Avira workspace composes an interactive artefact at production quality. No code. No drag-and-drop builder. The result looks like a designer shipped it; revisable, versioned, and consistent with the design language that lives in your install.
Password gates, expiry windows, per-recipient links. The artefact never lives on the open web unless you say so. Each recipient gets a stable URL you can revoke.
Every submission written with IP, user agent, timestamp, recipient identity (if known), and the full response payload. Six months later, “who answered what, when, and from where” is one query.
Optional review queue. Submissions enter pending; an operator approves, holds, or flags before they become part of the canonical record. Useful when you do not want raw input feeding downstream automation.
Submissions exportable as typed JSON for downstream pipelines — CSV for the spreadsheet humans, webhook for the integration humans. Schema is yours; we do not make you parse a free-text blob.
Submissions can land directly in Atelier as evidence packets for downstream AI stages. The audit ledger feeds Observatory. The artefacts compound.
Not Typeform. No logic-tree form builder, no survey-grade analytics. Folio assumes the artefact is the point and the form is one element of it, not the other way around.
Not Notion. No wiki, no collaborative editing, no internal team workspace. The unit is a published artefact, not a working document.
Not a public CMS. Folio artefacts are designed for recipient-shaped publishing — passwords, expiries, per-recipient links. If you want a public website, use a website CMS.
If your work involves publishing a careful artefact and tracking who responded, this is the substrate that does both at once.
