Operations & support
Backups run. Updates follow.
A backup counts when it can be restored.
We find the cause and test delivery again.
What is done. What stays open. What comes next.
It runs. And you know why.
Hosting, updates, backups, monitoring, incidents and small changes: one team takes all of it on. For systems we built and for systems we take over. Code, data and access belong to you, and a handover is possible at any time. The monthly report tells you what we did.
The operations plan is part of your proposal. It states what we do for your system and how often. Here is an example.
| Task | What we do | Rhythm |
|---|---|---|
| Hosting | Data protection first: providers from Germany and Europe, for example Hetzner or netcup. Or your own environment. | continuous |
| Updates | Security updates first. Larger updates after your approval. | monthly |
| Backups | One every day. Once a month we restore one as a rehearsal. | daily · rehearsal monthly |
| Monitoring | An automated check keeps looking whether your system is reachable. | continuous |
| Incidents | We follow up on every report: find the cause, fix it, test again. | when reported |
| Small changes | A field, a text, an account. | after approval |
Scope, rhythm and times are set out in your proposal. Provider names are trademarks of their owners.
No charts, no metrics: the report says in full sentences what is done, what we noticed and what is coming up. What remains unclear is listed as open, not as done.
Deutsches Finanzwerk
For Deutsches Finanzwerk, we designed and built the client portal and administration. Today we also run the system: hosting, updates and support come from the team that built it.
Frontend & backend concept: Patrick Hofbauer
Explore the case studyConversation · linked automatically
Linked advisory case
Investment property purchaseOpen requests appear in the personal client portal.
We do not take over a system built by others blindly. In the operations assessment we look at its state, access, dependencies and risks. The result is a clear answer: we take over, we take over after defined preparatory work, or we decline with reasons. Then you receive a proposal.
Then
Not as a blanket promise. How fast we respond, during which hours and through which channel is agreed for each system. It depends on what an outage means for your daily business. We do not promise permanent standby off the shelf.
Yes, after an operations assessment. We look at state, access, dependencies and risks. The result can be: we take over, we take over after defined preparatory work, or we decline with reasons.
With a provider from Germany or Europe, for example Hetzner or netcup. Data protection comes first in that choice. On request we run your system in your own environment. Provider names are examples and trademarks of their owners.
Anything that does not rebuild your system: a new field, a changed text, another user account. The scope is set out in the operations plan. New features and larger rebuilds get a proposal of their own.
A backup only shows that data was copied. Whether your system can be restored from it is shown by the rehearsal. So we restore backups as a rehearsal in the agreed rhythm. The result is in the monthly report.
Yes, at any time. Code, data and access belong to you. We keep documentation, access and data export current; every monthly report states where that stands. We plan the handover with you.
A short description of the system and someone who knows it. Read access is needed only later; we agree a separate channel for that, never the contact form.
