Platforms
WordPress.com vs. WordPress.org: choose the hosting arrangement
Compare hosting, plugins, maintenance, support, and total cost using the current WordPress.com plan rules.
WordPress.com is a hosted service. WordPress.org is the home of the open-source WordPress software, which you can run with a hosting provider of your choice. Both can power a serious business website. The practical decision is which hosting arrangement, permissions, support, and recurring costs suit your site.
Do not decide using the old shorthand that one allows plugins and the other does not. WordPress.com’s current documentation says plugins can be installed on all its paid plans. The exact plan features still matter, especially for backups, staging, developer access, and commerce.
What you are actually buying
| Question | WordPress.com | WordPress with another host |
|---|---|---|
| Where does the website run? | On WordPress.com’s hosting service | On the hosting provider you select |
| Who defines the hosting features? | The chosen WordPress.com plan | Your host and plan, plus any services you add |
| Can the site use plugins? | Yes on paid plans, subject to compatibility and service restrictions | Generally yes, subject to host restrictions and compatibility |
| Who handles a problem? | WordPress.com support within its service scope | Your host, developer, or plugin vendor depending on the problem |
| How much maintenance do you do? | Depends on the plan and site features | Depends on how much your hosting and maintenance contracts cover |
The official WordPress.com comparison explains the hosting distinction. WordPress.org’s software features page describes the publishing, theme, and plugin system. Neither page establishes that every third-party hosting plan offers the same support or resources.
Plugins are no longer the simple dividing line
According to the current WordPress.com plugin guide, Personal, Premium, Business, and Commerce support plugin installation. Its guide lists staging, SFTP/SSH, database access, and automated site backups with one-click restore among Business features. Check the specific capability your project needs rather than assuming a plugin-enabled plan includes every developer tool.
Before paying, send the host a short list of essential plugins and workflows. A booking system, membership plugin, custom integration, or unusual deployment process may matter more than the number of available themes. Ask about compatibility and who investigates conflicts after an update.
Self-hosted does not have to mean self-managed
You can choose managed WordPress hosting from a third-party provider. That provider may handle server maintenance, backups, caching, and selected WordPress tasks. You still need to establish the boundary: a host maintaining the server may not fix a broken custom checkout or update every paid plugin license.
For an owner who does not want technical work, compare the actual managed services on both sides. For a developer, compare access and restrictions. The domain ending in the provider’s name is less useful than a written answer about how the site will be operated.
Compare a complete annual budget
The WordPress software download being free does not make an operating website free. Include hosting, domain renewal, paid themes or plugins, transactional email, backups, and maintenance work. On WordPress.com, inspect what the plan already includes so you do not buy a duplicate service.
Use the standard renewal and a realistic billing term. A low introductory host price with paid backups and a separate maintenance contract may cost more than an apparently expensive bundle. A bundle containing tools you never use may be poor value too.
For an illustrative comparison, a $120 annual host plus $100 of licenses and $180 of maintenance costs $400 before the domain. Compare that $400 with the hosted-service quote, rather than comparing the quote with the $120 hosting line alone. These figures demonstrate the method; they are not current provider prices.
Which arrangement fits your next year?
- A straightforward business site: prioritize a manageable editor, the required forms, reliable recovery, and someone accountable for support.
- A custom application or complex integration: prioritize the necessary access, deployment workflow, and compatibility.
- A publication or newsletter: compare subscriber tools, email delivery, fees, and export options alongside the website.
- A client site: ensure the client controls the domain, billing, and recovery access, with appropriate delegated access for the builder.
Build a short acceptance list before choosing: publish a page, submit a form, recover a backup, add a collaborator, and explain how the site could leave. Ask the provider which parts are included and which require another product.
Moving later is possible, but content export and a complete site migration are different scopes. Preserve media, URLs, plugin data, and required licenses when planning an exit. Our WordPress migration service guide helps turn that work into a clear brief.