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.
- 1Your business processes are too complex for standard software.
- 2You need to combine and process data from different sources.
- 3Your existing system is becoming increasingly hard to maintain.
- 4A system outage costs you revenue and trust.
- 5Your company is growing faster than its software.
- 6Crucial domain knowledge is buried in Excel files or manual processes.
What we build — and what it is shaped around: your domain.
Sign-in, user management, and operations often make up the largest part of a business application. Our CDS platform already provides this infrastructure. We only build your specific application. You pay for your business logic, not for standard infrastructure.
1. Domain applications
We build custom software for your specific business logic. It remains maintainable and grows with your company. The software adapts to your processes, not the other way around.
Operated in Switzerland
2. System integration
We connect your systems. Your team keeps working in the tools they know. The integration belongs to the application, it is not a separate project.
Standard connectors
3. Intelligent data processing
We build systems that process large data volumes from multiple sources in real time. They compute complex scenarios and present the results clearly, even as data volumes grow.
Event-driven processing
4. Reliability engineering
We build software that runs stable under heavy load. Reliability and security belong to the architecture, they are 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 build on each other. The result of one step flows into the next. We work in one-week iterations. You see the current state at every handover and intervene before we continue building.
- 1
Understand
We analyse your processes and goals and document our understanding.
- Goes in
- Your request, meeting notes, existing decisions
- Comes out
- A story that describes your problem
- 2
Architecture
We design a stable architecture and divide the work into reviewable packages.
- Goes in
- The approved story
- Comes out
- One plan per package, with an acceptance criterion
- 3
Development
We build in short cycles together with your domain experts. We implement each package separately so faults stay isolated.
- Goes in
- The approved plans
- Comes out
- Tested software on the integration environment
- 4
Operation
You review and approve the software before the release. Afterwards we take over operation, maintenance, and further development.
- Goes in
- The tested software, your acceptance criterion
- Comes out
- A signed-off release — and the next round
Every line of code traces back to your request. Even six months later you read in the version history why we built something the way we did.
You know your goal, but not the first step. A pragmatic start.
Let's talk about your project.
We support you from architecture to operation. Bring what you have: a process, a system, or a requirement that standard software cannot meet.
Prefer to talk in person?
Michael — Call us, send an email, or tell us what it is about — whichever you prefer.