Is self-hosted WordPress cheaper than WordPress VIP?
If your renewal is on the table, start from a fact that removes one line from the comparison: WordPress core is released under the GPLv2 or later, so the software license costs nothing on either side. What you are actually comparing is the platform and operating services that VIP bundles, against the staff time, infrastructure and vendor contracts you would take on yourself. Self-hosting usually costs less where your infrastructure bill is predictable and you no longer pay a platform fee for hosting, edge delivery and managed environments. It usually costs more where VIP was doing work your team now has to staff: applying security updates, running on-call rotations, reviewing code and plugin changes, configuring edge caching, and testing and restoring backups. Ask VIP for a written list of what its contract includes, then map each item to a named owner in your own organization.
Build the comparison line by line rather than as a single total. The recurring lines are hosting compute and database capacity, CDN and object storage for media, backup storage and retention, monitoring and log tooling, and people. The one-time lines are the migration project, the initial code review and any pipeline you build for deploys. Each recurring line moves for different reasons: traffic and media volume drive CDN and storage, plugin count and custom code drive review hours, and your uptime target drives how much on-call coverage you need. WordPress.org recommends PHP 8.3 or greater and MariaDB 10.11 or greater or MySQL 8.0 or greater, so confirm that your chosen hosting supports those versions, since a platform that lags behind will add upgrade work. Also note that automatic background updates cover minor releases and that plugins and themes are updated automatically only in special cases chosen by WordPress.org, so the rest of the patch cycle sits with you.
Which cost components change when you leave VIP
This table compares each cost line of WordPress VIP with what you or a partner pay for when running the same GPL WordPress code yourself. Read each row for what VIP supplies, what the self-hosted side needs, and whether the cost is one-time or recurring. The main takeaway is that the runtime baseline is the same on both sides, so most of the difference lies in who operates the platform and who carries the on-call and patching work.
| Cost component | What VIP supplies | What you or a partner pay for when self-hosted | One-time or recurring |
|---|---|---|---|
| Hosting and runtime | Managed container-based infrastructure for WordPress and Node.js applications, per WordPress VIP documentation | Compute, database and PHP runtime. WordPress.org recommends PHP 8.3 or greater and MariaDB 10.11 or greater or MySQL 8.0 or greater, so the baseline matches on both sides | Recurring |
| CDN and object storage | Edge caching and media handling as part of the platform fee | Separate CDN contract, media object storage and egress charges, plus configuration of cache rules and purge logic | Recurring |
| Backups and monitoring | Full database backups downloadable from the VIP Dashboard or with VIP-CLI | Backup tooling, off-site retention, restore testing, uptime and error monitoring, and the time to review alerts | Recurring, with one-time setup |
| Security patching | Platform-level patching and a managed release path | Staff or partner time to test and apply core, plugin and theme updates. WordPress only auto-updates plugins and themes in limited cases, so most of this work is manual | Recurring |
| Code review and deploys | A GitHub repository per application and VIP's deployment workflow | Git hosting, CI pipeline, review process and deployment tooling you build and maintain | One-time setup, recurring upkeep |
| On-call support | Platform support and incident handling covered by the contract | Internal on-call rota or a partner retainer, plus escalation paths for hosting and third-party plugins | Recurring |
| Plugin and theme licensing | Platform-managed plugins as part of the VIP offering; confirm which third-party tools are included | Plugin and theme costs are mostly free under GPL, but premium licenses, replacement tools and vendor support still carry fees | Mostly recurring |
| Migration | Export tooling and support during the exit period, as set out in your contract | Repository and database transfer, media move, DNS cutover, parallel run and rebuild of any VIP-only integrations | One-time |
What moves each cost line up or down
Six drivers set most of the difference between a VIP invoice and the cost of running WordPress yourself. Each one pushes hosting, CDN, object storage, backup and on-call costs in a different direction, so model them together rather than one at a time.
Traffic and peak load
Peak concurrent requests decide how much compute you must keep ready, and how much cache sits between visitors and PHP. Self-hosted, you pay the cloud provider for capacity and for CDN egress, so spiky editorial traffic can cost more than steady traffic of the same monthly total. Ask your VIP account team how peaks are priced and capped, then load test your own stack at the expected peak before you compare figures.
Media and data volume
Your image library, video files and database growth drive object storage, backup storage and transfer costs, and all of them recur every month. Self-hosted, you choose the storage class, retention and whether media is offloaded to S3-compatible storage. Confirm how much media and database history you must keep, since the VIP export gives you full database backups that must be stored somewhere you pay for.
Number of sites and multisite scope
Each separate site adds its own container capacity, backup jobs, monitoring targets and patch cycle when you run it yourself. A WordPress multisite network shares one codebase and database, which lowers per-site overhead but concentrates risk and load in one place. Ask how many sites, domains and languages are in scope, and whether shared plugins and themes can be patched once for all of them.
Availability and recovery targets
The stricter your uptime and recovery point expectations, the more you pay for redundant servers, replicated databases, tested restores and out-of-hours coverage. A site that can be offline overnight for a few hours costs far less to protect than one that must recover within minutes. Write down the outage tolerance and data loss tolerance for each site before you ask for quotes, because these two numbers determine most of the backup and on-call spend.
Premium plugins and custom code
Commercial plugins carry licence fees that renew each year, and custom code adds review, testing and maintenance work that VIP currently absorbs through its code review process. Plugins and themes are only auto-updated by WordPress when the WordPress.org API flags a critical fix, so you must schedule their updates yourself. Inventory every plugin with its licence terms and owner, and mark which ones have no open-source replacement.
In-house skills
Your team's ability to run PHP, MariaDB or MySQL, container platforms and WordPress security sets how much of the work you can absorb and how much you buy from a partner. Thin in-house skills shift cost toward retainers, on-call coverage and training, while strong skills mainly cost salary and tooling. Map who owns patching, incident response and deploys today, and ask any partner to state in writing which of those tasks they would take over.
Who patches WordPress when VIP no longer does
Once you leave VIP, the patch cadence for WordPress core, plugins and themes becomes your own operating job, and the labour to run it is a recurring cost line. WordPress core is updated by the project, but the project does not patch your server, your plugin set or your release process. The WordPress Security Team, which includes more than 50 trusted experts, fixes responsibly disclosed vulnerabilities in bugfix releases, and it backports critical fixes to older versions as a courtesy. That courtesy is not a support commitment. Only the latest version of WordPress is officially supported, so a site that falls behind carries risk the project does not formally cover.
Core automatic background updates date to WordPress 3.7, and sites created since WordPress 5.6 have automatic major release updates enabled by default. Plugin and theme updates are different. By default, WordPress applies them automatically only in special cases that the WordPress.org API selects, usually to patch critical vulnerabilities. Everything else, including ordinary plugin releases and the compatibility breaks they can cause, lands on your team. Under VIP, the platform and code review pipeline handled much of this testing. Confirm with your current VIP account team which of those gates you would have to rebuild, such as staging parity, automated tests and a release sign-off step.
WordPress 7.1 was released on August 19, 2026, and 7.1.3 followed on October 6, 2026. The WordPress releases archive states that only the most recent release in the 7.1 series is actively maintained, so each point release has to be applied promptly rather than deferred to a quarterly window. Illustratively, a critical fix that ships on a Tuesday needs a staging copy, a plugin compatibility check and a tested rollback path before it reaches production. Budget for that cycle as recurring labour, and ask any partner quoting the work to state who owns the on-call response when an update fails at night.
How to build the cost comparison with your own numbers
This sequence turns a vague sense that VIP is expensive into a three-year model built from your contract, your invoices and your own infrastructure and staffing quotes, so each cost line has a named owner and a source.
Pull the current VIP contract and invoices
Gather the signed agreement, every order form or amendment, and at least the last twelve months of invoices. Your procurement or finance lead owns this step. Read the contract for the fee basis, the renewal and notice terms, usage overage rules, and anything billed by traffic, storage or environments. Confirm with VIP account management what each invoice line covers. You are done when every recurring and variable charge on the invoices maps to a clause in the contract.
List every paid add-on
Enumerate each optional service you pay for on top of the base platform, such as extra environments, additional storage, support tiers, premium CDN or monitoring features, and professional services hours. Ask the VIP account team for a written list of add-ons and their unit rates. Record which add-ons your team actually uses, because unused add-ons are often the first lines to drop in a self-hosted model. You are done when the add-on list reconciles to the invoices with no unexplained lines.
Map each VIP-supplied service to an owner
Build a table with one row per service VIP provides: container hosting, edge caching and CDN, database operations, backups, code repository and deploy pipeline, security patching, uptime monitoring, and support. For each row, name who would own it after a move, whether that is your internal team, a hosting provider, or a partner. Mark rows that have no owner today. Ask your platform lead to review the table. You are done when every row has an owner or is flagged as an open decision.
Price your infrastructure from your own quotes
Request written quotes from your cloud provider or data center for compute, database, object storage for media, CDN, egress bandwidth, backup storage and monitoring tooling, sized to your measured traffic and media footprint. Ask each provider to state the pricing unit, reserved or committed discounts, and data transfer charges separately. Ask whether backup retention and object lifecycle rules are included. Your cloud or infrastructure lead owns this work. You are done when each infrastructure line has a quote, a pricing unit and a sizing assumption you can explain.
Estimate internal hours for patching, review and on-call
Estimate the recurring staff effort by role: a developer for plugin and theme updates and code review, an operations engineer for hosting, patching and backups, and a rotation for on-call coverage. Base the estimates on your own ticket history and the number of plugins and custom components you run. Note that WordPress core and plugin updates arrive through different channels, so your team must track both. Ask any partner for a rate card and a written scope for the same tasks. You are done when each role has an hours figure, a loaded hourly cost and a list of tasks behind it.
Add migration as a one-time cost
Separate the move itself from running costs. Itemize the one-time work: repository and database export, media transfer, environment build, configuration of caching and backups, staging validation, cutover, and any retraining of editors. Request a fixed-scope quote from a partner with deliverables and acceptance criteria written out, and ask your internal team to estimate its own time. Keep these lines out of the recurring totals so they do not inflate the run-rate. You are done when migration costs sit in their own block with a named source for each figure.
Run a three-year view with recurring and one-time lines separated
Build a spreadsheet with three annual columns. Put VIP fees and add-ons, self-hosted infrastructure, staffing, and tooling in recurring rows, and migration and initial setup in one-time rows. Include a comparison row for any price increase or renewal term in your VIP contract, and a row for your own licenses or support contracts. Your finance lead signs off on the structure, and your platform lead checks the technical assumptions. You are done when the model shows yearly totals for both operating models with one-time costs visible.
Test sensitivity on traffic and staffing
Rerun the model with higher and lower traffic, larger media libraries, more plugins, and different staffing levels. Traffic and storage drive CDN, egress and database sizing, while staffing drives patching and on-call effort, so change each variable one at a time and record the effect. Confirm which VIP charges move with usage and which are fixed. The check is complete when you can state which two or three inputs change the answer most and what evidence would move each one.
Common questions about WordPress VIP and self-hosting costs
What does self-hosting WordPress cost compared with WordPress VIP?
Self-hosting replaces one platform fee with several cost lines that you or a partner pay for directly: compute, database, CDN and object storage, backups, monitoring, security patching, code review and on-call support. Some of these are recurring infrastructure bills, while others are one-time (migration, pipeline setup, runbooks) or recurring labor (patching, on-call, plugin upkeep). The main cost drivers are traffic peaks, media volume, how many environments you run, and how much after-hours coverage you need. Ask for each line separately in any quote so you can compare the totals fairly.
How long does it take to move off WordPress VIP?
The duration depends on the size of the codebase, the number of custom plugins and themes, the media library, traffic patterns, and how many environments and integrations must be recreated. Your database export and repository are the starting point, and the VIP Dashboard or the VIP-CLI command export sql can produce the full database backup. Timelines should come from a written scope agreed before work starts, not from a general estimate. Ask the partner which of these factors they assessed and what they excluded.
Can an in-house team run self-hosted WordPress alone?
Some teams can, especially if they already operate PHP applications, managed databases and CDNs. The honest test is whether someone owns patching, backups and restore testing, monitoring, and an on-call rota for the site, not only whether the site can be deployed once. WordPress core releases are actively maintained only for the latest version, and you will need a process to apply them quickly. Many organizations split the work, keeping content and editorial support in house while contracting out platform operations and security testing.
What skills does self-hosted WordPress require?
Plan for PHP application operations, MariaDB or MySQL administration, container builds and deployment, CDN configuration and cache purging, object storage for media, and log and metric monitoring. WordPress.org recommends PHP 8.3 or greater and MariaDB 10.11 or greater or MySQL 8.0 or greater, so your team must keep those runtimes current. Ask any partner which of these skills they staff for the engagement and who holds the on-call responsibility after handover.
How should I compare self-hosting quotes from different partners?
Put every quote into the same cost components: one-time migration work, recurring infrastructure, recurring labor for patching and support, and any licensed tools. Check whether each quote includes staging, backups tested by restore, edge caching, monitoring, and handover documentation. A low figure can hide an exclusion such as custom plugin rework or post-launch support. Ask each vendor to state assumptions about traffic, media size and environments so the numbers match.
Do plugin licenses change when I leave WordPress VIP?
WordPress is released under GPLv2 or later, and the WordPress project treats plugins and themes as derivative works that must also be GPL, so the core code remains free to run on your own infrastructure. Premium plugins and themes sold by third parties have their own license terms, which you must review, because some vendors tie usage to a site count or a hosting provider. Make an inventory of every plugin and theme, its license, and whether VIP supplied it or your team installed it, before you request a quote.
What should I ask a partner to confirm in writing?
Ask for a written scope listing deliverables, environments, the migration method, the backup and restore test plan, the monitoring and on-call model, and the security patching cadence for WordPress core, plugins and themes. Request the exclusions, the acceptance criteria, and who owns the infrastructure accounts at the end of the engagement. DeployOpen agrees scope, deliverables and timelines in writing before work starts, and it prepares systems and evidence for compliance assessments but does not issue audit reports or certifications. Ask any partner for the same clarity.
One-time migration costs and how to scope them
The one-time cost of leaving WordPress VIP is set by a short list of work items, and the size of each depends on your site's footprint more than on the destination. Start with the database export. VIP customers can download a full database backup from the VIP Dashboard or run vip @app export sql with the VIP-CLI, according to the WordPress VIP documentation. Ask the vendor or partner to confirm which environments and backup points you can export, and how large the dump is for your site. Table count, serialized options, custom tables and the volume of revisions drive the time spent cleaning and validating the import on the new database, which must meet the versions WordPress.org recommends (PHP 8.3 or greater and MariaDB 10.11 or greater, or MySQL 8.0 or greater).
The repository and media work is usually the next largest item. VIP supplies a GitHub repository for every application, so the code itself is already versioned, but you still need to confirm which mu-plugins, VIP-specific configuration and platform helpers are in use. Each one that depends on VIP's platform must be replaced or removed. Media is a separate task: uploads are not in the database dump, so ask how they will be copied to object storage, how URLs will be rewritten, and who checks for broken references. Caching and CDN rules that VIP handled at the edge also need to be recreated and tested against your own traffic patterns, not assumed to match.
Backups, monitoring and cutover testing are the items most often underpriced. A fixed-scope quote should name the backup schedule and restore test, the monitoring and alerting stack, the patch process for core, plugins and themes, and a written cutover plan with a rollback step and a parallel-run window. Request the test cases used to sign off on the cutover, including editorial workflows, forms, search and scheduled publishing. Also ask who owns DNS changes and who is on call during the switch. Each of these items should appear as a separate line in the scope so you can see what is one-time and what moves into recurring operations.
How DeployOpen scopes a fixed-price WordPress move
DeployOpen plans, implements, hardens, backs up and documents self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For a WordPress VIP cost comparison, we start from a written scope that separates what VIP does for you today from what your team would need to run, so the figures you compare are based on your environment.
How we scope
- Inventory the VIP plugins, edge caching rules, media volume and integrations your site depends on today
- Agree in writing which hosting, CDN, object storage, backup and monitoring components are in and out of scope
- Map who would patch WordPress core, plugins and themes, and who reviews code before each deploy
- Confirm your PHP and MariaDB or MySQL versions against the WordPress requirements before any build starts
- Ask for a quote that follows directly from the written scope, with recurring and one-time items listed separately
How we build
- Stand up the hosting, database, object storage and CDN in your accounts or data center using agreed configuration
- Rebuild the VIP-managed behavior you rely on, such as caching rules and media handling, and document each setting
- Set up a Git repository, code review and deploy path to replace the VIP workflow your team uses
- Test the site, plugins and themes against the target stack and record the results
- Configure automatic updates and patch routines that match the WordPress Security Team's update model
How we hand over
- Deliver runbooks for hosting, backup and restore, patching, monitoring and incident response
- Document the cost components in your environment so your team can track recurring spend over time
- Run a restore test from backups and record the result as evidence for your own assessments
- Train your operations and editorial staff on the new deploy and rollback process
- Provide evidence and configuration records to your independent auditors, who issue any audit reports
How we support
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts
- Ongoing support, upgrades and continuous security testing are available as retainers
- Retainers can cover WordPress core upgrades, plugin reviews and backup verification on a set schedule
- Ask us to confirm which on-call hours and response terms the retainer includes before you sign
- Security testing of the site and its APIs can be scoped separately from the platform build
