Software engineering from Vienna for the DACH region
Software engineering that reaches production.
We build domain systems you can evidence under audit, with large customers properly isolated. Control over data, identity and business logic stays with you — into operations, anchored internally.
01 — Starting point
Most people call us because something has to become provable.
Not “we would like some modern software”. A concrete trigger that suddenly becomes existential.
An audit finding that cannot be closed cleanly from the inside. A major customer demanding real tenant isolation, their own identity integration and audit trails. Or simply time pressure: hiring for it internally takes months — the initiative has to happen now.
For SaaS teams it is almost always the same moment: the product works for smaller customers, then the first enterprise prospect arrives — and the security questionnaire asks for data isolation, SSO and evidence. The deal has an expiry date; retrofitting costs more than it is worth.
And regulation does not arrive once — it returns every year. Whoever only reacts to NIS2, CRA and the AI Act pays every time. Built well, the next requirement is an extension, not a new project.
02 — Provability
Provability: what your system can evidence when it counts
Auditors, major customers and regulators do not ask whether you work carefully. They ask for evidence — and they return every year. Provability is durability, not a firefighting exercise before the audit.
Who changed what and when, how tenants are isolated, what can be reconstructed after an incident: that comes out of the architecture or not at all. A ten-question self-check shows you in five minutes where your system stands today.
03 — Our foundation
Event sourcing, agentic AI, compliance — why they belong together.
Three things have to come together: processes recorded immutably; AI that can decide reliably on top of them; and an architecture that absorbs yearly audits as an extension rather than a building site.
- Who changed what, when — evidenced in an audit, not reconstructed
- Tenant data cleanly separated at the event level
- Reconstruction after incidents in hours instead of weeks
What stays with you throughout: data, identity and business logic — no vendor lock-in.
About04 — What we deliver
One core, clearly drawn.
Architecture into operations, with ownership for the result — that is our core capability.
Software engineering & delivery
We build and ship — and own the outcome.
Custom software, event modeling, identity & access and platform — from architecture to operations, through an experienced network.
- Event modeling, DDD & event sourcing
- Keycloak, multi-tenancy & permission systems
- Platform: Kubernetes, IaC, CI/CD, observability
05 — Ways to start
Concrete entry points
One clearly scoped cut that closes the most critical gap — instead of a concept phase.
Problem
“The customer demands real tenant isolation, their own identity integration and audit trails. We cannot deliver that.”
Our approach
Keycloak & multi-tenant access
So the first large customer does not die on the security questionnaire and the second costs nothing new: tenant and permission model first, SSO integration, handover into operations. Identity stays yours.
See detailsProblem
“We have been discussing requirements for months and nobody shares the same picture.”
Our approach
Event modeling & adoption sprint
Two to four weeks to a decision basis: model the domain together, name the boundaries, record who inside the organisation answers for it afterwards.
See detailsProblem
“Hiring for this internally takes months. The initiative has to happen now.”
Our approach
Fractional tech leadership
Technical accountability on demand — architecture decisions, delivery steering and building the internal team, until someone on your side can answer for it.
See detailsProblem
“We log into the database, but anyone can change that.”
Our approach
Delivery with ownership
One core slice into production, with immutable history exactly where it hurts — instead of rebuilding the whole system.
See detailsWhat we are not the right answer for: pure capacity at an hourly rate, “modernisation” without a concrete trigger, and initiatives where provability, isolation and control simply do not matter.
KAIHITO FlexCo (in formation) — we reply async-friendly within 1–2 working days.
06 — Frequently asked
Answered briefly
- When do you start operating?
- We start operating with the company's formation in September. Before then we can already talk, think through your situation together and consider what would fit.
- What does a first conversation cost?
- Nothing but 15 minutes of your time. We clarify what it is about and say openly whether we are the right fit.
- How fast will I get a reply?
- Usually within 1–2 working days. We work async-friendly, so a written description is a perfectly good start.