Software development
New products, modernization of existing systems and long-term maintenance. Twenty-five years of shipping Java, Kotlin, Go, Vue and Nuxt, from start-ups to automotive groups, always with the infrastructure to run it.
Three kinds of engagement
A product, a portal, an internal tool. We start with the thinnest version that proves the idea, ship it, and grow it in milestones you can stop after.
Ageing Java, PHP or monolith systems that still earn money but nobody dares to touch. We add tests, split what needs splitting, and move it to infrastructure you can run.
Software whose original developers have moved on. We take it over, keep it patched, and keep shipping the changes your business asks for on a monthly budget.
From the work
A selection across the last decade. The full list, with the kind of work for each, is on the Work page.
Dealer quoting and contract platform. Vue and Nuxt front end, Spring Boot back end, review environments on Kubernetes, Google Cloud.
Public web application for university admissions, Vue and Java, with the DevOps pipeline built around it.
Services inside a large microservice architecture, Java and Spring Boot, in several Scrum teams.
Our own HR product for European companies: Nuxt front end, Spring Boot back end, hosted in Germany with EU-only AI.
Stack
Before you call
For clearly defined scopes, yes. For products that evolve, milestones with a written estimate each work better for both sides; you can stop after any milestone with working software in hand.
Java, Kotlin, Go and Vue first, because we have shipped them for two decades. We say so when a request would be better served by something else.
Yes. The assessment week produces a written picture of the code, the tests, the deployment and the risks before we commit to a maintenance budget.
You do, from the first commit. Repositories live in your GitLab or GitHub, or in ours with you as owner.
Talk to an engineer
Thirty minutes with a senior engineer. Reply within one business day.