Software for complex business processes. Built for reliability, growth and longevity.
Does one of these situations sound familiar?
We do not list technologies. We solve problems that standard software cannot.
- Your business processes are too complex for standard software.
- Data from different sources has to be brought together and processed.
- Your existing system is becoming increasingly hard to maintain.
- A system outage would have serious business consequences.
- Your company is growing faster than its software.
- Domain knowledge is buried in Excel files or manual processes.
What we build — and what it is shaped around: your domain.
The largest part of a business application is rarely the business logic: sign-in, user management, integration, operations. With us that already stands as the CDS platform — all that gets added is your business application. You pay for your business logic, not for infrastructure that already exists with us.
1. Domain applications
We build custom software that maps demanding business logic — traceable, maintainable, extensible over the long term. Your software adapts to your processes, not the other way around.
Operated in Switzerland
2. System integration
We connect your systems so your people never have to leave the tools they know — the new capability shows up where they already work. The integration is part of the application, not a project of its own.
Standard connectors
3. Intelligent data processing
We build systems that reliably and promptly prepare large volumes of data and bring it together from multiple sources — event-driven and in real time rather than in ageing batch runs. They compute complex scenarios and present them clearly, even as volumes grow.
Event-driven processing
4. Reliability engineering
We build software that stays stable under heavy load, can be operated reliably over the long term and provided securely. Reliability and security are part of our architecture, not an afterthought.
Running on Kubernetes
Reliability in the customer portals
Securing systems in production — our own as the example
What we have built it for.
MeteoSchweiz
ewz customer portal
WVZ «Mein Züriwasser»
Liechtensteinische Post
Stiftung FAR
ewz.LEG
Naturgefahrenportal
The engineering view
Which architectural decision sits behind which service — and why it makes the difference.
How we work.
Four steps that follow from one another: what comes out of one step goes into the next. At every handover you can see what we are working on — and step in before anything is built.
- 1
Understand
We analyse your business processes, goals and constraints — and write down what we understood.
- Goes in
- Your request, meeting notes, existing decisions
- Comes out
- A story that describes your problem
- 2
Architecture
We design a software architecture that stays viable and extensible over the long term, and cut the work into reviewable packages.
- Goes in
- The approved story
- Comes out
- One plan per package, with an acceptance criterion
- 3
Development
We build iteratively, transparently, in close collaboration with your domain experts — each package separately, so faults do not blend into each other.
- Goes in
- The approved plans
- Comes out
- Tested software on the integration environment
- 4
Operation
Before the release you sign off what was built. After that we keep supporting your solution: monitoring, maintenance, continuous evolution.
- Goes in
- The tested software, your acceptance criterion
- Comes out
- A signed-off release — and the next round
Every line of code traces back through a plan to a story to your request. Even six months later you can read why something was built the way it was — not from memory, but from the version history.
Let's talk about your project.
Whether it's complex business logic, data-intensive processing or business-critical systems — we support you from architecture to long-term operation. In the AI potential analysis we look, open-endedly, at what your case really needs.

Prefer to talk in person?
Michael — Call us, send an email, or tell us what it is about — whichever you prefer.




