Custom web application development
A web application is the only format that reaches everyone with nothing to install. It is also the one that forgives a sloppy architecture least, because everyone suffers the same slowness at the same moment.
What we build
Client portals, internal management tools, configurators, dashboards that pull several sources together, supplier extranets. What these projects have in common is not a technology, it is that they replace a binder, a shared file or an inbox that has become unmanageable.
We start from the actual process, not from the mockup. How many people enter data, who approves, what happens when two people edit the same record, and what must remain when someone leaves the company. Those answers drive the architecture far more than the choice of a framework.
- Client portals and secure workspaces with named access
- Internal management tools that replace a shared spreadsheet
- Dashboards aggregating several existing systems
- Configurators and online quotation journeys
- Programming interfaces to open your data to partners
The technical choices, and why
We work in TypeScript end to end, with Next.js for rendering and PostgreSQL for data. This is not an aesthetic preference: one language on both sides reduces the surface for mistakes, and a mature relational database avoids reinventing guarantees that forty years of engineering already settled.
Rendering happens on the server wherever content has to be found or read quickly. An application that takes four seconds to show its first page loses its users before proving anything.
- TypeScript, Next.js, PostgreSQL, Prisma
- Server side rendering for first paint and for search
- Named authentication, roles and an access log
- Automated tests on the journeys that are expensive when they break
- Reproducible builds and immediate rollback
After launch
A web application is not delivered, it is operated. We keep security updates, monitoring, backups verified by actual restore and response times in hand. That is the part providers avoid, and the one that decides whether the tool is still in use three years later.
- Zero downtime deployment, several times a week if needed
- Continuous monitoring and alerts on response times
- Backups tested by restore, not merely scheduled
- Security fixes applied without waiting for an incident
Custom web application development
How long until a usable first version?
Six to twelve weeks for a well held scope, provided business decisions are taken during the project rather than after it. The limiting factor is almost always the availability of the person who knows the process, never the speed at which code is written.
Where is the data hosted?
In Switzerland or in the European Union, depending on your obligations. We do not use a host whose backups travel elsewhere without your knowledge, and we give you in writing the location of primary data, backups and logs.
Can we take the code over later?
Yes. The repository is yours, the deployment documentation is part of it, and we use no proprietary component that would tie you to us. A handover to another team is prepared, not improvised on the day it becomes urgent.
Mobile and web applications
Applications built to last, with a running cost known from the design stage.
In the division Mobile and web applications
Let us talk about what you want to build.
Describe your situation in a few lines. If it falls outside what we do well, we will say so immediately.
Get in touch