Neleto vs WordPress: What You Give Up, and What You Stop Maintaining

Most "WordPress alternative" posts are written by people who need WordPress to look bad. WordPress runs a huge share of the web for good reasons, and leaving it costs you things you currently take for granted. So this post asks a narrower question: which sites are paying WordPress's maintenance bill without getting WordPress's benefits?

What are Neleto and WordPress, in one sentence each?

WordPress is a free, open-source PHP CMS that you extend with plugins from an ecosystem of tens of thousands, installed and maintained by you or your agency.

Neleto is an all-in-one CMS with a Rust backend. Rendering, hosting, the page builder, image scaling, redirects, translations, events and a native MCP server are built in, and it runs as managed hosting in EU regions.

The usual third option is a headless CMS, which stores content while you build and host a separate frontend application. Neleto renders the site itself, so there's no second stack to staff. We wrote about that trade-off in full CMS vs headless.

Should you leave WordPress at all?

For a large share of sites, no. If WordPress is working, keep it. Switching CMS is a real project with real risk, and "the architecture is more elegant" doesn't pay for it. WordPress stops being the right answer for a specific profile:

• A content and marketing site (pages, blog, events, files) with no e-commerce and no plugin-based business logic.
• Nobody in-house is a WordPress developer, so every plugin conflict becomes an outside invoice.
• Maintenance hours or retainer fees cost more than the site gains from being on WordPress specifically.
• You want an agent workflow (Claude Code, Cursor, Windsurf) against the CMS without building and maintaining the glue.

If two or more of these describe you, keep reading. If none do, stay where you are.

What do you give up by leaving WordPress?

Three things, and none of them are small.

The first is the plugin ecosystem. For most feature requests, a plugin already exists. If your business depends on WooCommerce, a specific booking or membership plugin, or a niche integration with your industry's scheduling system, leaving WordPress means rebuilding or replacing that. It's a real cost, and often the whole reason to stay.

The second is the people. WordPress has the largest pool of people who can work on a website, at every price point and in every country. Any freelancer can pick it up, and if your web person leaves, finding a replacement is easy. No smaller CMS matches that, Neleto included.

The third is themes. Thousands of ready-made themes mean a site can look finished on day one for a small fee. Elsewhere, you're designing, although AI design tools plus an MCP server have made that much cheaper than it used to be. We argued in Templates Are Dead that starting from your own idea now beats starting from someone else's theme. WordPress is also the safe institutional choice. Nobody gets criticised for picking it.

What do you stop maintaining?

Mostly, the update treadmill. On WordPress, core, themes and every installed plugin update on their own schedules, and each update has a small chance of breaking the site. On managed Neleto the platform updates underneath you, and what you maintain is your own content and layouts.

A few related jobs go away with it:

• Plugin conflicts. Two plugins work fine alone and stop working together after one ships a release. Diagnosing that is billable time that produces nothing new.
• Performance work that compensates for the architecture. Caching plugins, object caches, CDN tuning and image optimisation plugins mostly exist to undo the cost of assembling each page from PHP and a plugin stack at request time.
• The "who updated this and broke it" problem. With several people and automatic updates, the answer is often unclear.

None of this makes WordPress bad. It makes WordPress a system with an operating cost. That's fine if someone is budgeted to pay it and expensive if nobody is.

Is WordPress insecure?

WordPress core isn't the weak point. Plugins are, and the data on that is consistent. Patchstack's State of WordPress Security in 2026 report, covering 2025, counted 11,334 new vulnerabilities in the WordPress ecosystem, 42% more than the year before. 91% were in plugins, 9% in themes, and WordPress core had six, all low priority.

Two more numbers from the same report matter for anyone who maintains a site once a month:

• 46% of those vulnerabilities had no patch available when they were disclosed. Updating promptly doesn't help if there's nothing to update to yet.
• For heavily targeted vulnerabilities, the weighted median time from disclosure to first exploitation was five hours. About half of the high-impact ones were exploited within 24 hours.

So your exposure grows with the number of plugins you run and how fast each one gets patched. A lean, promptly updated install is fine. A site with 30 plugins, three of them abandoned, is a different risk, and a monthly maintenance visit can't keep up with a five-hour exploitation window.

There's also the layer underneath. WordPress runs on PHP, and on October 20 the PHP security team announced two critical CVEs (CVSS 9.2) affecting every PHP version since 5.0. A WordPress site with zero plugins still needed that interpreter patch, because the bug sat in the runtime and not in anything the site owner installed. Neleto's backend is compiled Rust, so there was no PHP interpreter on our serving path to patch.

We're not claiming Neleto can't have security bugs. Our claim is narrower. Features that would be plugins elsewhere live in one codebase that we patch centrally, and there's no shared interpreter underneath it, so the third-party surface is smaller by design.

What is built in, and what needs a plugin?

WordPress can do all of this. The difference is what you install, license and maintain to get there.

One limitation on the Neleto side: the built-in content types are what you get. Arbitrary user-defined types aren't shipped yet, and WordPress's custom post types are more flexible today.

What does each one cost?

WordPress software is free and stays free. You pay for everything around it: hosting, plugin licences and maintenance hours.

Hosting runs from a few euros a month on shared hosting up to managed WordPress plans. WP Engine's entry Startup plan is listed from $30/month billed annually (list price when we wrote this). Plugin licences are recurring and usually per site. WP Rocket lists at $59/year for one site, and premium SEO, multilingual and backup plugins are priced separately. Maintenance hours are usually the largest line and the one nobody budgets, whether they come out of your evenings or an agency retainer.

Neleto isn't free above the Free plan either. Solo is €19/month (€190 a year on annual billing) and Business is €39/month, with hosting, updates and the built-in features included. Comparing €19 against €0 misses the point. Compare it against hosting plus licences plus the hours.

If you self-host on cheap hosting and do the updates yourself without counting your time, WordPress is cheaper in cash and more expensive in hours.

When to stay on WordPress

In four situations, switching is the wrong call.

You depend on WooCommerce. Neleto has no e-commerce, so if your store is your business, that ends the discussion.

You have deep plugin investment: a booking system, a membership tier, a CRM integration, a directory, anything where a plugin holds business logic rather than content. Content migrates well. Functionality that lives in plugins doesn't.

You have an in-house WordPress team. You already pay the maintenance cost as salary, and you have the expertise that makes WordPress fast to work with. Switching throws that away.

It's a hobby blog. A lean self-hosted install or WordPress.com's free tier is fine. Don't pay €19/month for a site with no revenue attached.

How much work is migrating?

Neleto imports WordPress's standard export file (WXR), so pages, posts and media come across without retyping.

The import doesn't bring plugin-dependent features with it. If your site is content plus a contact form, migration is an import followed by a layout rebuild, and the rebuild is where most of the time goes, because a WordPress theme and a Neleto layout are different things. If your site has a booking flow, a members area or a shop, plan it as a project, not an afternoon.

Plan redirects separately. Keeping your existing URLs alive protects the rankings you already have. Our 40-page WordPress migration walkthrough covers the import, the redirect map and the parts that took longer than expected.

Try it on one site first. Import a WordPress site into a free Neleto project and rebuild a single page. Within an hour you'll know whether your site is mostly content, which moves easily, or mostly plugins, which doesn't.