werknario is an open tool for offices where the same kind of case comes up again and again: official notices, statements, file notes, checks. A program reads the documents in your own files, gathers what belongs in the draft, and hands it to a named person to approve. Nothing is saved until that person agrees. An agent, our word for the program, is software that carries a task through to the end, not just answers.
what actually goes away
A case splits in two. The first part is gathering, transferring and writing: going through the file, pulling figures out of three documents, putting the text together. The second is judging: is this right, do we stand behind it, will it be signed. werknario drafts the first part. The second stays with you, and that is the intent.
That is why checking costs less than writing. Every value in the draft points at its source, at a file and a line range. If the agent cites a file it never read, the draft fails before a person sees it. And what it cannot ground stays an open slot: the cost centre then reads COST CENTRE OPEN.
do the maths
For the activity “preparing final information, issuing an official notice”, the German Federal Statistical Office allows 60 minutes at medium complexity; 5 minutes for a simple case, 480 for a hard one. The explanatory column names official notices and file notes specifically. That is exactly the activity werknario drafts.
What remains is checking and signing. How long that takes at your office we do not know. We have not measured it at a customer, so there is no percentage here. Take a case you had twenty times this month and measure once how much of it was gathering and how much was judging. The first part is the one at issue.
Source: Statistisches Bundesamt, Leitfaden zur Ermittlung und Darstellung des Erfüllungsaufwands in Regelungsvorhaben der Bundesregierung, February 2026, Annex 7. Time values as of January 2025.
does this fit you
No server of your own, and nobody to run it? That is no argument against it. We set werknario up for you, build your workflow on top of it, and connect the systems you already work with.
Does this sound like your office? Name a case you handle often and we will look at it.
for your field
Open your field. Each line is a draft a person on your side approves. Your field not listed? Write to us and we will go through your workflow.
werknario does not replace RA-MICRO or beA. It works alongside them, through the export and import path RA-MICRO already offers: the file out, a draft for a brief or a case note in, checked and approved by a person. Messages over beA are still sent by the admitted lawyer.
werknario does not replace DATEV. It reads receipts and booking data from the folder where they already sit, and drafts, for example, a posting proposal or a query to a client. It puts the result back in DATEV format or in the receipt-transfer folder, approved by the tax adviser before anything is booked.
Whether Haufe PowerHaus, etg24, Domus, or immoware24: werknario replaces none of these. It reads what your software exports, drafts, for example, an annual statement or a resolution record, and writes the draft back into the same folder you import from. Every draft is approved by the appointed manager before it goes back into the system.
University offices work with a campus-management system (such as HISinOne) and often a document-management system (such as d.velop) as well. werknario replaces neither; it reads their export, drafts a decision notice, a file note, or a reply, and puts the draft to the authorised office for review, in the examinations office, the student office, or faculty administration. Post over EGVP is still sent by the university itself.
werknario reads what your building case system (such as GekoS Bau+ or ARCHIKART) or e-file (such as d.velop) exports, such as a building file or a deadline note, and drafts a decision notice, a file note, or a reminder. The case system and e-file stay the leading systems; werknario places its drafts alongside them over the existing export and import path. Every draft is checked and approved by the authorised office head, as the signing rules already provide.
In manufacturing, order and invoice handling runs through an ERP system, depending on the firm proALPHA, APplus, abas, or SAP Business One. werknario does not replace it; it reads receipts and order data from the export folder of the ERP or document system and drafts, for example, an order confirmation or the approval note for an incoming invoice. Approval is by management or an authorised officer before anything goes back into the ERP.
Whether ALV, Mercat or Reprtoir, plus your distributor's back end: werknario replaces none of these. It reads what they output as text, CSV and PDF, along with session notes and contracts, and drafts a split sheet or a GEMA work registration with contributors and shares per category. A share that appears in no source file stays in the draft as SHARE OPEN. Filing stays manual: the work registration in the GEMA portal through the member account of the entitled party or the publisher, the repertoire report in label.gvl by the phonogram producer holding a GVL agreement.
Whether connactz or Master Tour, plus a system like Release Rooms that brings catalogue and live together: werknario replaces none of these. It reads enquiries, contracts, receipts from the folder and the ticket settlement that comes from the promoter, and drafts a deal memo or the settlement after the show. Every line points at its evidence, and where the evidence is missing or arrives as a photo with no text layer, the line stays open. Signing is done by the person authorised to represent the agency, and for the performance contract, depending on how the deal is structured, by the artist.
an honest line
why this and not just any AI
alongside your software
DATEV, RA-Micro, beA, Haufe, your case-management system, or your ERP stay where they are. werknario reads what those programs export, drafts the change, and puts it up for approval; what you approve goes back through the same folder. A few systems like etg24 or d.velop have an open interface for a closer link.
for regulated offices
When a GDPR review comes, the first questions already have an answer here: Where does the data live? With you. Does it leave the EU? Not by default. Does a person stay responsible? Yes, approval is by hand. Is it traceable? Yes, every step is in the log. For professions bound by confidentiality, that is the first question.
Your files stay in a store that belongs to you, on a computer you control, with version history. When a task needs an AI model, werknario blocks models outside the EU by default as soon as personal data is involved.
werknario stores personal content encrypted by default, with a separate key per record. When content is deleted, that key is destroyed; without it, the plaintext can no longer be read (crypto-shredding). Whether this amounts to complete erasure under Art. 17 GDPR depends on your environment: no copies of the key and no separately restorable plaintext backups may remain.
The approval log is not exempt from this. What remains verifiable afterwards is that an approval took place and that the chain is unchanged, not the personal plaintext. This coverage of the log's free-text fields is planned as a default and not yet built.
Do you work with a works or staff council? werknario logs approvals, and if someone approves and merges their own work, that too, as in software development. Such a log can make conduct and performance visible. So involve your employee representatives early.
A reviewed text on controller and processor roles, retention, and deletion follows separately, checked by a lawyer. We do not promise here what we cannot show.
what it costs
werknario is open source, there is no licence fee. You pay only to run it: a server in the EU in the low tens of euros a month, and a few cents per document processed for the AI model. Setup is a one-time project handled by someone with technical experience. What that means for your case we work out after a short conversation, rather than name a number here that will not hold for you.
On liability: because werknario is open source, it comes without warranty (Apache License 2.0, Sections 7 and 8). You run it in your own environment, an agent drafts, an authorised person on your side approves, and you put the result to use. Responsibility for what is approved and used rests with your organisation and with the approving person. Whatever the law requires without exception, such as liability for intent or for harm to life, body, or health, remains in place. The binding terms are set out in the licence and in our terms of use.
getting started
No developer team? Then we take that on. We set werknario up for you, build the workflow you actually need, and connect the systems you work with. If you would rather set it up yourself, there is a guided kit that walks you through it step by step. A person signs in once, the program does the rest.
Need more? If you have particular requirements, such as large data volumes, special data-protection needs, or a link to a specific system, get in touch. If enough people want it, we build it into one of the next releases; otherwise we build it as a solution for you.
The first step is a conversation, not a project.
For the technical
The whole flow, offline: no account, no key, no server. It runs against an example store with a fixed model, so you see the shape of it.
Works the same on Windows, macOS, and Linux. The whole source is open under Apache-2.0.