Stabilization First
The first goal is to stop the situation from getting worse. This may involve disabling features, isolating systems, or accepting temporary degradation.
Home · Services · Emergency Support
Emergency Linux & Unix Support
Emergency support exists for when something is already broken. It is not a normal way of working. The focus is stabilization, not ongoing operation.
Last reviewed: March 2026
Description
what it is, and isn’tEmergency support is intended for situations where systems are down, unstable, or at immediate risk, and no ongoing operational relationship exists at the time of engagement. The objective is to reduce damage and regain control of the situation when possible.
The departure of internal staff alone does not constitute an emergency unless it has resulted in active failure or immediate risk.
Principles
Limited Scope
Emergency work is intentionally narrow. The focus is containment, not architectural cleanup or optimization. Changes that affect business operations require explicit approval.
Clear Stop Point
Engagement ends once containment is achieved. Temporary access is removed. Any further work requires separate discussion and agreement.
FAQ
common questionsHow quickly can you respond?
Response depends entirely on availability at the time of contact. I do not provide guaranteed response times or on-call coverage for non-retainer clients.
Will you fix everything?
The objective is containment, not perfection. Some problems can be mitigated quickly; others cannot be safely resolved without deeper context, time, or preparation.
What if documentation or access is missing?
Lack of access, credentials, or system knowledge may limit what can be achieved. Reconstructing context may be required before the issue can be addressed.
Will you make permanent changes?
Changes made during emergency support aim to be conservative and reversible, but that cannot be guaranteed in all situations. Structural improvements or cleanups are deferred to non-emergency work.
Is this confidential?
Yes. All work is handled confidentially. A formal NDA can be provided if required, but emergency situations should not be delayed for paperwork.
Can emergency support turn into ongoing management?
Possibly, but not automatically. Ongoing work requires proper onboarding, scoping, and mutual agreement after the emergency has passed.
Hard limits
Emergency support does not include SLAs, guaranteed response times or outcomes. Availability depends on current workload, time zone, and existing commitments. In some cases, support may not be possible.
Access, documentation, and system condition may limit what is possible in the moment. Some situations cannot be safely resolved under emergency conditions, especially without prior system knowledge or preparation.
Data loss may already have occurred before intervention, and further loss may be unavoidable during stabilization.
Pricing
Emergency support is intentionally priced higher than ongoing management. As a rough indication, rates are typically several times standard hourly consulting rates, with a minimum engagement.
This reflects disruption cost, context switching, and the risk inherent in working on unfamiliar systems under time pressure.
Terms of engagement
Emergency support is governed by terms specific to short-term, urgent intervention, in addition to the site-wide Terms of Use. Where the two conflict, these specific terms govern emergency support.
Timely access, credentials, and accurate information are required to perform the work. Delays, omissions, or incorrect information may limit what can be done in the moment; they do not alter pricing or liability boundaries.
Changes during emergency work are conservative and focused on immediate risk reduction. Temporary measures, degraded functionality, or partial restoration may be necessary to stabilize systems. Side effects that cannot be fully evaluated under emergency conditions are accepted as part of stabilization work.
The engagement ends once the immediate issue has been contained or the agreed scope is reached. Further work requires separate discussion, onboarding, and written agreement. Information accessed during emergency work is treated as confidential by default; an NDA may be executed if required, but emergency work is not delayed for administrative reasons.
Request emergency support
If a system is down or unstable and no operational relationship exists, describe the situation briefly by email. If I am available and the situation fits emergency scope, next steps and terms are confirmed in writing.