Software Reverse Engineering Services

For systems you own, and for interoperability, maintenance and security purposes, it is routine and lawful in most jurisdictions. We ask for confirmation that you own the system or are licensed to analyse it before starting, and we decline work aimed at circumventing licensing or copying someone else's product.

The original source, rarely. A working, documented equivalent, usually yes — through binary analysis and behavioural tracing. For most clients that is the real goal anyway: something maintainable, not the exact original file.

In stages. The first is a fixed-fee investigation that answers a specific question and tells you what the next stage is worth. You get a decision point with real information at the end of each one rather than an open meter.

Yes — that is one of our most common jobs. We observe the traffic, map the protocol, document the endpoints and build you a client with the edge cases and failure modes written down.

Often not, or at least not all at once. Rewrites overrun because the old system's undocumented behaviour is the requirement nobody captured. We map it first, then recommend maintain, bridge or replace — with the cost of each.

Always, before anything is shared. This work involves your most sensitive systems and we treat it that way.