Paid services are in preparation. Online payment and server jobs are not open yet. Check a PHP version free or email [email protected] about your setup. Prices below describe the planned services.
PHP checks and patching across your server fleet.
Review PHP installations across client servers, plan the changes and keep track of hosts that still need attention. Get volume pricing and a rollout matched to your environments.
Technical sources reviewed
Find which PHP needs attention.
Agencies and hosting teams can have several PHP versions on one machine, different packages across customers and applications that cannot move together. Start with the servers you control and the PHP used by their websites, background workers and containers.
Send a count and a short description of the environments. Identify who can authorize access and downtime for each customer. Keep passwords, private keys and detailed customer inventories out of the public request form.
- Inventory and assessment
- Scan checks the PHP installations it can inspect, package patch status, running workers and signs of compromise. The report keeps unknown or unavailable checks visible.
- Supported PHP2Shell patching
- Patch adds the update and restart work for accepted PHP 8.2 to 8.5 environments. Review older or unusual setups before including them in the rollout.
- Old applications
- Sites that need compatibility work follow the Upgrade service. Those projects are priced per site rather than per server.
Agree the order and checks before changes.
Review the inventory
Group servers by operating system, PHP package source and application needs. Confirm access and which platforms fit the accepted service scope.
Agree a first server
Choose a representative server and an approved window. Establish application checks and recovery before changing it.
Review before continuing
Review the first server's update, restart and application checks before proceeding. Keep failed or unresolved hosts separate from completed hosts.
Hand over the fleet report
Use a combined report to review host findings, changes and outstanding tasks. Agree remaining actions and remove temporary access when the job is complete.
Containers and Kubernetes workloads may need changes to images and deployment configuration rather than a package update on the host. Include them in the request so their rollout can be reviewed and quoted correctly.
Prices follow the number of servers.
A server is one machine, virtual machine or container host running PHP, regardless of the number of sites it serves. Site upgrades are quoted separately. All prices below are in US dollars per server.
| Servers | Scan | Patch | Care / year |
|---|---|---|---|
| 1 to 4 | $99 | $249 | $490 |
| 5 to 24 | $79 | $199 | $390 |
| 25 to 99 | $59 | $159 | $290 |
| 100+ | From $39 | From $129 | Quote |
Example: five servers on the Patch plan cost 5 × $199 = $995 before any priority-start add-on or applicable tax.
Scan is credited toward a Patch within 14 days. Confirm the credit for the same servers and show any combined discount in the quote. Care is an annual plan with the PHP2Shell Patch included, not a monthly price.
Online checkout is not currently open. Scan, Patch and Care retain the planned volume prices shown here. Fleet inquiries and all groups of 100 or more need a confirmed quote before any future order. The from prices for larger fleets are starting points, not a fixed checkout total.
Separate patching from application changes.
Fleet delivery is not open yet. The planned Priority add-on is $250 per server, with availability and schedule to be confirmed before ordering opens. A rollout needs a supported setup and approval for each maintenance window.
Care includes PHP security fixes, a monthly scan and compromise sweep. Application feature work, framework migrations and database changes need a separate scope when they are not part of an accepted upgrade.
PHP2Shell fixes can arrive as vendor backports under older version numbers. The fleet assessment needs each server's package source and running PHP processes. A single website's response header cannot establish the status of every server behind it.
Technical context: PHP's security release guidance and Ubuntu's fixed package notice. See PHP2Shell patching for fixed upstream releases.
Fleet questions
Is pricing per website or per server?
Scan, Patch and Care use server counts. Upgrade starts per site because compatibility work belongs to each application. Tell us both counts when several sites share a server.
Can you assess first and patch later?
Yes. Start with Scan, then review the required changes. The Scan fee is credited toward a Patch within 14 days for the same server.
What happens when a host cannot be checked?
Its unresolved status stays visible. We review missing access or unsupported arrangements before treating it as patched. The next action may require you, your host or a separate quoted job.
What should an agency include in its request?
Give server and site counts, PHP and operating-system details if known, hosting or control panels, approval contacts and maintenance windows. We arrange secure inventory and access after the initial request.