Software and a service
WordPress is open-source publishing software. WordPress.org is the website for the project and its resources: it provides the software, themes, plugins and documentation, among other things. WordPress.com is a hosting service operated by Automattic that uses WordPress. The two names are similar, but they do not refer to the same thing.
Imagine a notebook and a printing company. The first represents the tool you use to prepare your content; the second represents a range of services that help make it available. This comparison is imperfect, but it helps separate the software from the commercial offering.
Who handles what?
With an installation at a hosting provider of your choice, you decide on the site’s environment within the limits of your contract. That does not necessarily mean administering a server: managed hosting can take care of some tasks. On WordPress.com, the available options depend on your plan. Check its current terms before deciding.
For your project, make a list of responsibilities rather than an abstract comparison between freedom and simplicity. A plan that works comfortably for a personal journal may be insufficient for a site with complex forms.
- Identify who makes backups and who restores the site.
- Ask who steps in if there is an outage or a problematic update.
- Check the features you need: domain, plugins, storage and support.
Plan for the real cost
WordPress is open-source software, but a website often involves paid services. Hosting, a domain name, support or additional tools may all form part of the budget. Do not compare introductory prices alone: examine the period covered, renewal and what you will actually need.
We recommend a small personal table with three columns: essential today, potentially useful later, unnecessary. For a recipe blog, publishing, organizing and illustrating posts may be enough at launch. There is no need to choose a plan for a hypothetical shop.
Avoid two shortcuts
A website whose address ends in your own domain can be hosted on WordPress.com. The site’s public appearance is therefore not always enough to identify its hosting provider. To find out, check the management account or invoice rather than deducing an answer from the design.
Another pitfall is thinking that open-source software eliminates all technical constraints. For an independent installation, compare the hosting offering against the official WordPress requirements, particularly HTTPS and supported versions of PHP and the database. Avoid building your project on components that have already been abandoned.
Validate your choice before committing
A good outcome is a choice you can explain in one sentence: “This solution covers my current needs, and I know who maintains the site.” If several responsibilities remain unclear, ask questions before paying.
Also ask for clarification on how to retrieve your content and media. A future change of hosting provider is easier to prepare for when the exit arrangements are known from the start. No model works for everyone: your available time and need for guidance matter as much as the technical options.
- Write down three features you really need at launch.
- Confirm their availability in the plan you are considering.
- Keep a record of renewal costs and the responsibilities agreed upon.
Sources and documentation
Differences between WordPress.org and WordPress.comAbout the WordPress projectWordPress technical requirementsAI-assisted translation. Labels may vary depending on your version of WordPress.
