Web Design and Development en Munich
How we work in Munich
The file gets written while the thing is being built
Architecture diagram, the third-party services involved, where each piece of data is stored and who can reach what. Pulling all that together once the project is finished is weeks of archaeology; noting it down as each decision is made costs a few hours spread out. When the first questionnaire arrives, the answer is already written.
Named accounts, no shared logins
A password five people use cannot be revoked when one of them leaves. Everyone signs in with their own account, with two-factor and the minimum permission they need. Removing access becomes a one-minute job instead of a notice sent to everybody.
The hosting region is chosen on day one
Germany and Spain apply the same data protection regulation, and the project can stay entirely on servers inside the European Union, with no international transfer to document. Changing region once there are customers inside is extremely expensive, and it always comes up late, when somebody asks.
Dependencies, inventoried and dated
Which libraries the project carries, at which version, and which ones have stopped receiving fixes. It is a list that generates itself if it is planned from the start and has to be rebuilt by hand if it is not. It answers the question when you are asked, and tells you what needs updating.
Answering your questions
What people ask us about Web Design and Development in Munich.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Web Design and Development: stack, process, use cases and FAQs