We build software meant to last decades.
Interware is a founder-led engineering studio on the Microsoft stack. For more than 25 years we've designed, shipped and maintained mission-critical line-of-business systems — including one we built and evolved for 22 years straight. Most of our work is done under contract, embedded in our clients' teams — and lately some of that craft has also gone into products of our own.
Engineering you don't have to babysit.
Contract engineering
Senior, founder-led development of line-of-business applications across desktop, web and mobile — specified, built and delivered without a layer of account managers in between.
Long-term maintenance
We don't vanish after v1. Systems get evolved for as long as the business needs them — through regulation changes, platform shifts and a generation of Windows. We measure relationships in decades.
Product development
Turning deep domain knowledge into products with their own legs. enaro and drive-evos are the first two coming out of the studio — built on the same engineering discipline as our client work.
Architecture & consulting
Platform choices, modernization paths and the hard calls — from someone who has lived with the consequences of those decisions for twenty years, not twenty months.
The proof is in the longevity.
Four engagements that mattered — and one that lasted twenty-two years.
Interware has never chased logos. The track record is a short list of deep, long engagements — the kind where you live with your decisions long enough to learn what “maintainable” really means. Software like that usually costs more to build and less to own: fewer rewrites, fewer surprises, a lower total cost over the years it stays in service.
Interware founded
Set up as a senior engineering practice — built to take on long, serious work without the overhead of an agency.
Traffic-control systems
Communication software for signalling devices and their interoperability, for a global industrial group's traffic-control division — early, unforgiving real-world systems.
First .NET application
An RMA platform for a computer- and parts wholesaler — one of our first production systems on .NET, and the start of a stack we’d back for the next two decades.
Share-register platform
Flagship · 22 yearsTwenty-two years on one platform at the edge of the stock-exchange industry, used every day by the client’s own staff and run entirely on their own infrastructure — no cloud, no outside dependency. We designed it, built it and evolved it the whole way; from 2010 I held the role of acting CTO, as an external. Through changing regulation, shifting platforms and a generation of the Microsoft stack, it never became the system nobody dared to touch. Retired cleanly at the end of 2024.
Swiss energy · Trading onboarding
For one of Switzerland’s largest energy companies: an internal platform for managing client contracts and onboarding them into the trading system. Modern Blazor and C#, for a business where reliability isn’t negotiable.
What the long game teaches.
Some endings aren't technical
A project can stop for reasons that have nothing to do with the work. A delivery-planning system we began for a coach-and-bus dealer in the summer of 2001 was cancelled during the prototype phase when, after 9/11, the budget simply vanished. Good engineering can't outvote that — so we build to hand over cleanly rather than to make ourselves irreplaceable.
Right solution, wrong moment
A design can be entirely feasible and well-built, and still be postponed as priorities move. Engineering has to align with business timing, not just the specification.
Scope always moves
Long initiatives shift direction as new insight arrives. Robust architecture absorbs that change without losing its coherence.
Legacy deserves respect
Older platforms carry deep domain logic and operational reality. Sustainable modernization starts by understanding what already works — not by treating it all as debt.
Organizational change reshapes software
Leadership transitions, mergers and budget cycles can redirect a roadmap overnight. Software lives inside organizations, and has to adapt when they evolve.
Adoption needs a sponsor
Even excellent work doesn't roll out without internal ownership and the right timing. Delivery includes stakeholder alignment and clear ownership, not just the build.
Run it where you can actually keep it.
This isn't a reaction to the headlines. For two decades we built systems that simply ran — on our clients' own infrastructure, in a world where the cloud was never even an option. Lately we've seen the other side up close: a modern, cloud-dependent operation brought to a standstill because a service an ocean away couldn't be reached. The newest risk to critical software isn't technical — it's who holds the keys.
We help clients get out from under the American cloud giants — building on Linux, Docker and Kubernetes, on infrastructure you control: your own hardware, a Swiss or European host, or a private cloud. Built to move, so no single vendor — or government — ever holds your business hostage.
Run anywhere
Containers and Kubernetes from the first commit. The same system runs on your servers, a Swiss data centre or a private cloud — your call, reversible at any time.
European by choice
Keep data and workloads on this side of the Atlantic, under Swiss and EU jurisdiction, whenever that's what your business — or your regulator — requires.
Portable by default
No proprietary lock-in baked into the foundation. A change in a provider's terms becomes an inconvenience, not an existential risk.
A few things that are also ours.
enaro · enaro.energy
An operating system for local energy. Measuring, distributing and settling locally produced power for energy communities — telemetry, routing and billing on the installation itself.
Visit enaro.energy → Active developmentevOS · drive-evos.com
EV-native navigation and vehicle intelligence for electric cars whose factory software never kept up. Range-aware routing, live telemetry and offline maps — running on hardware in the car, with no cloud dependency. A Rust core, native on Linux and Android.
Visit drive-evos.com →How we work.
Senior by default
You talk to the people who write the code. No account layer, no hand-off to juniors once the contract is signed.
Optimized for the decade
We make choices that still look right in ten years — not the ones that demo best this quarter. Boring where boring wins.
Sustainable solutions
Maintainable, documented and built to be handed over. Software that a future team — ours or yours — can actually live with.
Windows, period — and beyond
Deep on the Microsoft stack since 1998 — and fluent in where it's going: Blazor on the web, Avalonia and MAUI cross-platform, Linux and Kubernetes in production. And it reaches all the way down to the metal: bare-metal Rust on an ESP32 — our own SignalR, rebuilt in Rust, running on the chip itself — driving real-world devices over RS-485. The newer work — AI-agent infrastructure (MCP servers, semantic memory) and shared-memory gRPC — gets the same long-view discipline.
We join your team.
At home with XP practices — pair programming, review, working in the open. Over the 22-year engagement we brought two junior developers up to senior level through pairing, until they left for adventures of their own.
We hold a Professional Scrum Developer (PSD I) certificate and slot into a Scrum team without fuss. The conviction underneath is agile with a small a: working software and honest adaptation over ceremony.
Lead a build, or work as a senior pair of hands inside an existing team. Remote across the DACH region or on-site in Switzerland. Contract terms, no agency in between.
Founded in 1998 and still founder-led. Interware is deliberately small — a senior engineering practice, not an agency — working with clients who need software that outlives its roadmap.
Have a system that needs to outlast its roadmap?
A few lines is plenty to start — what you're building, the rough scope and timeline, whether it's on-prem or cloud, and how best to reach you.