TYPO3 maintenance and support.
Quality doesn't end at sign-off.
We continue to look after your TYPO3 website after launch: with regular updates, technical monitoring and support with questions or faults. Your contacts know the system and plan further development together with you.
We also take over existing websites from other service providers. At the start of the collaboration, we clarify which services and service hours you need.
After launch, ongoing operation begins.
Over time, the technical requirements of a website change: PHP versions reach the end of their support, extensions are no longer maintained and a new TYPO3 LTS version is due. If clear responsibilities and a reliable maintenance plan are missing, necessary updates are easily postponed.
The longer several technical dependencies remain unchanged, the more laborious later modernisation can become.
At the same time, smaller problems accumulate: messages from a form are no longer reliably delivered, a data import runs into errors unnoticed or individual functions can no longer be operated well on a smartphone. Taken on their own, these shortcomings are often manageable. In total, however, they impair daily work and trust in the system.
Sometimes an unclear handover situation is added: the previous service provider can no longer be reached, the documentation is incomplete or important access details are missing. We also take over existing TYPO3 systems that were originally developed by another agency.
Our TYPO3 support combines regular maintenance, personal TYPO3 support and the plannable further development of your system.
The first step is a structured assessment. It shows how the system is built, which risks exist and what should be clarified or updated first.
Clear responsibilities. Reliable processes.
Reliable operation begins with clear responsibilities, agreed processes and transparent priorities. That is why we jointly define:
- Which components are regularly checked and updated?
- How do we test and publish updates?
- Which response times apply to security vulnerabilities and faults?
- Who decides when an update requires further adjustments?
- How do we proceed in the event of a specific security incident?
We do not install updates on the production system without checking them. We assess security advisories promptly based on their criticality and the actual threat to your installation. How quickly we respond to an incident and start working on it depends on its urgency and the agreed service hours. We define the procedure for necessary immediate measures in advance.
We plan larger TYPO3 upgrades and version changes early, before regular support for your version ends, and prepare them separately. We first check extensions, custom code and the server environment on a test installation. We agree the time of publication with you in order to keep effects on ongoing operation as small as possible.
For us, responsible maintenance also includes the economic perspective. If the long-term operation of a heavily outdated or heavily customised installation becomes disproportionately laborious, we address this openly.
We then compare continued maintenance with a step-by-step modernisation and recommend the path that makes more sense technically and economically in the long term.
What our support does for you.
How support runs with us.
Before we take over ongoing operation, we create a shared and transparent basis. This way, both sides know which services have been agreed and who is responsible for what.
Assessment
We check the technical condition of your installation: TYPO3 and PHP versions, extensions, custom code, server environment as well as existing documentation and access.
You receive a written overview with identified risks, open points and recommended priorities. You can use this documentation regardless of whether we then take over support.
Agreement
Together we define the concrete scope of services. This includes check and maintenance intervals, response times, approval paths and the responsibilities on both sides.
We summarise the most important provisions in a clear service description. This makes it quick to see in everyday work what has been agreed and how we proceed in different situations.
Operation
Updates, monitoring and support take place according to the defined processes and priorities. Documented changes and regular status information make it clear which work has been carried out and which points are still open.
In the event of faults, the previously agreed reporting and escalation paths apply.
Further development
At agreed intervals, we look together at the current state, open requirements and upcoming technical changes. From this we prioritise the next steps and plan effort, budget and a suitable time.
This way, your website is supported technically and developed further in a controlled way along your actual requirements.
More predictability in ongoing operation.
The technical condition of your platform remains transparent. Necessary updates, expiring support periods and foreseeable adjustments are included in planning early. This avoids a maintenance backlog and reduces the risk of unexpectedly laborious modernisations.
For your editorial team
Familiar processes remain as stable as possible, and responsibilities are clear in the event of technical problems. Your team knows whom to turn to and how a request is handled. On request, we train your editorial team directly on your own system.
For your management
Upcoming measures, priorities and costs become transparent. Larger version changes or technical adjustments can therefore be included in time and budget planning early.
If the effort develops differently than expected, we address this in good time. Together we then decide whether the scope should be adjusted, the implementation split up or another path chosen.
Platforms for long-term operation.
These projects show why ongoing support is just as important as a successful start.
We have already had various projects carried out. Short-notice processing, a constant contact and good work!
Further tasks around your website.
We agree these services with you separately as needed.
Frequently asked questions
Questions about maintenance and support.
Yes. We regularly take over existing TYPO3 installations from other service providers.
Before support begins, we carry out an assessment. Among other things, we check versions, extensions, custom code, server environment and maintenance status. You then receive a documented assessment of risks, priorities and the next sensible steps.
We agree this to suit the importance of your platform. A heavily frequented event website may need different response times than an internal information area.
At the start, we define priority levels, service hours and escalation paths. We distinguish between the response time, the start of processing and complete resolution. This makes it clear for both sides what happens in the event of a critical fault and which requests are scheduled regularly.
The costs depend on the technical scope and the importance of the system. Relevant factors include the extensions used, custom code, interfaces, desired check intervals and agreed response times.
After the assessment, you receive a reliable estimate. We estimate and agree larger version changes or further developments in advance as separate projects.
We bill individual services transparently according to the actual effort. For clients with regular needs, we can agree a fixed contingent of hours. We plan this capacity bindingly and bill it as a monthly flat rate.
Which form makes more economic sense depends on how regularly you need support and which response times are to be agreed.
What matters is whether security updates are still available for your version and whether they are installed. After the end of regular support, paid Extended Long Term Support (ELTS) may be available depending on the version. We also check the status of your extensions and the server environment.
Together we plan when a version change makes sense or is necessary. We agree scope, effort and billing with you separately. We describe our approach under TYPO3 upgrade.
Yes. We schedule smaller, clearly defined adjustments within the ongoing budget. We treat more extensive functions or structural changes as separate stages with agreed scope, schedule and approval.
Implementation and testing initially take place on a test environment. This reduces effects on ongoing operation and allows publication to be prepared in a controlled way.
On request, we look after your website within our hosting structure. If a suitable server environment already exists, we continue to work with your existing provider. What matters is that we have the necessary access for maintenance, updates and troubleshooting.
First we agree with you which access details and documents are needed for the takeover and what is already available. This can include the TYPO3 backend, source code, hosting, database and the existing documentation. Access data is transmitted via a securely agreed channel.
We then check the technical state and discuss the first necessary measures. Building on this, we agree the scope of services, responsibilities and the start of support.
If documents or access details are missing, we support you in clarifying them and in an orderly handover with the previous service provider. Whether and when the takeover is possible also depends on which technical prerequisites are already in place.
At the start of support, we define how cover for your contact is organised and through which contact channel you can reach us. We document important decisions, technical processes and the required access so that authorised deputies can access them.
This reduces dependence on individual people and makes handover easier. For urgent requests, the agreed service hours and reporting channels apply.
Are you looking for reliable support for your TYPO3 website?
Discuss the support of your TYPO3 website with us. For the free initial consultation, the link to the website and a short description of your current situation are enough. Known details about version and extensions help, but are not required. We agree the scope and costs of a subsequent technical assessment separately.