When this is useful
Situations that can start the work.
- The site failed after an update or migration.
- The project is abandoned and component ownership is unclear.
- There are signs of compromise or unstable operation.
Evidence / preflight
We first verify what is available.
- A file, database, and configuration checkpoint before intervention.
- Logs, versions, integrity, and the boundary of available investigation.
- A separate clean stage and a recovery scenario.
Deliverables
What remains with the owner.
- An evidence-based recovery plan and explicit unknowns.
- A verifiable recovered version or an honest stop condition.
- Migration notes, secret rotation, and rollback.
Honest boundary
What cannot be promised in advance.
Without forensic evidence, the exact incident cause or absence of persistence cannot be guaranteed. A specialist is involved when the scope requires one.
Tell us what the site needs.
A goal, the current difficulty, and an optional website address are enough. Do not send passwords, keys, or private exports.