For your IT
Secure and compliant.
Architecture, sign-in, data storage, patching and exit.
Architecture
Four parts, cleanly separated
Editing
capture content, structure it, preview, release
Output
produces all seven editions — web, print PDF, Word, XML, XBRL, commercial-register XML and individual figures. The web edition as pre-built static pages
Permission core
decides who may see and change what
Log
records who did what, and when
The permission core depends on neither the editing system nor the sign-in method. Replace either one and it stays.
Data storage
Content and figures are held as structured JSON — tables included, whether typed, pasted or linked from Excel. No formatting in the source.
Runtime
A Node application, PostgreSQL, a reverse proxy in front. No GPU needed. The delivered edition needs neither a database nor an application server at runtime.
Sign-in
How your people sign in
Two routes, both without an extra password. You decide which one suits you.
With your company account
Your people sign in with the same account they use at their desk in the morning — in most organizations that is Microsoft Entra ID, formerly Azure AD. You keep managing access where you manage it today.
When someone leaves, their access to the report goes with them — without anyone having to remember.
Through our sign-in
No company directory of your own, or you want to bring in outsiders — auditors, consultants, an agency? Then sign-in runs through our Microsoft access, with two-factor authentication.
Here too we store no passwords, and you set nothing up.
Sign-in and permissions are two different things
From the sign-in, bonoto takes exactly one thing: the person’s immutable identifier. Not the email address, not their groups. What permissions hang on it, bonoto decides itself.
For your security review
Authorization code with PKCE, identity via OpenID Connect, access tokens validated against the provider’s key set. No secret in the browser.
Hosting
Two hosting modes, one build
Hosted by us
A data center in Germany or Austria. Every customer gets a separate instance with its own database and its own sign-in directory — nothing is shared between customers.
Hosted in your infrastructure
The same build as a deployment package: containers for editing, preview and reverse proxy, PostgreSQL as a container or as your own database service. No orchestration system required — Compose is enough.
Patching — where the line runs
| Area | Responsible |
|---|---|
| Operating system, kernel | Platform operator |
| Database, reverse proxy | Platform operator |
| Base image and dependencies | bonoto |
| Application code | bonoto |
Privacy and security
What is assured, by contract and technically
No customer data outside the EU
Hosting and backups stay in the EU. Data processing is agreed by contract, and a record of processing activities is provided.
Restores are rehearsed
Encrypted backups held off the server, and the restore is actually replayed on a regular basis — not merely configured.
Read logging can be switched off
Who viewed which part of the report can be logged — configurable per customer. If you have a works council or privacy requirements, you decide.
Open core
No vendor lock-in
An open-source core
bonoto builds on Strapi, an open-source editing system under the MIT license. The source is versioned and the building blocks are open to inspection. The permission core, the log, sign-in, the specific content blocks and all output formats are our own code.
Your content leaves
Text and figures leave bonoto at any time in open formats — not only as PDF.
Hosting can move
From us to you, with containers and an operations handbook. You remain a licensee — that does not make you dependent.
Governance, built in
What ships with it, rather than being bought on top
A log of everything
Every change to text or data point with person, time, before and after. On request also who read which part of the report — switchable per customer.
Release paths
Draft → review → released, per section and with an editing lock. Who may release is set by the head of the business unit — no administrator needed.
Version history
Every state stays traceable. A closed report is frozen and can be reproduced together with its outputs — even years later.
Single sign-on is included
Signing in with your people’s company account — or through our access with two-factor authentication — is part of the delivery, not an add-on package.
Support
Who answers when it matters
Named contacts
You talk to the people who build the product — not to a ticket number.
A commitment for the publication window
In the weeks when the report goes out, guaranteed availability and response times can be agreed.
Backed by the open core
If you decide to end the relationship, the system does not stop. The core is open source and hosting can move to you.
The content platform where teams and AI build reports together
See the demo — 45 minutes, with your own figures. No slides.