TYPO3 in the technology region
Karlsruhe asks different questions of a supplier than other places do: here sit clients whose own development teams are reading along, and institutions with high expectations of structure and traceability. That suits how we work: configuration in files, code in Git, installations built to be handed over as a principle.
Typical projects in the region: extension development with interfaces to existing systems, multilingual sites for research and industry, and SEO foundations that are technically sound rather than patched on afterwards.
A good three quarters of an hour away
Stuttgart to Karlsruhe is one of the shortest routes between our regions: around 80 kilometres, direct by train. On-site meetings are therefore not a logistics question but a question of whether they are useful: kick-offs and workshops yes, daily check-ins no, those work better as a call.
From KIT spin-off to public authority
The range in the region is wide: young technology companies that need a solid foundation quickly, alongside chambers and state institutions for whom accessibility is binding. What both have in common is the expectation that the website is a system you can understand, not a black box only its builder can operate. That is exactly how we build.
Operation is part of the conversation here
Technical clients ask about running the site earlier than others do, and that is pleasant. Instead of “how will it look” the question is “how do you deploy”, “where does the configuration live”, “what happens in a rollback”.
Our answers are unspectacular and dependable for exactly that reason: development in Git, configuration in files rather than in database records, a reproducible deployment route, backups whose restore has been tested. What an environment needs for that is set out in the guide on hosting requirements.
If your IT team provides the environment, we work our way into it rather than making a move a condition. If something does not fit, we name exactly what is missing; the decision stays with you.
Security as a shared task
In organisations with their own IT, security is rarely a sales topic but a question of responsibility. Who applies updates, who monitors the platform, who decides in an incident?
We settle that in writing before it is needed. A current TYPO3 is of little use on a server with an outdated PHP version, and the other way round. Which measures actually work and which mainly reassure is set out under securing TYPO3.