Skepra / Web recovery & resilience

Start with a focused recovery review.

Clarify the situation, decision points and a proposed next route before recovery work is agreed.

Request a recovery review

Price and boundary

Recovery Review — €50 fixed (pilot). Included: high-level situation review and a short written next-route summary. Not included: repair, emergency response commitment, credentials channel, technical access, or a guaranteed outcome. The price stays fixed because the scope is deliberately bounded to this one output—it is not a market average and not a first instalment of a larger, undisclosed fee. If further work may be suitable, its scope, responsibilities and fixed quote are agreed in writing before work begins.

When this route fits

Use this route when a business-critical website is disrupted, appears compromised, cannot be restored with confidence, or has become too unclear to make the next decision safely. It is not a route for sending credentials or asking for an automatic repair.

Why review and repair are priced separately

Some website-recovery providers bundle diagnosis and repair into one upfront fee, so a repair commitment is implied before the situation has been reviewed. Skepra keeps the two steps separate: the €50 Recovery Review covers only the situation review and a written next-route summary. Repair or other work, if suitable, gets its own written scope, price and acceptance—nothing is assumed from the review alone.

What to share first

Share high-level business context: what changed, what users or the business are experiencing, and what decision is blocked. Do not send credentials, secrets, payment data, database dumps or full logs at this stage.

What happens in a review

The review clarifies whether a focused route is suitable, what needs to be decided first, and which responsibilities need to be explicit. It ends with a short written summary of the proposed next route, not an implied commitment to technical work.

The gate before work

If a recovery sprint is proposed, its intended outcome, scope, price, communication boundary and responsibilities are accepted in writing first. No chargeable recovery work is assumed from the request alone.

Frequently asked questions

What happens during a website recovery review?

The review clarifies whether a focused route is suitable, what needs to be decided first, and which responsibilities need to be explicit. It ends with a short written summary of the proposed next route, not an implied commitment to technical work.

What should I share first when requesting a recovery review?

Share high-level business context: what changed, what users or the business are experiencing, and what decision is blocked. Do not send credentials, secrets, payment data, database dumps or full logs at this stage.