Website maintenance plans differ less in name than in what they actually do: how often updates and backups run, how long backups are kept, what is monitored, and whether time for small changes is included. Compare plans by these items, not by their names. Hosting is a separate cost.
What maintenance covers
- Updates: the platform, themes, and plugins, with a check after updating.
- Backups: copies of the files and the database, kept somewhere other than the website itself.
- Monitoring: whether the site is up and whether the SSL certificate is valid.
- Security updates: applied when they are released, not only on a monthly cycle.
- Support: help with problems related to the plan's work.
WordPress documentation describes a complete backup as two parts: the database and the files. It notes that the database usually can't be backed up by downloading the site's folder, and recommends keeping several recent backups in different places. It also recommends backing up before you update.
What changes the price
- Number of sites: each site usually needs its own plan.
- Platform: plans are often designed for one platform; other platforms may need a custom quote.
- Included time: whether the plan includes hours for content updates or small fixes.
- Backup frequency and retention: daily or weekly, and how many days of backups are kept.
- Reporting: whether you receive a monthly report of the work done.
What a plan usually does not include
- New features, new page designs, or a redesign
- Emergency or out-of-hours work, unless the plan says so
- Hosting, the domain, and paid licenses, which you pay directly
Why the platform version matters
Websites also depend on the software they run on, such as PHP. PHP.net explains that each version receives active support, then security fixes only, and after its end of life no updates at all, so sites on an old version can be exposed to unpatched security issues. Part of maintenance is noticing when that time is coming. See PHP end of life.
Doing it yourself or using a plan
A small site with few plugins can be maintained in-house if someone has the time and a routine: updates, a backup before each change, a check after, and a way to restore. A plan makes sense when nobody owns that routine, or when a problem would cost more than the plan. See DIY maintenance vs. a plan for a closer comparison.
Questions to compare plans
- How often are updates done, and are security updates applied sooner?
- Is a backup made before every update? How long are backups kept, and where?
- What is monitored, and when are alerts reviewed?
- Is there included time, and does unused time carry over?
- What happens when you cancel? Do you receive current access details and information about backups?
How DEXVANE plans work
DEXVANE website maintenance & support plans cover WordPress sites: monthly updates of WordPress, themes, and plugins with a check after updating and rollback of problems caused by an update, security updates as needed, daily backups, uptime and SSL monitoring, and support for plan work during business hours. Plus includes time for small changes and a monthly report. See plans.
Sources
- WordPress Developer Resources, Backups (accessed October 4, 2026)
- WordPress.org Documentation, Updating WordPress (accessed October 4, 2026)
- PHP.net, Supported versions (accessed October 4, 2026)