WordPress wordpress.com

Can AI replace WordPress?

Q: Can AI replace WordPress?

Half-bot. The thing people actually use WordPress for on a personal site, write posts, upload images, publish, have an RSS feed, is a weekend build and always has been. An agent can hand you a SQLite-backed CMS with a markdown editor, media uploads, drafts, tags, and a sitemap in one sitting, and it will be faster and less hackable than the real thing. What you cannot one-shot is the other 90 percent of WordPress: 60,000 plugins, WooCommerce, Yoast, Elementor, the block editor, and the fact that any freelancer on earth can pick up your site. Also worth noting that core WordPress is already free and self-hostable, so the honest question is whether you want to maintain your own CMS instead of someone else's. If your site has a contact form, a store, or a client who needs to log in, stop reading and just install WordPress.

The thing people actually use WordPress for on a personal site, write posts, upload images, publish, have an RSS feed, is a weekend build and always has been. An agent can hand you a SQLite-backed CMS with a markdown editor, media uploads, drafts, tags, and a sitemap in one sitting, and it will be faster and less hackable than the real thing. What you cannot one-shot is the other 90 percent of WordPress: 60,000 plugins, WooCommerce, Yoast, Elementor, the block editor, and the fact that any freelancer on earth can pick up your site. Also worth noting that core WordPress is already free and self-hostable, so the honest question is whether you want to maintain your own CMS instead of someone else's. If your site has a contact form, a store, or a client who needs to log in, stop reading and just install WordPress.

Verdict: Half-bot · AI gets you partway; the hard part stays hardBuild time: a weekend

Half-bot

01What it costs

$4/moPersonal, per month, billed annually

$48per year at that price

Checked Aug 18, 2026 · source: wordpress.com.

02Could AI build it for you?

The core job: A single-admin, self-hosted CMS that stores posts in SQLite, edits them as markdown, uploads images to local disk, and serves fast static-ish HTML with an RSS feed.

What a working version needs:

Node 22 and a machine or VPS to run it on
A domain and TLS if you want it public
Local disk or an S3 bucket for media
Your own backup habit

Replacing WordPress for a personal blog is easy; replacing it for a site with a checkout is a career change.

03What you'd give up

The plugin ecosystem: SEO, forms, caching, memberships, analytics, backups, all one click away in WordPress and all your problem in the DIY build
WooCommerce and anything resembling commerce
Gutenberg block editing and the visual page builders non-technical people actually like
A theme marketplace, so your site looks like whatever the agent felt like that day
Any hope of handing the site to a developer who already knows the stack
Security updates and managed hosting done by someone who is not you

Almost nobody pays for WordPress the software. They pay for managed hosting so the site stays up and patched, for the three or four plugins that quietly run their business, and for the person who knows how to fix it when the theme update explodes. A personal CMS you built yourself removes the hosting bill and adds an on-call rotation of one. That trade is fine for a blog and terrible for anything that takes money.

05The build prompt

Paste this into an AI coding tool (such as Claude, ChatGPT, Lovable or Replit) to build your own version.

prompt.txt

Build a self-hosted personal CMS for a single author. Empty folder, no cloud services, no telemetry, no accounts beyond one local admin.

Stack, non-negotiable:
- Node 22 with TypeScript, Fastify for the server
- SQLite via better-sqlite3, single file at ./data/cms.db, schema created on first boot
- Server-rendered HTML with Eta templates, no client framework
- Plain CSS in one stylesheet, readable typography, dark mode via prefers-color-scheme
- markdown-it for rendering, with a syntax highlight pass and HTML sanitization on output

Features in scope:
- Posts and standalone pages: title, slug, markdown body, excerpt, tags, status (draft, scheduled, published), publish timestamp
- Admin at /admin behind cookie session auth: one admin user, password hash from ADMIN_PASSWORD_HASH in .env, argon2 or bcrypt
- Admin editor: textarea with live preview pane, save as draft, publish, unpublish, delete with confirm
- Media upload to ./data/uploads, images resized to a max width with sharp, served with long cache headers, insert-into-post button that pastes markdown
- Public routes: home with paginated post list, /posts/:slug, /:pageSlug, /tags/:tag
- /feed.xml RSS 2.0, /sitemap.xml, per-post OpenGraph and Twitter card meta tags
- Full text search over posts using SQLite FTS5
- Scheduled posts appear automatically based on publish timestamp, checked on request, no cron needed
- Import script that reads a folder of markdown files with YAML frontmatter and inserts them, so a WordPress export converted to markdown can be loaded
- npm run backup that copies the db and uploads into a timestamped tarball

Explicitly out of scope: plugins, themes, comments, multi-user roles, multisite, e-commerce, a block editor, and any hosted API.

Secrets in .env with a committed .env.example. Ship a README with setup, the password hash generator command, and how to run it behind Caddy with TLS. Include a seed script with three sample posts and a page so the site is not empty on first run.

Sponsor slot · openFeatured alternative to WordPress. A labeled card for one relevant tool.

Book this spot →

App prices, verdicts, alternatives and build prompts are adapted from Can I Vibecode It? (MIT License, © 2026 Rob Hallam). Each price shows the date it was checked and its source. Prices change; confirm on the vendor's site before you decide.

01What it costs

02Could AI build it for you?

03What you'd give up

05The build prompt

Get new verdicts in your inbox.