Appearance
Why kitloom
There are plenty of ways to build a site in 2026, and most of them work. kitloom's answer fits in one line: start from WordPress, grow on Laravel, run it with AI. WordPress is where nearly every site and client begins, so that is where kitloom starts. Laravel is what the site stands on from then on. AI is where sites are going, so that is where it takes them. Here is why we think that is worth your time — each point with something you can check for yourself.
1. An AI agent does the work, under your control
kitloom/ai puts an MCP server on the site. Claude, Cursor or your own agent connects to /mcp, calls describe_site, and then does the work through the same code as the admin: create_content for posts and pages, upload_media, menu_save, redirect_from_404, product_save and orders_list — every installed module brings its own tools. Ask it "which addresses gave 404 this week? Redirect the ones that have a new page", or "fill in the SEO descriptions of the products that have none".
It acts as the user whose key it holds: an author's key writes drafts, a read-only key only reads, and nothing it does is beyond what that user could do in the admin. The settings that decide who gets in or what code runs on every page are locked, nothing is deleted for good — it goes to the trash — every change is in the activity log, and revoking the key stops it at once. Run your site from Claude or Cursor shows it at work.
2. Start from your WordPress site, or a new one
Bring the site you have. kitloom runs on the WordPress database. Not an import, not a copy: the same wp_posts, the same options, the same users with the passwords they already have, the same plugin tables. The site answers at the same URLs, so search engines and old links don't notice the move.
You don't have to take that on faith either. kitloom can draw your live site from its database with a read-only user, and a script compares both sites page by page — the rehearsal happens before anything is switched.
Or start a new one. php artisan kitloom:install asks which modules the site needs, a theme fills it with demo content, and no WordPress is installed. The content takes WordPress's shape — posts, pages, terms, menus, users — which editors know from the first day and AI models know well, and where a client's old WordPress site fits in later.
3. It is Laravel, with nothing hidden underneath
There is no WordPress code inside: no hooks, no wp-admin, no globals. A post is an Eloquent model ($post->title, $post->field('price')), an option is Settings::get(), a change to content fires a Laravel event. Every module is a Composer package with its own tests.
So your team works the way it already does — Composer, PHPUnit, queues, Octane, your deploy pipeline — and the next developer who opens the project recognises what they see.
4. Fast, and clean by Google's measure
On the same database, kitloom serves a page faster than WordPress: 14.7 ms against 19.6 ms across thirteen pages, and 25 ms against 43 ms once WordPress carries the plugins most sites run. The benchmark shows every number and how it was taken.
Speed on the server is half of it. The other half is what a visitor's browser gets. Here is Keystone, one of the themes that come with kitloom, measured by Google Lighthouse on a public demo — as a phone on a slow connection sees it, and on a desktop:
On a phone: ninety-nine for performance and one hundred for accessibility, best practices and SEO, with the first text in about a second and nothing shifting while the page loads. On a desktop, one hundred for all four. That is the theme as it ships, not a page made for the video: canonical URLs, meta tags and structured data come from the core and the SEO module, images that will be the largest thing on screen are fetched first, a map loads only when the visitor scrolls to it, and contrast, link names and heading order are part of how a theme is checked. Open a demo, press Lighthouse in Chrome's developer tools, and see what you get. The benchmarks page has the other pages of the theme, how it was measured and how to measure it yourself.
5. Filament or Nova — your call
The admin is the one your team already knows. Kitloom for Filament and Kitloom for Nova carry the same core, the same modules and the same themes; only the admin differs. Every module brings a screen for each.
6. Plugins become modules, and keep their data
A WordPress site is as much its plugins' data as its posts. kitloom's modules read that data in the plugins' own formats: ACF fields, Contact Form 7 forms and Flamingo messages, WooCommerce products and orders, Rank Math's SEO settings and redirects. Here is what comes over and how.
Around them are the modules a Laravel site needs anyway — languages, bookings, courses, listings, backups, two-factor sign-in, webhooks, a cookie banner that holds trackers back — each installed with Composer and switched off with one setting.
7. You see all of it before you pay
There is no free tier and no trial clock, because there is nothing held back. One click gives you a Filament or Nova sandbox of your own with every module and theme — no sign-up, no card. The documentation is all public, with video lessons for the modules. And if kitloom doesn't fit once you have it on your own site, you get the full amount back within 14 days, no reason needed. Why it works this way.
What kitloom is not
To be fair about it: kitloom doesn't run WordPress plugins or themes — a plugin's data comes along when there is a module for it. It has no block editor; existing blocks are drawn, and new content is written in a visual editor. And the move is one way: kitloom writes arrays as JSON, which WordPress doesn't read back.
If that still sounds like your next site, open a demo — it takes one click.