Skip to content

Product engineering

Software rescue and stabilisation

Software rescue is taking over a system from a previous supplier or departed team, making it safe to run and change, and then improving it. Hexploits starts every rescue with a stabilisation phase: documentation, verified backups, access review, monitoring and a test harness, before any change is made.

A named engineer replies within one working day. A written scope and an indicative price within two.

  • Businesses whose supplier has gone quiet, gone bust or moved on.
  • IT directors inheriting a system with no documentation and a single point of failure.
  • Companies where every deployment is a gamble.

Deliverables, not slogans. Each one appears in the statement of work.

  • A stabilisation report within two weeks: what exists, what is at risk, what must happen first.
  • Verified backups and a tested restore.
  • Access review: named accounts, rotated credentials, least privilege.
  • Monitoring and alerting where there was none.
  • A test harness and a release pipeline, so change becomes routine.

Our engineers work across the major languages, frameworks and cloud platforms. We build on the stack you already run, with technology choices explained in writing before work begins.

The same four stages as every Hexploits engagement, applied to this capability.

  1. Stage 1

    Secure

    Credentials, backups and access first. Nothing else matters if these are wrong.

  2. Stage 2

    Document

    Architecture, dependencies, runbooks and known issues, written down and kept current.

  3. Stage 3

    Stabilise

    Tests, pipeline, monitoring. Releases stop being events.

  4. Stage 4

    Improve

    Only now do we change what the system does, on a managed support contract with a change allowance.

Every engagement agrees its measures and the measurement period in writing before work starts.

  • Restore tested and timed.
  • Incidents per month, before and after stabilisation.
  • Time to ship a change, before and after (Gradvisor: three weeks to two days).

Case studies with numbers, and reviews linked to Google where they were left there.

  • Director, Gradvisor

    Fantastic company and our development partner for Gradvisor, a social mobility careers platform with national ambitions. Extremely responsive and mission-oriented. Cameron owns any shortfalls humbly - rare for IT providers. Thinks like a client too.

    Tushar PrabhuDirector, GradvisorRead the review
  • Director, Lothbury

    Top quality delivery, and reasonable price. Will be using again.

    Peter DentonDirector, LothburyRead the review
What do you need from us to start?
Access to the code, the hosting accounts and whoever knows the most about the system, plus the contract with the previous supplier so we know what you own.
Will you tell us to rebuild it?
Only if the assessment shows it is cheaper than keeping it, and we will show the working. Most rescues stabilise and modernise incrementally.
How quickly can you take over?
Stabilisation starts within days of access being granted. The SLA starts once monitoring and backups are in place, usually within two weeks.

Sectors where this is most often needed

Request a proposal.

Tell us about the system and the sector. A named engineer replies within one working day. A written scope and an indicative price within two working days of a short scoping call.