01 / INVENTORY
Know what runs where
Runtime, hosting model, application or WordPress dependencies, public exposure, and accountable owner.
PHP SECURITY UPDATE / RECOVERY PLANNING
Patch fast.
Keep a way back.
Critical PHP fixes are out. Plain Ops Lab turns your runtime, hosting, backups, compatibility risks, and rollback conditions into a written plan before production changes.
No unauthorized scanning or exploit testing. We work only on systems you own or are authorized to manage.
WHY NOW
Updating is urgent. Recovery still needs evidence.
PHP recommends immediate updates for installations serving web requests. A rushed production change without an inventory, restore path, or critical-path checks can create a second outage. We prepare the decision and the recovery path together.
02 / RECOVERY
Know how to return
Backup source, restore method, decision owner, rollback trigger, and change window.
03 / EVIDENCE
Know what passed
Login, checkout, forms, uploads, email, background jobs, and integrations before and after the change.
SCOPE
A written execution record, from update decision to recovery.
Production changes happen only after authority, scope, backups, and rollback conditions are confirmed.
Environment inventory
PHP version, vendor package, hosting method, owner, dependencies, and exposure.
Compatibility plan
Critical journeys, plugins or frameworks, extensions, custom code, and vendor guidance.
Backup and rollback design
Restore source, decision threshold, responsible owner, and monitored signals.
Executive decision brief
One page separating confirmed facts, unknowns, conditions, and the next decision.
PROOF & PRODUCT
Review the deliverable, or keep the decision kit in-house.
The fictional WordPress sample shows our process. The USD 99 local-first kit lets your team record six release gates, acceptance checks, and rollback conditions in its own browser. Neither is presented as a customer case study.
PLANS
Choose the depth your change needs.
USD starting prices. Tax treatment and payment method are confirmed in the written quote. Extra environments, after-hours work, and substantial custom-code repair are separate.
A / 2 BUSINESS DAYS
PHP Runtime Mismatch Fix
$390
One site, one runtime mismatch- Verify PHP seen by the app and host
- Check domain and directory handlers
- Confirm recoverable backup conditions
- Correct a safe configuration mismatch
- Custom-code repair is separate
View the fictional diagnostic record
Request mismatch fixB / 3 BUSINESS DAYS
Patch & Rollback Plan
$890
One environment- Runtime and dependency inventory
- Backup and restore checklist
- Compatibility and test plan
- Update and rollback steps
- No production change
C / ONE SPRINT
Guided Remediation Sprint
$2,200
One environment, one update sprint- Everything in B
- Staging update and evidence
- Approved production support
- Seven days of first-line triage
- No change without backup and authority
BEFORE YOU ASK
Clear answers before access or payment.
The first inquiry needs only non-sensitive facts. We use scope, authority, recovery conditions, and timing to decide what can be quoted safely.
SCOPE
What does USD 390 cover?
One site's PHP-version mismatch, with a safe configuration correction only when recovery conditions are confirmed. Custom-code repair is quoted separately.
PRICE
Can the listed price change?
The starting price applies to the listed scope. Extra environments, after-hours work, and substantial custom-code repair receive a separate written quote before work.
ACCESS
Should I email a password?
No. The first review uses non-sensitive information. After written scope, we agree on a least-privilege access method for the contracted work.
RECOVERY
Can you work without staging?
Plan A proceeds only when a recoverable backup and a low-risk configuration change are confirmed. Plans B/C stop until safe test and rollback conditions exist.
TIMING
When do two business days start?
The next business day after scope, authority, recovery conditions, required access, and written terms are complete. Extra discovery is stated before the start.
RESULT
Is a fix guaranteed?
No. Delivery separates verified facts, unknowns, changes made, stop conditions, and the next decision. Unknown custom-code repair is never silently included.
PROCESS
Scope the work before sharing sensitive access.
Non-sensitive intake
Environment count, authority, known version, and target date.
Written scope
Deliverables, exclusions, stop conditions, price, and payment method.
Secure access method
Credentials and secrets are never requested through public forms or email.
Evidence-backed delivery
Confirmed results, unknowns, performed work, and next decisions stay separate.
Check readiness, then prepare a non-sensitive request.
Both tools run in your browser. They do not scan a site or transmit your answers automatically.