Classify before executing
Generate a manifest, hashes, material type, missing parts, credential findings, risk flags, and a customer next action from a non-executing quarantine copy.
Existing-site intake
First find out what you actually have. Then decide what can be recovered.
Site Intake accepts two customer routes: SOURCE / BACKUP and an authorized URL. A deterministic inspection separates a workable WordPress project from an incomplete deployment artifact, missing database, risky package, or front-end-only reconstruction.
The public pilot form never accepts archives or credentials. Controlled upload is opened only after manual fit and privacy review.
Reconstruct what the browser can see
Recover public structure, styles, assets, and visible interactions into maintainable front-end or WordPress work—without claiming hidden PHP, database, or admin logic was recovered.
A build artifact is evidence, not source
If the package contains only compiled or deployed output, stop and request source, database, a complete backup, or an authorized URL before choosing rebuild or rejection.
What happens next
A visible path, with a stop at every meaningful decision.
- 01
Confirm authority
Record that the customer owns the site or is authorized to process it. Public availability alone is not authorization to copy.
- 02
Inventory safely
Inspect size, archive paths, hashes, file types, WordPress markers, database material, credentials, and risky content without running unknown code.
- 03
Report recoverability
State what can be continued, migrated, reconstructed, or only used as reference—and list the exact missing materials.
- 04
Choose the route
Proceed to source continuation, backup restoration, authorized-URL reconstruction, a manual rebuild, or Stop. The customer approves the next scope.
Included in this route
- Material manifest, classification, risk flags, and missing-material report
- SOURCE/BACKUP and authorized-URL routes may be combined
- Clear distinction between original source, restored WordPress, and approximate front-end reconstruction
- Customer-facing next action and Stop condition
- Original material retained separately from working copies according to the agreed policy
Not assumed or promised
- Execution of unknown archives or plugins during intake
- Recovery of hidden PHP, database, admin, API, or scheduled-job behavior from a public page alone
- A promise to recreate the original Git history or uncompiled source from minified assets
- Bypassing logins, paywalls, CAPTCHA, robots restrictions, licenses, or third-party ownership
Limited private pilot
Bring the source, the backup, or the authorized URL—not a guess.
Start with a plain-language description and public URL if available. We will confirm the controlled material route only after the project fits the current pilot.