Documents should come out the way you drew them
Crixaa exists because that is surprisingly hard, and because almost every tool that promises it quietly gives up at the last step.
The problem
Most document tooling asks you to describe a layout and hope. You fill in a form, or write markup, or nudge a template in an editor that is only approximately showing you the result. Then you generate the file and find the spacing moved, a font was substituted, and a paragraph you carefully sized now runs onto a second page.
The gap is structural. The thing that draws the preview and the thing that produces the PDF are usually two different engines, with different fonts and different ideas about how text wraps. Any agreement between them is a coincidence you have to keep re-checking.
The approach
We closed that gap rather than papering over it. The editor and the PDF renderer embed the same font families, and the canvas asks the rendering engine what it would compute rather than guessing. When text will overflow, you find out while you are designing, not after you have sent a thousand documents.
That single decision shapes most of the product. The editor does not offer a control the renderer would ignore. Fonts outside the supported set are mapped deliberately instead of being silently swapped at render time. It is less flexible in a few narrow ways, and far more predictable in the ways that matter.
What we build toward
A document tool should be pleasant for the person designing it and boring for the system generating it. So the canvas got real design tooling — vector editing, snapping, layers, multi-page documents — and the API got the opposite: six endpoints, one header, and predictable JSON.
AI sits in the middle as an accelerator, never an authority. It drafts, it suggests, it repairs a broken layout — and every result arrives as a preview you accept or reject. Nothing it produces is applied to your work without you saying so.
How we decide things
Predictable over clever
A feature that works every time beats one that works impressively most of the time. Documents are not a place for surprises.
Show the failure early
Overflowing text, an unverified sending domain, a template with no committed version — better to surface it while someone can still fix it cheaply.
Your data stays yours
Your templates and documents belong to you. We do not train on them, and generated files are served through private, short-lived links.
Honest about what exists
We would rather say a capability is not built yet than imply it is. That applies to our documentation, and to this website.
Try it on a document you already send
That is the honest test — rebuild something real and see whether the PDF matches.