Operations and upkeep
Operations cover updates, backups, fixing faults, further development and walkthroughs. If you like, all of it comes from a single source, and you can commission each part on its own.
Software is not finished at launch; from then on it is in operation. You get consulting, prototype, delivery and upkeep from a single source, for everything I develop.
Scope
I apply updates before a vulnerability becomes an incident. I make backups and also restore them once as a test. I fix faults and develop the system further when requirements change, and they do.
Introducing new people is part of it too. Knowledge about a system rarely sits in the documentation and usually in one person’s head. When that person leaves, the whole thing starts over.
Agreement
Every step can be commissioned on its own. If you can and want to handle the upkeep yourself, you do: the systems are open, the access is yours, and I hold back nothing you need for it.
We settle beforehand what you do and what I do, not in the middle of an incident.
Limits of this phase
I do not extend anything on the quiet. An addition nobody ordered does not appear on the invoice either.
Nor does the technology tie you to me. If you want to hand operations to someone else, that is a handover and not a migration, because there is no format and no interface that only I can read.
Frequent questions
Can we handle the upkeep ourselves?
Yes. The systems are open, the access is yours, and I hold nothing back that is needed for it.
What happens during an incident?
We agree beforehand what applies then: availability, order of work, who calls whom. During an incident, that is no longer up for negotiation.