For regulated mid-sized companies · Stuttgart, Germany
We build software for your business processes. It records who decided what, and on what basis. Any later change to that record can be detected.
The software shown here is already running. Try the demo. Your own copy of Approval, deleted after 24 hours. No sign-up.
What this is about
Before a team works with AI, two questions need an answer: which data may a model receive, and who checks what it produces? Our libraries enforce the data rules and record every review decision. Here is how, by example.
An example
Ms Berger keeps the customer records in accounts. Kai is her team’s AI assistant: he reads incoming requests and drafts the changes. Whether they are made is Ms Berger’s call.
Data sent outside your organisation
Confidential content is sent to an outside AI service without anyone checking it first.
Decisions without proof
Without a decision record, it is hard to reconstruct later who approved a change and why.
Every request, the same path
Each station passes on only what it has checked. That is how a request becomes a decision you can prove.
ExampleA customer changes their bank detailsInvented case, for illustration.
Request
A department sends in a case, with its documents.
The email: “Please change my bank details. New IBAN attached.”
Classification
Public, internal or confidential — checked before every model call. Confidential content stays in your environment.
Name and IBAN are confidential, so Kai uses a model in your environment. These details stay there.
AI proposal
The AI prepares a proposal with the current values beside it. It writes nothing to the database itself.
Kai drafts the change: new IBAN in the customer record, the old one beside it, the email as the source.
Human review
A responsible person accepts, edits or rejects the proposal, in part if need be.
Ms Berger checks the proposal against the email and accepts it.
Ledger
Each applied change is chained into the ledger: who, when, on whose behalf. Later edits show.
Entry: bank details changed, accepted by Ms Berger, on the customer’s behalf, 14 Oct, 9:42.
Evidence
The evidence for a period is generated from the ledger, ready for the audit.
At the next audit: every change of bank details this quarter, and who accepted each one.
Why octabits
Rules your IT can read
Every station is an open-source package, 29 in all. From November 2026 your IT or an outside auditor can read what they do.
We use them ourselves
Approval, Reynt and Freiday run on the same libraries.
You talk to the architect
Daniel Hartmann is a software architect with 25 years of experience. He is your contact at octabits and develops your application.
A real product: Approval
Every new piece of software needs approval from data protection and information security. That means reading the documents, collecting the facts, writing the assessments. In Approval the AI does this groundwork — only your officers may sign.
“May we use this new software tool?”
A department requests software. Approval reads five vendor documents, drafts both assessments and puts them in front of your officers.
Facts extracted for your review
Five documents, fourteen facts, each with its quote. A quote the document does not contain is rejected.
Your team decides
The model proposes and drafts. A person accepts each fact, and only the officers can sign.
The evidence is recorded
The log records every request, document version, decision and signature. Hash-linked entries make later changes detectable.
It notices when the facts change
A changed document invalidates the facts it no longer supports and reopens the approval based on them.
Watch it run
This shows the process used in Approval, with fictional requests, documents and figures.
We can implement this division of work for your processes, in a new application or your existing software.
A quotation that is not in the document is rejected at once.
What we offer
Already running
Share when you are free, not what you are doing
Freiday shares your availability by link: a week view of busy and free times from all your calendars. The link expires on its own. Freiday stores no titles, places or attendees, only when you are busy.
Booking platform for holiday rentals
Reynt helps holiday rental operators manage bookings, offers, payments and invoices, with storefronts and compliance features. We develop and operate it using our published libraries.
Working together
How does the process work today, and who decides? A spreadsheet from your daily work is a good start. The first call is free.
For the agreed scope: a first version in week one, delivery in 4–6 weeks
We develop your application for a fixed price and agree a monthly fee for ongoing maintenance.
Development at a fixed price, with monthly maintenance. Prices in detail →
For management
Tell us briefly what you are working on and where you need help. Email is the fastest way to reach us; the person who would work with you will reply.