
The short version:
When people say “WordPress,” they often mean two very different things. One is an open-source content management system you control. The other is a hosted site-building service designed for convenience. They share a name, but they lead to very different outcomes.
WordPress as Software (wordpress.org)
WordPress, as found on wordpress.org, is open-source software and a global development community.
This is WordPress as a platform. It means:
- You control where the site is hosted
- You control how it’s structured
- You own your content and custom development
- You’re not locked into a single vendor or pricing model
This version of WordPress is meant to be shaped. It assumes professional judgment, discipline, and ongoing care.
This is the WordPress we work with—and the foundation for everything else in this series.
WordPress as a Service (wordpress.com)
WordPress.com is a hosted website platform built on top of WordPress. It prioritizes:
- Speed to launch
- Convenience
- Bundled hosting, themes, and features
- Tiered plans and predefined limits
For some use cases, that tradeoff makes sense. But it’s important to understand that WordPress.com behaves much more like other site builders: easier to start, harder to shape.
Control is exchanged for simplicity.
Why the Distinction Matters
The confusion isn’t academic—it’s practical.
When someone says: “We use WordPress,” they could mean:
- A fully custom site built on open-source WordPress
or - A hosted service with structural and functional constraints
Those two sites may look similar on the surface, but they behave very differently when it comes to:
- Custom development
- Integrations
- Performance tuning
- Long-term flexibility
- Ownership and portability
Control vs. Convenience
At its core, this distinction mirrors a theme you’ll see throughout this series.
- WordPress.org favors control and long-term flexibility
- WordPress.com favors convenience and speed
Neither is “wrong.” But they are built for different priorities.
Organizations that need custom structure, integrations, and long-term stability almost always outgrow convenience platforms. Organizations with simple needs may never need to leave them.
The key is choosing deliberately.
How This Connects
This difference underpins everything else we’ve written about:
- Using WordPress as a platform, not a shortcut
- Why structure comes before convenience
- Why plugins, updates, and governance matter
- Why ownership and portability aren’t abstract concerns
Understanding which “WordPress” you’re using clarifies all of it.
Our Opinion:
Most frustration around WordPress doesn’t come from the platform itself—it comes from realizing too late that convenience and control were never the same thing.
- Why We Use WordPress—and How We Make It Work
- Using WordPress as a Platform, Not a Shortcut
- Plugins, Updates, and Why WordPress Sites Break
- WordPress.org vs. WordPress.com: Same Name, Very Different Tools
- WordPress: What It Is, What It Isn’t, and Why That Matters
- WordPress: Why Structure Comes Before Convenience
Our WordPress Series
- Why We Use WordPress—and How We Make It Work
- Using WordPress as a Platform, Not a Shortcut
- Plugins, Updates, and Why WordPress Sites Break
- WordPress.org vs. WordPress.com: Same Name, Very Different Tools
- WordPress: What It Is, What It Isn’t, and Why That Matters
- WordPress: Why Structure Comes Before Convenience
Trademark Notice: WordPress®, the WordPress logo, and related marks are trademarks of the WordPress Foundation. Their use on this site is for informational purposes only and does not imply endorsement, sponsorship, or partnership.

