Start with the work your team needs to do
A content management system (CMS) is the place where your team creates, edits and publishes website content. In a hosted CMS, the provider generally runs the software and its underlying infrastructure. In a self-hosted CMS, your team chooses where to run the software and takes more responsibility for its operation. The boundary is not always neat: a hosting company may manage parts of a self-hosted setup, while a hosted service may still leave content structure and site settings to you.
Before comparing products, map a typical publishing week. Who drafts articles, who approves them, and who can change a page after publication? Do you need scheduled posts, reusable page layouts, media libraries or different permissions for editors? A CMS that makes those routine tasks clear is often a better fit than one with an impressive feature list your team will rarely use.
What a hosted CMS takes off your plate
A hosted CMS usually bundles the editing interface with hosting, software updates and some operational support. That can be appealing when a small team has no one available to maintain servers or troubleshoot software. Editors may be able to start with a template, set up their content types and spend most of their time publishing rather than managing the system.
Convenience has boundaries. Providers differ in how much you can customize templates, add features or connect other tools. Pricing may also change with the number of users, sites, features or content items. Look at the plan your team would actually need, not only the entry-level price. Ask who can change the site’s design, what support covers, and what happens if you need a feature the service does not provide.
Keep the website’s domain registration and key account access under the organization’s control, even if a freelancer sets up the CMS. Use individual accounts where possible so that a departing team member does not take the only login with them.
What self-hosting gives you—and asks of you
A self-hosted CMS can offer more choice over hosting, themes, extensions and custom development. It may suit a team with unusual content structures or integrations that a hosted service cannot accommodate. Having access to the software and its files can also make some kinds of migration easier, though moving a site is rarely effortless.
That flexibility creates ongoing jobs. Someone must plan updates, check that extensions still work, manage backups, monitor access and know how to restore the site when something breaks. Paying a host or developer to handle those tasks can be sensible, but the responsibilities should be explicit. A backup is most useful when the team knows where it is stored, who can access it and whether a restore has been tested.
Avoid treating the software’s price as the full cost. Add hosting, paid extensions, development help and staff time to the comparison. A system that is inexpensive to install but hard for editors to use may consume more time with every publication.
Check portability before you build a library
Your content may outlive your choice of CMS. Before committing, find out how to export articles, page text, images and metadata such as titles and descriptions. Check whether the export preserves useful structure or produces files that would need substantial cleanup. Consider what would happen to internal links, image descriptions and redirects if you changed platforms.
Run a small trial with real material: one standard article, one complex page and a few images. Publish them, revise them, then try to export them. This reveals practical limits that a feature checklist may miss. It also gives editors a chance to notice friction, such as confusing preview controls or too many steps to correct a typo.
Make the decision as a team
Choose hosted when its available layouts and features meet your needs and reducing technical upkeep matters most. Consider self-hosted when you need greater control and have a reliable person or provider to maintain it. Neither choice guarantees a good website: clear content responsibilities, accessible templates and a sustainable review process matter in both.
Make a short decision sheet with the tasks that must work on day one, the person responsible for maintenance and an estimated budget for ongoing work. Test the leading options with the people who will publish, not only the person who will set them up. The right CMS is one your team can use confidently now and maintain as the site grows.
