WordPress

Self-hosted WordPress reviewed for non-technical founders who want ownership without platform lock-in.

TL;DR

• What it is: Open-source (GPL) content management system — the software behind blogs, business sites, portfolios, and stores for roughly 43% of all websites on the internet [1].
• Who it’s for: Founders, bloggers, and small business owners who want complete control over their website without sharing revenue with a platform, plus developers who want unlimited extensibility through plugins and themes [1][2].
• Cost savings: WordPress.com’s Creator plan runs $25/mo; its Entrepreneur plan (with full WooCommerce and plugins) runs $45/mo. Self-hosted WordPress on a $5–10/mo VPS with shared hosting costs a fraction of that with zero restrictions [1].
• Key strength: 60,000+ plugins and unlimited themes. If you need a store, a membership site, a booking system, or a job board — there’s a plugin for it. No other self-hosted CMS comes close on raw extensibility [1][2].
• Key weakness: You own the maintenance. Updates, backups, security patches, and plugin conflicts land on you (or your hosting provider). It’s a real ongoing cost that platforms like WordPress.com, Squarespace, and Wix absorb [2][4].

---

What is WordPress

WordPress is the software you download from WordPress.org, install on a web host, and run yourself. The name covers two very different things that regularly confuse newcomers: WordPress.org (the free, self-hosted open-source platform) and WordPress.com (the managed SaaS version run by Automattic). They run the same core software, but the experience, cost structure, and control you get are completely different [2].

WordPress.org started in 2003 when Matt Mullenweg and Mike Little forked a blogging platform called b2/cafelog. What started as “an elegant personal publishing system” grew into a CMS that now runs rolling stones at Rolling Stone, NASA’s public-facing sites, TechCrunch, Harvard university pages, Microsoft blogs, and Time Magazine — all listed as showcase examples on the WordPress homepage [website]. The GitHub mirror has 20,959 stars, though the real development activity happens on WordPress’s own Subversion infrastructure at core.trac.wordpress.org [GitHub profile].

The license is GPL (General Public License), which means you can modify it, redistribute it, run it commercially, and build products on top of it. The merged profile lists the license field as “NOASSERTION” due to how the repository is structured (it’s a Git mirror of a Subversion repo), but the actual WordPress license is and always has been GPL v2 or later [website].

What makes WordPress different from competitors isn’t the core software — it’s the plugin and theme economy. The official WordPress.org repository alone has over 60,000 free plugins. Third-party premium marketplaces (ThemeForest, EDD, etc.) add thousands more. There is effectively nothing you cannot build with WordPress if you’re willing to pay for or find the right plugin.

---

Why people choose it (and what they’re escaping)

The pattern across all four reviews is consistent: people come to self-hosted WordPress because a hosted platform stopped working for them — usually because of restrictions on what they could post, embed, or monetize.

Escaping Blogger. One direct-experience review [4] describes moving from Blogger to self-hosted WordPress because “Blogger just wasn’t cutting it” once blogging became serious. The specific friction: you can’t embed certain tools (like Rafflecopter for giveaways), you live with the risk of platform shutdown if a post is flagged as inappropriate, and you have no real ownership of your content. The apartment-vs-renting analogy from that review is apt: with Blogger, your host can kick you out because it’s their server. With self-hosted WordPress, you’re the tenant with a contract [4].

Escaping WordPress.com restrictions. This is the most common upgrade path. WordPress.com’s free tier gives you a yourname.wordpress.com subdomain, a restricted plugin list, and WordPress branding in your footer. To get a custom domain, remove ads, and access plugins, you pay — and the plans that actually compete with self-hosted WordPress (Creator and above) run $25–45/mo [2]. The Clarity DX review [2] puts it directly: “Over time, these costs can add up and it may be cheaper overall to use self hosted WordPress.”

Owning your data. Multiple sources cite content ownership as a core reason. With WordPress.com, “your site is not truly yours. You are essentially renting space on the WordPress.com platform. If WordPress.com changes its terms or features, or restricts what is available, you have little recourse” [2]. Self-hosted WordPress means you hold the database, the files, and the hosting relationship. The platform can’t pull the rug on you.

Monetization freedom. On WordPress.com’s lower tiers, you can’t run your own ads, affiliate links, or WooCommerce stores without upgrading. Self-hosted has zero revenue-sharing restrictions from day one [1][4].

The honest counterpoint that none of the reviews sidestep: this freedom comes with maintenance responsibility. Backups, updates, security monitoring, and plugin conflict debugging are real work. A Quora contributor [3] frames it cleanly: WordPress.com is like “renting” and WordPress.org is like “owning your home.” Homeownership is better for most purposes, but it requires showing up when the pipes leak.

---

Features

Core CMS:

• Block editor (Gutenberg) — drag-and-drop page building with native block types for text, images, video, columns, accordions, and more [website]
• Full site editing — theme templates editable from the same block interface [website]
• Custom post types, taxonomies, menus, widgets [website]
• User roles (admin, editor, author, contributor, subscriber) with granular permissions [website]
• Built-in comment system, media library, post scheduling [website]
• Multisite — run multiple sites from a single WordPress installation [website]
• REST API for headless/decoupled setups [primary docs]

Extensibility (the actual differentiator):

• 60,000+ free plugins in the official repository covering SEO (Yoast, RankMath), security (Wordfence, Sucuri), backups (UpdraftPlus), performance (WP Rocket, W3 Total Cache), WooCommerce for eCommerce, membership systems, LMS platforms, booking engines, and anything else you can name [1][2]
• Theme system: thousands of free and premium themes controlling site visual design
• Child themes and direct PHP/CSS access for developers who want to go beyond the UI [1][2]
• WooCommerce — the dominant open-source eCommerce platform, now owned by Automattic — installs as a plugin and turns any WordPress site into a store

Headless/modern usage:

• WordPress REST API and WPGraphQL enable it as a headless CMS with a React/Next.js frontend [merged profile subcategory: headless-cms]
• Active development on the Gutenberg block framework continues pushing it toward a more modern editor experience [website]

What the block editor still doesn’t do well:

• Complex page layouts that require multiple sidebars, grid systems, or advanced interactions still often need a dedicated page builder plugin (Elementor, Bricks, Oxygen) on top
• The block editor’s learning curve is real for non-technical users who’ve never used a CMS

---

Pricing: SaaS vs self-hosted math

WordPress.com (their managed SaaS):

• Free: WordPress.com subdomain, no plugins, WordPress ads on your site
• Starter: ~$9/mo — custom domain, no ads, limited themes
• Explorer: ~$18/mo — some premium themes
• Creator: ~$25/mo — unlimited plugins, Jetpack features
• Entrepreneur: ~$45/mo — full WooCommerce, premium extensions
• Enterprise: custom pricing

The Entrepreneur plan is the first one that gives you the full self-hosted-equivalent feature set (plugins + WooCommerce). At $45/mo that’s $540/year [website pricing — primary source].

Self-hosted (WordPress.org):

• Software: $0 (GPL)
• Shared hosting (Namecheap, Hostinger, SiteGround): $3–10/mo
• VPS if you want better performance and more control: $5–20/mo
• Domain: $10–15/year
• Security and backup plugins: free options available (Wordfence free tier, UpdraftPlus free tier)
• Total realistic entry cost: $5–15/mo plus one-time setup time [1]

Concrete comparison:

A small business running a WordPress site with a store, a contact form, SEO tools, and a security plugin:

• WordPress.com Entrepreneur: $45/mo = $540/year
• Self-hosted on shared hosting: $8/mo hosting + $15/yr domain = $111/year
• Self-hosted on a $6 Hetzner VPS: $6/mo + domain = $87/year

Savings at the Entrepreneur-equivalent tier: roughly $430–$450/year [1][2]. The caveat is that shared hosting at $3/mo has real limitations — you’re on a congested server, performance suffers under traffic, and support is limited. A proper managed WordPress host (Kinsta, WP Engine) runs $30–100/mo and starts to close that gap. That’s a legitimate use case, but it’s not the self-hosted story.

---

Deployment reality check

The WordPress README’s boast is “Famous 5-minute install” — and for managed hosts with one-click installers (Bluehost, Namecheap, SiteGround), that’s accurate. You click “Install WordPress,” pick a domain, set an admin password, and you’re in the dashboard [README].

What you actually need for a clean self-hosted setup:

• PHP 7.4+ (8.3 recommended) [README]
• MySQL 5.5.5+ or MariaDB 10.6+ [README]
• Apache with mod_rewrite, or nginx [README]
• HTTPS (SSL certificate — free via Let’s Encrypt on any modern host) [README]
• A web hosting account or a VPS with the above installed

For a VPS install (more control, more work):

• A Linux VPS (Ubuntu/Debian recommended)
• Web server stack: nginx or Apache + PHP-FPM + MySQL/MariaDB
• Certbot for SSL
• SMTP provider or plugin (WP Mail SMTP) for outgoing email
• Backup solution (UpdraftPlus to S3 or Google Drive)

The Quora reality check [3]: Multiple answerers push back on the idea that self-hosting is “extremely complicated and risky.” The consensus is: use a reputable host with WordPress-specific tooling, don’t try to run it on your home computer, and the install itself is genuinely straightforward. The complexity creeps in after launch — plugin conflicts, performance tuning, security hardening, and update management are where non-technical users hit walls.

Honest time estimate:

• Technical user on a managed host: 15–30 minutes to a working site
• Technical user on a fresh VPS: 2–4 hours including stack setup and hardening
• Non-technical founder following a guide on a managed host: 1–3 hours including theme selection and basic configuration
• Non-technical founder on a VPS: budget a full day or hire someone

What goes wrong:

• Plugin conflicts — install 40 plugins and eventually two will fight each other. This is the single most common support request in the WordPress community [3]
• PHP memory limit exhaustion on cheap shared hosting
• XML-RPC attacks and brute-force login attempts if you skip security basics (Wordfence, fail2ban, CAPTCHA on login) [3]
• Skipping backups, then discovering a plugin update broke the site with no rollback [1]
• Update fatigue — WordPress core, themes, and plugins all update independently. Ignoring updates for months creates security debt [2]

The Quora answer [3] from a WordPress core contributor frames the maintenance work honestly: “backup, security, keep it updated” — three things that are mostly automatable with free plugins, but require intentional setup.

---

Pros and cons

Pros

• Free and genuinely open source (GPL). The software costs nothing. The license lets you modify it, build products on it, and run it commercially without paying Automattic [2].
• Powers 43% of the internet. Talent pool for developers, designers, and support is massive. You’ll find a tutorial, a plugin, or a Stack Overflow answer for almost any problem [1].
• Plugin library is unmatched. No competing CMS has 60,000+ free plugins covering this range of functionality. WooCommerce alone makes WordPress the default for small-to-medium eCommerce [1][2].
• Full content and data ownership. Your database, your files, your hosting relationship. No platform can take it down, restrict your content, or change the rules mid-game [2][4].
• Unlimited monetization. Run whatever ads you want, affiliate links, paid content, subscriptions, stores. Zero revenue sharing with the platform [1][4].
• Scalable from blog to enterprise. The same software that runs a personal blog runs Fortune 500 marketing sites. Rolling Stone, NASA, and Harvard run WordPress [website].
• Headless-capable. REST API and WPGraphQL let you use WordPress as a content backend while building a modern React/Next.js frontend [merged profile].
• Massive hosting support. Every web host on earth supports WordPress. One-click installs, managed WordPress hosting, and Dockerized setups all exist [1][2].

Cons

• Maintenance is your problem. Updates, backups, security patches, plugin conflicts — none of that is handled for you on self-hosted. You either do it or pay someone [2][4].
• Plugin quality is inconsistent. Sixty thousand plugins range from excellent to abandoned-in-2017-and-full-of-security-holes. Vetting plugins takes real effort. The plugin count is not uniformly an asset [3].
• Performance requires work. Shared hosting WordPress sites are slow by default. Caching plugins (WP Rocket, W3 Total Cache), image optimization, and CDN setup are needed for production performance.
• Security is an ongoing battle. WordPress’s dominance makes it the most-attacked CMS. Brute force login attempts, plugin vulnerabilities, and XML-RPC exploits are routine. You need Wordfence or equivalent [3].
• The block editor (Gutenberg) is divisive. Introduced in 2018, it replaced the classic editor that millions of users knew. Users either adapt or install the Classic Editor plugin. For new users, the learning curve is real [website].
• Plugin dependency creep. A site with 40 active plugins has 40 potential failure points, 40 update notifications, and 40 incompatibility risks. This is a structural problem with WordPress’s extensibility model.
• Hosting costs add up if you want performance. Cheap shared hosting at $3/mo delivers cheap-shared-hosting performance. Managed WordPress hosting at Kinsta or WP Engine ($30–100/mo) reduces maintenance burden but closes the cost gap vs. WordPress.com.

---

Who should use this / who shouldn’t

Use self-hosted WordPress if:

• You’re building a content-heavy site (blog, news, magazine) and want to own it long-term without platform lock-in.
• You need WooCommerce for eCommerce and don’t want to pay Shopify 2.9% per transaction plus a monthly fee.
• You want unlimited plugin access without paying $45/mo for WordPress.com’s Entrepreneur tier.
• You or someone on your team can handle (or learn) the basics of WordPress maintenance, or you’re willing to pay a one-time setup fee.
• You need a custom theme, custom post types, or integration with third-party services via plugins.

Skip it (use WordPress.com) if:

• You need to publish a site today with zero technical setup and have a budget for managed hosting.
• Your team has no one who can handle plugin conflicts, updates, or a hacked site.
• You have fewer than 5 pages and no need for plugins or custom themes — WordPress.com’s Starter plan ($9/mo) covers basic use cases cleanly.

Skip it (use Ghost) if:

• You’re a writer or journalist who wants a clean, fast, distraction-free publishing platform. Ghost is purpose-built for content and has fewer moving parts [merged profile — alternative consideration].

Skip it (use Webflow) if:

• You’re a designer-first team that cares more about visual precision and animations than plugin breadth, and you’re comfortable with Webflow’s pricing ($23–49/mo) for the reduced maintenance overhead.

Skip it (use a static site generator like Astro or Next.js) if:

• You’re a developer who wants performance-first, content managed via Markdown or a headless CMS, with WordPress-level operational complexity eliminated entirely.

---

Alternatives worth considering

• Ghost — purpose-built blogging and newsletter platform. Cleaner writing experience, faster by default, simpler deployment. GPL licensed. Smaller plugin catalog. Better choice if content publication is your only use case.
• Strapi — open-source headless CMS for developers who want an API-first content backend. No built-in frontend; pairs with any frontend framework. Better suited for technical teams building custom apps.
• Directus — open-source data platform that doubles as a headless CMS. Wraps any existing SQL database with an admin UI. More flexible than Strapi for complex data schemas.
• Webflow — managed, no-code website builder with design-first tooling. Significantly better visual output for designers; no plugin conflicts; $23–49/mo with no self-hosting option.
• Squarespace / Wix — fully managed, simpler than WordPress.com, more template-driven. Fine for simple brochure sites. Not meaningfully self-hostable.
• Joomla / Drupal — older GPL CMS alternatives. Drupal is more powerful and more complex; Joomla sits between Drupal and WordPress on the complexity spectrum. Both have smaller communities than WordPress and less plugin breadth.

For a non-technical founder who just wants a website without monthly SaaS bills, the realistic shortlist is self-hosted WordPress vs. Ghost. Choose WordPress if you need the plugin ecosystem (WooCommerce, memberships, LMS, forms). Choose Ghost if you’re publishing content and want a simpler, faster system.

---

Bottom line

WordPress is not exciting to review in 2026 because it’s been the default answer for so long that people forget to question it. That inertia is partly justified: 43% of the internet runs it for real reasons — the plugin ecosystem has no equal, the hosting support is universal, and the GPL license means you truly own what you build [1][2]. The honest case for self-hosted WordPress over WordPress.com’s equivalent tiers is straightforward: you save $400+ per year and remove the platform’s ability to change the rules on you [1][2][4].

The honest case against it is equally real: WordPress trades platform fees for maintenance overhead. Plugin conflicts, security hardening, and update management are persistent costs. If your business has no technical capacity and no budget for a managed host, that overhead is not free — you pay it in time and stress instead of dollars [2][3].

For a non-technical founder weighing “SaaS convenience vs. self-hosted ownership,” WordPress is the mature, lowest-risk choice if you can get past the initial setup — either by learning it once, or paying someone to do it for you. That’s precisely the deployment service that unsubbed.co’s parent studio upready.dev offers. One-time setup, you own the infrastructure, the platform bill disappears.

---

Sources

1. CreativeThemes / Blocksy Blog — “Self-Hosted WordPress: Build a Site You Truly Own”. https://creativethemes.com/blocksy/blog/what-is-self-hosted-wordpress-pros-and-cons-setup/

2. Clarity DX WordPress Blog — “WordPress.com vs Self Hosted WordPress: What’s the Difference?” (Jul 10, 2025). https://claritydx.global/wordpress/wordpress-com-vs-self-hosted-wordpress-whats-the-difference/

3. Quora — “Self-hosting via WordPress.org seems extremely complicated and risky. Would I need a separate computer to house it?” (multiple answers including Mario Peshev, WordPress Core Contributor). https://www.quora.com/Self-hosting-via-WordPress-org-seems-extremely-complicated-and-risky-Would-I-need-a-separate-computer-to-house-it

4. Paging Serenity — “Thoughtful – The Pros and Cons of Self Hosted WordPress” (Emily, Apr 9, 2015). https://www.pagingserenity.com/thoughtful-the-pros-and-cons-of-self-hosted-wordpress/

Primary sources:

• Official website: https://wordpress.org
• GitHub mirror: https://github.com/wordpress/wordpress (20,959 stars)
• System requirements and installation documentation: https://wordpress.org/documentation/
• WordPress.com pricing: https://wordpress.com/pricing/