News Published on 10 August 2026
Why we build without dependencies
An institutional site meant to last ten years is not built on a stack you have to rebuild every six months.
Most sites delivered today rest on hundreds of libraries whose role nobody on the client side knows. Two years later, the smallest fix requires rebuilding a whole environment, often no longer compatible with the machine it used to run on.
We take the other road when the project allows: hand-written code, no build step, a database that fits in a file, and a deployment that consists of copying files. Shared hosting is enough.
This choice has a cost: we write ourselves what a library would have provided, and that takes time up front. It also has a limit: it is not the right approach for a very high-traffic application or one with very dense business rules. We say so when that is the case.