Document Assembly · API-first · Swiss-hosted

Turn templates and data into finished documents.

XGenerate is a programmable document-assembly engine. Bring your DOCX, HTML or Markdown templates, POST your data, and stream back perfectly rendered PDFs, Word files or HTML — at any scale, on every channel. The generation half of the DocFlow + XGenerate stack, sold standalone or bundled.

The engine

Assembly, not generation by guesswork.

Most document-generation stories today reach for a chat model and hope. XGenerate doesn't. It's a deterministic assembly engine — same template, same data, same output. Auditable, testable, version-controllable. The kind of pipeline you can put a regulator's name on.

Template-first authoring

Bring the templates your team already maintains — Word, HTML, Markdown — with merge fields declared inline or in per-template binding sidecars. No proprietary editor, no DSL to learn.

Deterministic, auditable output

Same template plus same data plus same options equals byte-identical output, every time. No model hallucinations. Every render is reproducible, version-controllable and explainable to a regulator.

API-native, embed anywhere

Every operation is a clean, OpenAPI-documented REST endpoint. Drop XGenerate behind your CRM, ERP, or internal portal — it is a service your developers integrate, not a product your users have to learn.

Format-agnostic output

Render to PDF, DOCX, or HTML from a single source template. Pick the output format per request — same merge fields, different channel.

Swiss-hosted, jurisdiction-clean

Hosted in Swiss data centres on Swiss-owned infrastructure. No US parent in the chain — out of reach of US subpoenas and the CLOUD Act. FINMA-compatible, DSG and GDPR-aligned.

Swiss Made Software — certified Swiss software

Swiss Made Software

Certified Swiss software — developed and hosted in Switzerland.

How it works

Template plus data in, rendered document out — in three steps.

  1. Step 1

    Author your template

    Drop in a Word, HTML or Markdown file. Mark merge fields with simple placeholders or per-template binding sidecars. Your template lives in version control alongside the rest of your code.

  2. Step 2

    POST your data

    Send a structured payload (JSON / XML) to the render endpoint and pick PDF, DOCX or HTML as the output. XGenerate resolves bindings, applies layout, and returns the finished document.

  3. Step 3

    Archive, deliver, automate

    Stream the file back to the user, push it to S3, or hand it to DocFlow — every rendered document gets archived as a versioned, retrievable asset with no glue code required.

Integrations

Built to slot in — not to be the centre of your stack.

XGenerate is a service, not a destination. Every operation is a clean, OpenAPI-documented REST call, authentication federates to your identity provider, and DocFlow waits as a sibling product whenever you also need archiving and retrieval.

DocFlow — the natural pairing

Render with XGenerate, archive with DocFlow. Every document XGenerate produces lands in DocFlow as a tenant-scoped, versioned asset, automatically. Buy them together for a single Swiss-hosted assembly + archive stack — or run XGenerate standalone and bring your own storage.

REST + OpenAPI, end to end

Every endpoint documented, every payload typed. Generate clients in minutes, integrate from any backend, automate from curl. Built for the developer in your team who would rather read a spec than book a call.

S3-compatible object storage

Direct deposit of rendered documents into the bucket of your choice. Skip the round-trip if you do not need archiving — XGenerate writes the file and hands you back the key.

OIDC identity federation

Any OIDC identity provider can front XGenerate, with JIT user provisioning. No parallel user directory, role-based access scoped per tenant.

XGenerate + DocFlow — assembly and archive as a single, Swiss-hosted stack. Run XGenerate standalone, or bundle it with DocFlow and let every rendered document land in your archive automatically.

Why XGenerate

An assembly engine for teams that need provable, repeatable output.

Document generation today is full of demos that look great until somebody asks how exactly the file was produced. XGenerate is built the other way around: every render is deterministic, every binding is explicit, and every output is reproducible from the same inputs months later.

Multi-tenant from day one, with OIDC authentication and role-based access. Encrypted in transit (TLS) and Swiss-hosted — with nothing encrypted at rest, because nothing is kept at rest: XGenerate has no database and no object storage. Templates and data live in memory for the life of the request and no longer. There is no render archive to breach, subpoena or back up; when you need retention, keys and an audit trail, that is DocFlow's side of the stack.

Built in Switzerland for organisations that have to explain to a regulator how a document was produced — not invent the answer afterwards. Financial services under FINMA, Swiss and EU public sector, and regulated enterprise across the DACH region. And when you also need an archive, DocFlow bolts on as a sibling product — XGenerate renders, DocFlow keeps the canonical copy.

FAQ

Frequently asked questions about XGenerate

What is XGenerate?

XGenerate is a REST API for document generation: you send JSON data and a Word template, and XGenerate produces finished PDF, DOCX or HTML documents — deterministic, layout-faithful and hosted in Switzerland.

Can XGenerate create Swiss QR-bills?

Yes. XGenerate generates standards-compliant Swiss QR-bills with the QR code straight from your data — as PDF or DOCX, ready for dispatch and archiving.

Does XGenerate replace classic mail merge?

Yes. Mail merge and bulk generation run through the same API: one Word template with placeholders, any number of records — and one finished document per record. Generate PDF, DOCX or both.

Where does XGenerate run, and what happens to my data?

XGenerate runs in Swiss data centres, operated by Stratech GmbH, based in Appenzell. The service is stateless: templates and data are processed, never stored — nothing remains after generation.

How do I integrate XGenerate?

Through a lean REST API: send a Word template, post JSON data, receive the finished document. No proprietary template language — your business teams maintain templates directly in Microsoft Word.

Get in touch

Let's talk about your documents.

Book a working demo against a template you actually use, or just send us a note. We reply personally — usually within one business day.

Email
hello@xgenerate.io
Stratech GmbH
Weissbadstrasse 8b
9050 Appenzell
Switzerland
I'd like to *

By submitting, you agree to our privacy policy.