Automattic Alternatives

Last spring a photographer handed me a WordPress.com site she had outgrown. She was on a Premium plan, the site looked lovely, and she wanted three things: a mailing list signup that didn't look bolted on, a proper portfolio gallery, and to install one specific plugin for client proofing. Two of those three were unavailable on her plan. The plugin — the one thing her business actually needed — required stepping up two tiers to Business. Her annual bill was about to go from comfortable to "I should just learn to code," and she asked me the question this article is built around: when does it make sense to leave the WordPress.com ecosystem entirely?

I'm talking about Automattic here — the company behind WordPress.com, WooCommerce, Jetpack, and a chunk of the commercial WordPress economy. WordPress.com is not WordPress the open-source software; it is Automattic's hosted, managed, plan-gated version of it, and that distinction is the root of almost every reason people leave. On WordPress.org you install any plugin you like on any host you like. On WordPress.com you are inside a product with tiers, and your freedom scales with your invoice. That can still be a great deal — I'll get to that — but let's start with the exits.

When it makes sense to leave Automattic (WordPress.com)

The plan gates are the real price list. At time of writing, WordPress.com sells Free, Personal, Premium, Business, and Commerce plans. The lower tiers are inexpensive — Personal and Premium sit in the single-digit dollars per month on annual billing — but the feature boundaries are sharp: plugin installation and full theme customization are tied to the higher tiers, and Business and Commerce cost considerably more, roughly in the $25–$50/month range billed annually at time of writing (verify current figures at wordpress.com/pricing; these numbers move). My photographer's story is the common one: the site grows up, needs one capability, and the cheapest path to it is a plan jump that costs more per month than a competent self-hosted setup.

Renewal and auto-renew dynamics. WordPress.com bills annually and auto-renews at the then-current rate per their terms of service. That means two things: you are committing for a year at a time, and the rate you renew at is whatever Automattic charges when your term ends, not the rate you signed up at. WordPress.com doesn't play the extreme first-year-discount game that shared hosts do, which is honest of them, but list prices have risen over the years. Check what the renewal rate is today before you model a three-year cost.

Platform policy is not your policy. Automattic governs the platform and makes changes that land on your site whether or not you like them: feature reorganizations, editorial-adjacent decisions, branding shifts. There was also a very public conflict in late 2024 between Automattic and WP Engine over WordPress trademark interpretation and the broader commercial ecosystem, which shook confidence for some site owners in how stable the ground beneath the WordPress economy is. I'm not taking sides in that dispute — I'm noting that if your business runs on a platform, platform politics is business risk.

Commerce economics on lower plans. If you sell anything on a lower-tier WordPress.com plan, check the transaction fee situation at time of writing — store payments on cheaper plans can carry a platform cut that Commerce removes. A couple of percentage points on every sale is a real number once you have volume.

The branding and identity limits. On the cheapest plans you carry WordPress.com branding and limited design control. Fine for a personal blog; if the site is your storefront, your brand is renting space from someone else's.

Export is possible but not lossless. WordPress.com lets you export content, and the WordPress importer will bring posts, pages, and comments across. What doesn't travel: paid features, your theme setup, some block-based layouts, Jetpack-dependent functionality, and anything built around WordPress.com's own services. Plan on a rebuild of the design layer even in a good migration.

A practical test I use. Before recommending anyone leave, I ask them to write down the three capabilities their site needs in the next twelve months. If those three things are available on their current WordPress.com plan, leaving is usually motion without progress — you absorb migration cost, design risk, and a learning curve to arrive at feature parity. If one of the three is gated behind two plan tiers, or isn't available on WordPress.com at all, the move starts to pay for itself within a year. The photographer above had client proofing as her non-negotiable, and no WordPress.com tier shipped it properly. That single fact made the decision for her.

When you should stay

Stay if you want WordPress without operating WordPress. Automattic handles hosting, caching, CDN, security patching, backups, and uptime, and the platform is genuinely fast for what it is. If your site is a publication, a portfolio, or a small business presence and you have no interest in server admin, that convenience is worth paying for.

Stay on the free and cheap tiers if they fit. A Free WordPress.com site is still one of the best no-cost ways to put writing online, and Personal/Premium are fair value for a blog with a custom domain — the annual plans typically include a domain, which cancels out part of the cost comparison.

Stay if you are deep in the ecosystem deliberately: Jetpack features, WordPress.com's stats, built-in newsletter tooling, WooCommerce via the Commerce plan with the hosting worries abstracted away. Automattic's commerce offering is a legitimate way to run a store without hiring anyone.

Stay if what spooked you was pricing that turns out to be competitive anyway. Run the real comparison before moving: a self-hosted WordPress stack with decent managed hosting, backups, CDN, and a caching layer often costs the same or more once you price your own time. I've talked clients out of leaving because the maths didn't actually support the move.

The alternatives

These six are the ones I'd genuinely put in front of someone leaving WordPress.com. I've grouped them by the kind of leaver they suit, with pricing as I could verify it at time of writing.

Squarespace — for design-led businesses who want everything in one box

Squarespace is the polished all-in-one: templates that look designed, commerce built in, domains, email, and analytics under one login. At time of writing the entry website plan lands in the mid-teens per month on annual billing, with commerce tiers above that. The upgrade over WordPress.com is coherence — nothing looks bolted on because everything ships together. The downgrade is portability: Squarespace is its own closed platform, and leaving it later means another rebuild. Choose it the way you'd choose a well-fitted suit: for how it looks and works now, not for exit options.

Webflow — for designers who want real control without a server

Webflow gives you visual design control that genuinely approaches hand-coded CSS, hosting on a fast global CDN, and CMS collections for structured content. Webflow simplified its site plans in 2026 — at time of writing, site plans start around $15/month billed annually for basic sites and higher for CMS-heavy ones, with workspace seats billed separately for teams. It's the choice I make when the client cares intensely about design fidelity and doesn't want a developer on retainer. It is also the steepest learning curve of anything on this list — plan for that.

Wix eCommerce — for store owners who want selling features without plugins

Wix eCommerce handles online stores with native features: product galleries, abandoned cart recovery, POS, and an app market when you need more. At time of writing the entry commerce tier runs roughly $29/month billed annually, stepping up through the higher plans for more features and staff accounts. Where it beats a plan-gated WordPress.com is that the commerce tooling at each tier is clearly labelled and broadly included. Where it loses is template lock-in — change your design seriously and you can find yourself rebuilding page by page.

10Web — for people who want actual WordPress, AI-assisted, with managed hosting

10Web takes a different route out: it gives you a real WordPress site on managed Google Cloud hosting, plus an AI builder that generates pages and content you can then edit normally. Pricing is per site per month at time of writing. This is the right exit if the reason you were on WordPress.com is that you wanted WordPress — the open kind, with any plugin you like — but you didn't want to manage a server. You get the plugin freedom that WordPress.com's lower tiers deny you, with the hosting handled.

HubSpot CMS (Free) — for marketing sites tied to a CRM

HubSpot CMS (Free) hosts a website at no cost and wires it directly into HubSpot's CRM, forms, and contact tracking. At time of writing the free CMS tier is genuinely free and the paid Marketing Hub tiers add the automation and analytics. If your website exists to feed a sales pipeline — and you're already living in a CRM workflow — this combination makes more sense than any generic builder. If you just want a pretty site, it's more platform than you need.

Format — for photographers and creatives who want a portfolio first

Format is a portfolio platform: proofing galleries, client workflow tools, and themes built around images rather than text. Monthly pricing by plan at time of writing. It is deliberately narrow and that is the appeal — my photographer client ended up in exactly this category, because the thing she needed wasn't "WordPress with plugins" but "a portfolio that handles client proofing properly." A platform built for your craft beats a generalist with an app store.

How to switch without downtime

Leaving a site builder is not like changing hosting — there is no cPanel backup you can restore elsewhere. But the no-downtime discipline is the same, and it's all about DNS timing.

Export what can be exported. WordPress.com provides a WXR (WordPress eXtended RSS) export tool in the dashboard: export your full content file before you do anything else. On pure builders, look for content export, blog export, or at minimum crawl the site and save every page's text and images. Assume the design layer won't come with you.

Rebuild the new site on a temporary URL first. Every platform on the list above gives you an unpublished staging environment or a staging subdomain. Recreate the important pages, import your content, and rebuild navigation. This is the laborious part and it cannot be shortcut — budget for it honestly rather than pretending a tool will map everything.

Set up redirects before you flip anything. If URLs will change (they usually do), write a redirect map from every old URL to its new destination. Do this while the old site is still live so you can verify every row. Losing search rankings because of forgotten 301s is the classic builder-migration injury, and it's entirely preventable.

Lower DNS TTL 48 hours before the switch. Drop the A/CNAME record TTL to 300 seconds ahead of time so propagation is minutes rather than a day.

Point the domain at the new platform and watch. Change the single record that routes web traffic. Leave the old subscription active for a week — do not cancel it the moment the new site looks right. Test forms, check analytics are receiving data, and click your redirect map in anger.

Then cancel, and take stock of the side services. Cancel the old plan after a clean week. But before you do, audit what else was attached to it: domain registration, domain-linked email, any paid mailbox, newsletter tooling, DNS records for third-party services. In my experience, the forgotten mailbox is what actually breaks a week after the migration feels finished.

One more option worth naming: staying in the family but off the platform

If the objection is the plan gating rather than WordPress itself, there is a middle path worth pricing out: keep WordPress (the open-source software) and move to any managed WordPress host that installs it for you. You keep every plugin and theme you want, lose Automattic's all-in-one convenience, and often pay less than a Business plan for more freedom. This is the route I take when the client is comfortable with WordPress but not with servers. The alternatives listed above are for people who want to leave the WordPress model; this one is for people who only want to leave the landlord.

How we evaluate hosting providers

We evaluate on what you pay over the life of the product, not what the first invoice advertises. That means recording the introductory rate, the renewal rate, and the gap between them — Automattic's WordPress.com is relatively straightforward here (no deep teaser discounts, but auto-renewal at prevailing rates), while much of the shared hosting industry renews at two to three times the signup price. We also weigh what's gated versus included at the tier you'll actually buy — WordPress.com's plan boundaries being a textbook case — plus support access, resource honesty, and exit costs (how hard is it to leave?). We say "at time of writing" when a figure can shift, cite where it came from, and treat hidden renewal pricing as a finding in itself.