Backend & frontend engineering
Custom software that fits your workflows. We build backends, frontends and integrations, modernise existing applications and strengthen your team.
15 minutes with Robert · free, no obligation
devs group builds custom software for companies in Switzerland: Go backends, REST and gRPC APIs, and frontends in Vue.js — from the Bitcoin broker for Relai to the form service for the Swiss FOITT. Efficient software engineering needs a strong foundation. We build scalable applications with a firm focus on performance and maintainability. Our goal is efficient, high-performance and genuinely usable solutions that meet our clients’ specific requirements.
Our preferred technology stack
For modern applications we like to combine Golang for the backend with Vue.js for the frontend. This proven stack lets us build efficient, high-performance solutions that are at the same time intuitive to use.
Broad know-how for your requirements
Beyond our preferred stack we have deep expertise in other leading technologies. Angular, React, PHP or Python — that breadth lets us deliver complex and varied projects successfully, and adapt flexibly to our clients’ specific requirements.
Frequently asked
How do you use AI in software development?
Coding agents support implementation, tests and documentation. Our engineers own architecture and reviews. Our AI-assisted software development service explains how we connect requirements, tests and releases.
Why do you build backends in Go?
Because Go forces a kind of simplicity a team can still read three years later: explicit error handling, a static binary, concurrency you can explain. The full reasoning is in Why we build critical backends in Go, including the cases where we do not reach for Go.
Do you also extend existing teams?
Yes. On the FOITT tax administration systems our engineers work inside existing Scrum and SAFe teams on tax administration systems. Co-development and team extension are, alongside project delivery, our most common engagements.
How do you handle codebases that have grown over time?
Understand first, change second: we document architecture decisions before making them, and build observability before rebuilding anything. Why that is the cheapest available insurance against unreadable systems is in Decisions you can still understand in two years.
