Overview
Nathan Wrigley talks with Michelle Frechette and Jonathan Desrosiers on the Jukebox podcast about how wordpress.com and wordpress.org came to be, how they differ, and how they work together within the WordPress ecosystem.
Origins and history
WordPress started in 2003 when Matt Mullenweg and Mike Little forked b2. From the beginning it was open source software released under the GPL, freely downloadable, modifiable, and runnable by anyone. In 2005 Matt founded Automattic, which launched wordpress.com as a managed hosting service offering free blogs (yourname.wordpress.com) and paid plans with added features. WordPress.com helped popularize WordPress by making publishing simple at scale while wordpress.org remained the home of the open source project.
What each site represents
– wordpress.org: This is the distribution and community site for the open source WordPress software. You download or install it on your own server (many hosts offer one‑click installers). It’s the self‑hosted option that gives you full control over plugins, themes, server settings, and code.
– wordpress.com: A hosted service run by Automattic that uses the WordPress codebase. It provides free and paid tiers, handling hosting, security, and updates for you. Free plans are limited in customization; paid plans progressively unlock more functionality and can approach feature parity with many self‑hosted setups, while higher tiers add enterprise and e-commerce services.
Why the split matters
The separation reflects historical norms and practical needs. Traditionally, .org signaled community-driven or nonprofit projects while .com indicated commercial services. WordPress.org embodies the open source project and community; wordpress.com is a business-built platform that makes publishing easy and sustainable.
Key impacts:
– Accessibility: wordpress.com lowered the technical barrier to publishing long before hosting and installation were easy for everyone, enabling more people to get online.
– Portability: WordPress emphasizes content ownership and exportability, allowing users to move their sites—an advantage over many closed platforms.
Community and perception
The WordPress ecosystem includes volunteer contributors who work through .org channels (plugins, themes, documentation, meetups, WordCamps) and users/customers on wordpress.com. Because many active contributors come from the self‑hosted side, public perception can skew toward .org values.
Tension sometimes appears between open source purists and commercial interests, but they often overlap. Companies that earn revenue from WordPress frequently contribute back in code, sponsorship, documentation, and community work. Initiatives like Five for the Future encourage organizations to dedicate time to the project.
Contributions are broader than code: support, translations, event organization, and funding are all vital to the project’s health.
Features, user experience, and convergence
– Limits and freedom: Free wordpress.com plans restrict plugins, themes, and custom CSS. Self‑hosted WordPress offers unrestricted access to plugins, themes, and server-level tweaks. Paid wordpress.com plans gradually restore much of that flexibility.
– Scale and architecture: WordPress.com runs as a large WordPress multisite instance—millions of sites on a single infrastructure—an impressive engineering achievement that provides insight into real-world usage patterns.
– Dashboard and tools: WordPress.com developed Calypso, a distinct dashboard experience, and over time there has been movement to align dashboards and tooling between the two platforms. Converging experiences reduces duplicated effort, simplifies migration, and helps deliver consistent features across the ecosystem.
Practical guidance
– Choose based on needs: Use free wordpress.com for fast, low-risk publishing; pick paid wordpress.com plans if you want a managed experience with fewer technical responsibilities; choose self‑hosted (.org) when you need maximum control, custom code, or specific plugins.
– Account for real costs: The software is free, but running a self‑hosted site incurs hosting, maintenance, security, and possible development costs. Think of wordpress.org as “free software with operational responsibilities.”
– Value ownership and portability: WordPress’s export and migration tools make it easy to move content, which is important for long‑term control and resilience.
– Get involved: Contributing—through code, docs, support, translations, or events—keeps the ecosystem strong. Contributions come in many forms and all help the project grow.
Final perspectives
Michelle stresses that .org and .com are complementary rather than adversarial: each serves different audiences. Free wordpress.com broadens access to publishing, while self‑hosted wordpress.org underpins the contributor community that builds the project. Jonathan notes that understanding these options is a continuum rather than a binary choice—clear explanations help more people pick the right path and participate in the broader web.
Summary
WordPress has a dual identity: wordpress.org is the open source software project offering total control, and wordpress.com is a managed service that makes publishing simple. Both grew from early project decisions and practical needs and now feed into the same ecosystem. Choose the route that matches your goals, mindful of costs, responsibilities, and the strong migration and ownership advantages WordPress provides.