WordPress infrastructure: what to document and maintain
A WordPress site depends on more than its theme. Document the services that keep it available, the people who maintain them and the recovery steps if one fails. Market-size forecasts do not establish whether your own setup is reliable.
Map the dependencies
Record the hosting account, domain registration, DNS, web server, database, file storage, email delivery and external integrations. Identify who controls each account and how authorized staff recover access. Keep credentials in a controlled credential store, not this inventory.
Plan maintenance and recovery
Assign responsibility for operating-system, WordPress, plugin and theme updates. Back up both the database and files, retain a separate recovery copy and test restoration away from production. Check whether external services need their own export or recovery procedure.
Measure your own service
Monitor availability and representative user journeys, such as sign-in and checkout. Record response times, capacity limits and failed background tasks. Use those observations to plan changes. The earlier article's unfinished market figure and unsupported forecasts have been removed; they are not evidence for a hosting decision.