Support and Maintenance en Brisbane
How we work in Brisbane
What we can do without calling you, in writing
Roll back a deployment, restore a backup, switch off a failing feature, scale up a server. The protocol says what we do on our own, up to what spending limit, and who gets told afterwards. Without that permission in advance, an outage during your working day waits for daylight in Spain.
The keys are located before the incident
The most expensive question during an incident is who holds the access. Domain registrar, hosting provider, mail accounts, certificates and contact people are all documented when the contract starts. Hunting for a credential with seven hours in between turns a twenty-minute fix into a lost day.
Detection doesn't depend on somebody reporting it
Availability, performance and error monitoring, with alerts separated by severity. It matters more here than with a nearby client: much of your working day passes while it is night in Spain, and if the warning depends on an angry customer writing in, the incident starts with hours of a head start.
Backups are tested before they are needed
A daily copy held off the main server, and a restore genuinely tested by bringing the site up from scratch in a separate environment, with a record of each test and how long it took. On the day it is needed there will be no margin to work out where anything is, or to wait for somebody to wake up.
Answering your questions
What people ask us about Support and Maintenance in Brisbane.
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