We build and ship — and own the outcome.
Software engineering & delivery
At KAIHITO, engineering is not an appendix to consulting — it is the core capability. We take on architecture, implementation, production readiness and handover, and stand behind the result.
What we offer
- Event modeling: mapping the domain together with the people who own it every day — before any code is written
- Architecture work for domain-complex systems, including domain-driven design, CQRS and event sourcing
- Identity & access: Keycloak setup and remediation, multi-tenant realms, role and permission models, SSO, self-service admin UI and user migration
- Backend modernisation and implementation in JVM/Spring/Kotlin, NestJS and Angular — technology-agnostic, but not arbitrary
- Platform engineering: Kubernetes, infrastructure as code, CI/CD, observability and production readiness
- Delivery through a network of experienced architects and engineers instead of anonymous resources
- Technical project leadership: scoping, prioritisation, quality assurance, handover into operations
- Fractional tech leadership for organisations without their own technical lead
Why it matters
Architecture co-decides whether a system is accepted. Traceability, reliable history and understandable domain logic are not technical niceties — they are the reason business units trust a system instead of keeping a spreadsheet on the side.
So we do not just build what was ordered. We clarify which technical decision will carry the later usage. And we say so when the simpler solution is the better one.
How we anchor domain logic, history and traceability technically is described in our overview of event sourcing.
Articles on this topic
All articles →Engineering & deliveryFoundation
Tenant separation that survives the security questionnaire
One forgotten filter is a reportable incident. Why isolation in application code is not evidence — and which models enterprise buyers accept.
Engineering & deliveryFoundation
Software that lasts: why we start with the domain — not with the stack
Most systems do not fail because of the technology choice, but because nobody understood the domain properly. On event modeling, event sourcing and ownership as the foundation of durable software.
Engineering & deliveryFoundation
The three transitions: architecture, delivery, adoption
Software initiatives rarely fail in the middle of a phase. They fail at the transitions — where ownership quietly changes hands.