Fewer parts to break
No plugins, so no conflicts between them and no plugin updates to keep up with. In 2025, 91% of the 11,334 new vulnerabilities found in the WordPress ecosystem were in plugins.
Velk is a CMS in PHP and MySQL, like WordPress, and it runs on the same hosting. What changes is how a site gets made: you describe it to the AI, the panel is generated for that site alone, and forms, SEO, languages, members and a store already come with the engine.
Both run on PHP and MySQL, from shared hosting to a VPS. A WordPress site grows by stacking plugins on the core; a Velk site is described in one file, site.json, on top of an engine that already has the features.
wp_postmeta.
site.json that declares pages, content types and fields.
The same ground: PHP and MySQL, on shared hosting, a VPS or the cloud
The usual checklist of a professional site, and where each item comes from on each platform.
| What the site needs | WordPress | Velk |
|---|---|---|
| Custom fields | A plugin such as ACF to get field screens; the values are saved as key and value rows. | 18 field types declared in site.json — repeaters, blocks, relations, files — and the panel screen follows. |
| Several languages | A plugin such as WPML or Polylang: the core does not translate content. | Built in: a language prefix in the address, a slug per language, translation tabs in every record, hreflang and fallback. |
| Forms and leads | A form plugin and, often, another one to keep the submissions or send them to a CRM. | Built in: every lead saved in the panel even when the e-mail fails, antispam, campaign data and webhooks to a CRM. |
| SEO | The core makes a basic sitemap; title, description and sharing image need a plugin such as Yoast or Rank Math. | Built in: title, description and sharing image on every page and item, and a sitemap with hreflang. |
| Members area | A membership plugin. | Built in: login, sign-up, password reset and member types with their own fields. |
| Store and subscriptions | WooCommerce, plus extensions for subscriptions and for some payment methods. | Built in, with Stripe: one-off sales, monthly or yearly plans, orders and the customer portal. |
| Tracking and consent | A tag manager plugin and another one for the cookie banner. | A Scripts screen for GTM, GA4 and pixels, held until the visitor accepts, and a conversion event on every lead. |
| Page layouts | The block editor, or a page builder such as Elementor. | Block pages and blocks inside the text, designed by the theme: the editor arranges, the design holds. |
| Login security | A security plugin to limit login attempts and add two-step login. | In the engine: login attempt limits, two-step login with a code by e-mail and CSRF on every form. |
| Updates | The core, the theme and each plugin update on their own schedule, and one can break another. | One engine. An upgrade swaps only its files; theme, content, uploads and .env stay as they are. |
| Working with AI | The AI has to deal with each plugin's screens and data. | Everything the panel does, bin/velk does in JSON, and the official skill teaches Velk to Claude Code. |
Plugin names are common examples, not a review of any of them.
Less to install, less to update, and nothing between the engine and your theme.
No plugins, so no conflicts between them and no plugin updates to keep up with. In 2025, 91% of the 11,334 new vulnerabilities found in the WordPress ecosystem were in plugins.
The client sees the pages, content types and fields the site really has: no dashboard full of notices, no menus for features nobody uses.
Each record keeps its fields together in a JSON column, as the schema declares them. Exporting, moving or querying content means reading one row, not reassembling meta rows.
The structure is one file the AI writes, the CLI answers in JSON and the official skill holds the rules: the AI builds, fills and publishes the site end to end.
A second language is a setting, not a plugin. Addresses, slugs, translation tabs and hreflang come with the engine.
The engine is a versioned download, checked by its fingerprint before it is unpacked. An upgrade replaces the engine and nothing else.
Three parts with clear owners: the engine, which nobody edits; the theme, which is the site; and the content, which the client edits in the panel.
In Claude Code, with the Velk skill, say which pages and content the site has and the fields of each one.
The AI declares everything in theme/site.json: pages, content types, categories, fields and forms.
Velk generates the admin from that file: one screen per page and content type, with exactly those fields.
Plain PHP templates print the content with helpers such as field() and image_url(). No hooks, no template language.
Any host with PHP 8.2 and MySQL. Over SSH the AI deploys and publishes changes; over FTP, the engine finishes its own upgrades.
"item_types": {
"case": {
"label": "Cases",
"slug": "cases",
"template": "single-case.php",
"fields": [
{ "name": "client", "type": "text" },
{ "name": "cover", "type": "image" },
{ "name": "results", "type": "repeater", "fields": [
{ "name": "number", "type": "text" },
{ "name": "label", "type": "text" }
] }
]
}
}
/cases/.WordPress is a solid platform with the largest ecosystem on the web: it runs 39.6% of all websites. Velk is the better fit for another kind of project.
Source: W3Techs, October 2026
There is no one-click importer. The AI moves the site in steps, and you check each one in the panel before the next.
Pages, post types, categories and custom fields become the schema. Approve it before anything is written.
Ask the AI
This WordPress site is moving to Velk. List its pages, post types, categories and custom fields, and propose the site.json before writing anything.
The AI recreates the design as a Velk theme, with the content coming from the panel instead of the code.
Ask the AI
Recreate the current site's design as a Velk theme: same layout, colors and fonts, with every text and image editable in the panel.
Posts, pages, categories and images come from the WordPress export file and are created through the Velk CLI.
Ask the AI
Import the posts and categories from this WordPress export file into the blog, with their images in the media library. Show me the first ten before importing the rest.
Velk addresses posts as /prefix/slug. Keep the slugs, and plan 301 redirects with the AI for every address that changes shape.
Ask the AI
Compare the old WordPress addresses with the new ones and list every address that changes, with the redirect each one needs.
Publish on the new hosting, compare page by page and only then point the domain.
Ask the AI
Publish the site, then list every page with its old and new address so I can compare them before pointing the domain.
No. Velk has no plugin system, by design: what a site needs comes from the engine or is written in its theme. A WordPress theme's look can be recreated as a Velk theme.
If it runs PHP 8.2 or newer with MySQL 5.7+ or MariaDB 10.3+, yes: the same shared hosting that runs WordPress. Apache and Nginx both work.
Yes. Texts, images, posts, menus, translations and leads are all in the panel. New pages, content types or fields go into the schema, through you or the AI.
Not if you work with Claude Code and the Velk skill: you describe, the AI writes. If you'd rather write the code yourself, the theme is plain PHP and the documentation covers it.
Yes. Velk is MIT-licensed and has no paid tier.
A Velk page loads the engine and the theme, with no plugins in between, and a CDN can keep a copy of it once caching is turned on in .env. The final speed still depends on the theme and the hosting.
It is built in the theme — a template, a field, theme/functions.php — or it becomes a request for Velk. The engine is never edited, so upgrades never undo your work.
Install the skill in Claude Code, describe the site and compare for yourself.