WordPress.com plan ladder: $4 sounds great until you need a store or hosting tools
The WordPress.com funnel is well-designed. Personal at $4/mo (billed yearly) gets you a custom domain, plugin installs, and removes Automattic's ads — legitimate pain points solved at a price that feels cheap. The cost climbs when you try to do anything beyond a plain blog. SFTP/SSH, Git deployments, and real-time backups? Business, $25/mo. WooCommerce for digital products? Commerce, $45/mo. A newsletter with real capability? MailPoet for 500 subscribers comes with Business, and anything larger means another tool on top. Each individual upgrade is reasonable. The cumulative effect of two upgrades — $4 to $25 to $45 — plus plugin licenses is a year-one cost that surprises most users who expected to pay less than a typical CMS subscription.
Why Automattic's commercial play struggles against modern all-in-one platforms
WordPress's architecture was designed in an era when "add functionality via plugins" was the right answer. The plugin ecosystem is genuinely impressive — 60,000+ plugins, a massive developer community, decades of accumulated tooling. WordPress.com packages that ecosystem with managed hosting and Automattic's infrastructure investment. The architectural problem Automattic cannot solve is that plugin architecture introduces maintenance complexity by design: each plugin is a separate codebase, a separate update cycle, a separate security surface, and a potential conflict with every other plugin in the stack. A modern all-in-one platform like VeloCMS sidesteps that entirely by building newsletter, commerce, and AI natively. There are no plugins to install, no conflicts to debug, and no annual licence renewals.
When managed WordPress is right (and when it's just inertia)
The honest case for WordPress.com is managed infrastructure. Automattic has decades of experience running WordPress at scale, and the managed hosting layer — backups, security patches, global CDN, DDoS mitigation — is genuinely good. For organisations that have already invested years in the WordPress ecosystem (custom themes, bespoke plugins, editorial workflows built around WordPress), migrating to a different architecture is expensive and risky. The case for staying that is worth scrutinising is inertia — choosing WordPress.com because "we've always used WordPress" rather than because the plugin ecosystem is genuinely necessary. A creator starting fresh in 2026, with no existing WordPress codebase, no custom plugins, and no team of WordPress developers, is probably not the user WordPress.com's $25–45/mo tiers are designed for.