Anyone buying software for regulated processes should know what it stands on. This page names what we built ourselves and what we owe to others.
The editor is our own work
TAOM Process Studio uses no third-party modelling library. Rendering, editing and evaluation of BPMN models are developed entirely by Traniva AG.
That is unusual: most BPMN tools build on a widely used library whose licence requires attribution inside the editor. For us, building it ourselves means we can attach attributes to process steps, search across all models and connect agents without running into the limits of someone else’s software.
The QR code is ours too
QR codes on printouts, certificates and invoices are generated by us — on the server and in the browser, without loading a single line of foreign code.
The usual approach is to fetch a library from a content delivery network. But that means every printout sends a request, including the visitor’s IP address, to a foreign server, usually in the US — for a graphic made of black and white squares. Our implementation follows the same standard and was verified module by module against an established reference.
What we owe to others
No serious product comes from nothing. TAOM runs on software others built over years and made openly available — and we are glad to name it.
| Component | Used for | Licence |
|---|---|---|
| Linux | Operating system of the servers TAOM runs on | GPL-2.0 |
| nginx | Serving pages and protecting workspaces | BSD-2 |
| PHP | The language the platform runs on server-side | PHP License |
| MariaDB | Database for attribute directory, accounts, statistics | GPL-2.0 |
| WordPress | Foundation for website, accounts and API | GPL-2.0 |
| WooCommerce | Shop, licences and invoices | GPL-3.0 |
| n8n | Automation layer between editor and language model | Sustainable Use |
This list names the load-bearing components. It does not replace the full licence texts shipped with the respective projects.
Where your data is processed
Openness does not stop at libraries. Which service providers are involved in processing, for what purpose and in what location, we keep up to date:
What we do not load
Two things that are standard on most websites and absent on ours:
No fonts from foreign servers. All typefaces sit on the same server as the page. Calling a font service would transmit the visitor’s IP address on every page view.
No Gravatar profile pictures. WordPress normally loads profile pictures from a service in the US, addressed by a hash of the e-mail address. Ours are stored locally; anyone without a picture gets a mark generated on the server.
Both are verifiable: open your browser’s developer tools and look at which addresses are requested when this page loads.
Why we write this down
We ask our customers to entrust us with processes that carry verification duties and approvals. Anyone doing that may ask what the software stands on and where data flows.
That answer belongs on a page people can find — not in a clause they have to look for.
As of 23 August 2026 · Error or missing attribution? info@traniva.com