Word stays the editor
Business teams design documents in Word. Developers only send data.

Write the document in Word. Put tags where the data goes: <<client.name>>, a table row repeated per line, a section shown only for some customers.
Add it to the DocIbis library. The console checks the template, keeps its versions and publishes the one your applications use.
Send the data, get the PDF. Your application sends JSON to DocIbis and receives the finished document, usually in a fraction of a second.
curl -H "Authorization: Bearer $DOCIBIS_API_KEY" \ -F templateName=exemples/03-facture.docx \ -F data=@invoice.json \ -o invoice.pdf https://docs.example.com/v1/render
Word stays the editor
Business teams design documents in Word. Developers only send data.
Docmosis-compatible
Same tag syntax and a compatible /api/render call: existing templates and clients keep working.
Self-hosted
One command installs it with Docker on your server. Documents and data stay with you.
Safe publishing
Versions, checks at import, comparison with reference PDFs, scheduled publication and rollback.
Install
One command on a Linux server, then first steps.
Write a template
The tags for fields, tables, conditions, images and QR codes.
Call the API
Produce documents from any language, or move a Docmosis client.
Run it