WebX · AI-enabled CMS for growing businesses

A CMS your team can run—and your AI assistant can help manage.

We build sites on WebX, a flexible CMS for small and midsize businesses. Run pages, catalogues, SEO, languages, and site structure from one admin panel; connect an AI client through MCP to prepare and update work in drafts, then decide what goes live.

A clear UI for content, catalogues, and publishing.

WebX brings the everyday work of running a site into one clear system: people have a practical admin panel, while an AI client can work through the same permissions, drafts, and review steps. These are real screens from our demo site.

WebX admin panel editing a Consulting service page: block list on the left, live preview on the right showing a new lead saved as a draft, the page marked Live with pending edits, and a Publish button.
The same service in the WebX admin panel on a phone, with the draft shown in the preview and a Publish button.

The WebX admin panel on desktop and mobile. An AI assistant has saved a new service lead as a draft; the live site keeps the published text until someone publishes the change.

  1. 01

    The assistant gets a task

    Connected through MCP, it reads the site’s content rules, runs a dry run to check exactly what would change, and saves the edit as a draft.

  2. 02

    The draft waits for review

    The page is marked as having edits. The preview shows the new text, while visitors still see the published version.

  3. 03

    A person decides what goes live

    Publishing is a separate step. Every published version stays in the history and can be restored, and earlier drafts are kept too.

Recorded on our WebX demo site in October 2026 with demo content only. Screens are cropped, not edited. Select a screenshot to enlarge it.

One CMS for the work that grows with your business.

WebX is part of a website we build around your operation—not a self-serve subscription. Start with the sections you need, then adapt the system as content, products, and workflows become more complex.

Content and pages

Create, preview, structure, and update the pages your team needs as the business changes.

Catalogues and commerce

Manage products, properties, stock, filtered landing pages, and product information in one place.

SEO and site structure

Keep SEO fields, addresses, redirects, menus, and sitemaps accurate as the site grows.

AI-assisted operations

Connect an AI client through MCP to prepare content, format updates, and work with the same controlled workflow as your team.

Most sites stall on content, not on design.

The website launches, and then every update depends on someone finding time to do it by hand.

Content is the bottleneck

Articles, product cards, translations, and seasonal updates pile up because someone has to sit in the admin panel and do them by hand.

AI lives in a separate tab

Teams already draft with AI assistants, then copy and paste the result into the site field by field. The slowest step is still manual.

Most admin panels were built for clicks

A conventional CMS has no safe way to let an assistant work inside it: no scoped access, no preview of a change, no record of what it did.

Your assistant works inside the site, not next to it.

The parts of the site you allow an assistant to access are available through the same rules and review step.

  1. 01

    You give the task

    In plain language, in the AI assistant you already use: “Write an article on spring maintenance and add it to the blog as a draft.”

  2. 02

    The agent reads the rules

    Before writing, it reads your site’s languages, tone of voice, what never to say, and what already exists, so it reuses rather than duplicates.

  3. 03

    It tries the change first

    Every change can run as a dry run: the system reports exactly what would happen, without changing anything.

  4. 04

    It works in drafts

    Content lands as a draft or a new version. The live site does not change until someone publishes.

  5. 05

    You review and publish

    You check the result in the same admin panel your team uses, edit if needed, and publish—or ask the agent to revise.

  6. 06

    Everything is recorded

    Each change is kept in the history with its author, so you can see what the agent did and restore an earlier version.

Work you can hand over today.

Blog and articles

Draft, structure, and update articles in every site language, with internal links and SEO fields filled in.

Catalog updates

Create and update products, properties, and stock, or import a supplier spreadsheet and review the result.

SEO fixes

Run a site audit, review the issues, and fix titles, descriptions, redirects, and broken links.

Translations

Bring pages, products, and articles into the other languages of the site, following the same tone rules.

Inbox triage

Read incoming form submissions, sort them by status, and prepare a summary for the team.

Routine site edits

Update banners, menus, FAQs, team profiles, vacancies, prices, and events without opening a ticket.

You stay in control

Autonomy you grant, not autonomy you hope for.

The agent can do only what you allow, in the sections you allow, and every change is visible. Start with drafts; widen access when the results earn it.

Access per section

Each agent key can read or write only the sections you choose. Read-only for the catalog and write access to the blog is a normal setup.

Keys you manage

Agent access is created and revoked in the admin panel. Remove a key and the agent loses access immediately.

Dry run before writing

Changes can be previewed as a dry run, so you see the effect before anything is saved.

Drafts and versions

Agents work in drafts and versions. Publishing stays a deliberate step, and earlier versions can be restored.

History of every change

The history shows who changed what and when—a person or an agent—so nothing happens silently.

House rules for content

Languages, tone of voice, and forbidden claims are stored once in settings and read by the agent before it writes.

Not sure how much to delegate? Read how to choose the first job for an AI agent. WebX can support a custom website, an e-commerce catalogue, or ongoing SEO and growth work.

Most platforms now let AI in. The difference is what it can safely do.

Choose based on the parts of the site an assistant can reach, whether you can preview a change, and what record it leaves—not simply whether a platform has an AI feature.

AI agent access compared
WebXWordPressShopifyWebflowDirectusContentful
What an agent can work withEvery section of the site: pages, blocks, blog, catalog, SEO, forms, menus, media, and settingsWordPress.com and Jetpack-connected sites: posts, pages, comments, categories, tags, and media. Other self-hosted sites: only what installed plugins exposeOfficial servers cover shopping carts, store policies, and developer docs; editing the store admin needs a third-party serverDesign, pages, assets, and existing CMS items; cannot create new localized CMS itemsCollections, items, files, field definitions, comments, and configured flows in the connected Directus projectEntries, assets, content types, releases, locales, tags, and AI Actions in connected spaces and environments
How it is enabledBuilt in; agent access is created in the admin panelWordPress.com paid plans, or Jetpack AI or Complete on self-hosted sites. Otherwise: MCP Adapter plugin plus plugins that register abilitiesBuilt-in Sidekick assistant inside Shopify; external agents through third-party serversOfficial MCP server, authorized per workspaceNative MCP server connected to a Directus project with a user token or loginRemote MCP uses OAuth plus an MCP-app allow-list per space and environment; local MCP uses a personal access token
Preview before savingDry run for every change: the result is reported, nothing is savedWordPress.com: the agent describes the change and asks for approval. Self-hosted: not providedDepends on the third-party serverIsolated page branches on Enterprise plansNo standard MCP dry run; use the project’s own publishing and review workflowContent Preview API for unpublished content; releases can be validated before publishing
Access controlRead or write access per section, per agent keyWordPress.com: roles plus per-operation switches. Self-hosted: permission checks written by developersAdmin API token scopes, such as product write accessExisting Webflow roles, one workspace per authorizationRole-based permissions, including granular controls for collections and fieldsA user’s Contentful permissions plus a remote MCP allow-list for each space and environment
Drafts and recoveryDrafts and versions with restoreWordPress.com: new posts default to draft; trash kept for 30 daysDepends on the third-party serverPage branches on Enterprise plansUnpublished content versions can be compared with the main version; item revisions record changesDraft state, published-entry snapshots, and releases that can be validated before publish
Record of agent actionsHistory of every change, by a person or an agentWordPress.com: Activity Log. Self-hosted: requires a logging pluginDepends on the third-party serverNot described in the documentationActivity and revision records are linked to the Directus user making a changeEntry versions record published changes; the MCP documentation does not describe a separate agent-action log
HostingBuilt on open-source packages; can run on your own serverAny host, or WordPress.comHosted by ShopifyHosted by WebflowDirectus Cloud or self-hostedHosted Contentful SaaS

Based on public documentation, last checked in October 2026. Self-hosted WordPress depends on the plugins installed, and all platforms change quickly. Sources: WordPress.com MCP server documentation; WordPress MCP Adapter review (InstaWP); WordPress.com MCP write capabilities (The Next Web); Shopify MCP guide (Gamut); Webflow MCP server documentation; Directus MCP and platform documentation; Contentful MCP server documentation.

One system for the whole site.

Each site gets only the sections it needs. Every section is available to people and to AI agents alike.

Content

Pages built from reusable blocks, blog, media library, menus, FAQ, press, and events—so your team updates the site itself, in every language.

Commerce

A full catalogue—categories, brands, properties, stock, filtered landing pages, pricing plans—so products and prices stay current in one place.

Marketing and SEO

SEO addresses, redirects, sitemap, and a built-in site audit, plus banners and reviews—so search basics stay correct as the site grows.

Operations

Form inbox with notifications, tasks, services, team profiles, and vacancies—so enquiries and routine pages are handled where the site is managed.

Access and settings

Roles, AI agent access, languages, and site-wide settings—so you decide who and what can change which part of the site.

Data and maintenance

Catalog import and export, redirect import, image optimization, backups, and site health checks—so the site stays fast, safe, and easy to move or restore.

A complete admin panel—with or without AI.

For your team

  • A clean admin panel for people, with light and dark themes
  • Interface available in 10 languages
  • Block-based page building with reusable content blocks
  • Multilingual content on every page, product, and article
  • Drafts, previews, and version history for the whole team

Under the hood

  • Laravel on the server, Vue 3 in the admin panel, so any experienced web developer can work with it
  • Built from open-source packages, so you are not locked into a proprietary platform
  • Each section ships with AI agent tools and documentation, so an agent knows what it can do without custom setup
  • Extended through supported extension points, without forking the core, so customizations do not block core updates
  • Agents connect over the Model Context Protocol (MCP), an open standard, so you can use the assistant you already have

Control, security, and ownership in plain terms.

Short, factual answers to the questions teams ask before giving anyone—or any AI—access to their site.

Who can access what?
Each administrator has a role. Each AI agent has its own key with read or write access to specific sections. Sign-ins to the admin panel are logged, including bursts of failed attempts.
What reaches the live site?
Agents and editors work in drafts. A change goes live only when someone with permission publishes it, and an agent’s change can be checked with a dry run first.
How do we undo a change?
Published versions are kept and can be restored in one step. Earlier draft copies are kept too.
Can we see what changed?
Every change is recorded in the history with its time and author. The history and the log of agent activity are not deleted automatically.
How is access removed?
Revoke an agent’s key or remove an administrator in the admin panel, and their access ends immediately.
Where does the site live, and who owns it?
The site runs on your own hosting; WebX is not tied to a particular provider or control panel. The site, its content, and its database are yours to move or take elsewhere at any time.
What about backups?
WebX can create database backups as an extra safety net. Full backups of files and databases are made with your server’s or hosting provider’s own tools.
How is sensitive data stored?
Passwords, keys, and tokens are not stored in plain text.
What happens when something breaks?
Critical issues are fixed out of turn. Other issues are handled in order during business hours.

Not available yet. Sign-in uses an email and password; two-factor authentication and single sign-on are not available yet. We do not hold security certifications such as SOC 2 or ISO 27001.

Ask us a technical or security question

Before you start.

Which AI assistants can work with the site?

Assistants that support the Model Context Protocol (MCP), such as Claude, ChatGPT, and a growing number of other tools. You use the assistant you already have; the site provides the connection.

Is it safe to let an AI agent into the admin panel?

The agent gets only the access you grant, section by section, and you can revoke it at any time. It works in drafts, can preview changes as a dry run, and every change is recorded in the history. Publishing remains your decision.

Do we have to use AI at all?

No. The admin panel is a complete content management system for people. AI access is an option you switch on when it is useful.

How do we connect our assistant?

The admin panel includes step-by-step instructions. Connecting an assistant takes a few minutes and does not require a developer.

Is this a product we buy separately?

No. It is the system your website is built on. You order a website from us, and this is how you and your AI assistant manage it after launch.

How much does a site like this cost?

It depends on the scope: the sections you need, the design, integrations, and content. We propose a scope and estimate after a short conversation about your business.

Start with the problem

Tell us what is not working—or what still feels unclear.

We will recommend a starting point.

Discuss your project