Support and Maintenance en Porto
How we work in Porto
A document for starting the project without us
What gets installed, in what order, which variables are needed and how a change is deployed. It is written at the start and kept current, because a maintenance arrangement where only we know how to deploy is not a service: it is a key we have taken from you. Your team has to be able to start it by reading.
Emergency fixes come with an expiry date
When something breaks you fix it however you can, and for a few hours that is fine. What is not fine is the fix moving in for good. Every emergency repair is written down and goes back into the queue, to be redone in cold blood. The projects nobody dares touch are a pile of fixes that never came back.
Backups that really are restored
A daily copy off the main server and inside the European Union, with a test restore every so often on a separate environment. And one detail that only matters the day you want to move: that it can be brought up at another provider and not only at the one that produced it.
Cancelling has to be cheap
No long tie-ins, and the handover included in the price: access, documentation and a call with whoever comes next. We would rather you stayed because the service is worth it and not because leaving is a hassle. A supplier who holds on through exit difficulty ends up giving just enough service.
Answering your questions
What people ask us about Support and Maintenance in Porto.
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
Support and Maintenance: stack, process, use cases and FAQs