Ruweb for developers: the CMS your AI knows

Laravel 13, PHP 8.3 and Tailwind 4, with docs written for agents, 12 skills for Claude Code and Codex and its own MCP server. Open source, MIT licensed.

Documentation and tools for agents

Ruweb includes documentation, skills and an MCP server so different AI tools can work with its structure and content.

  • AGENTS.md and a task table

    The repository rules and which skill and which document fits each task. A new agent knows where to start without anyone explaining it.

  • 12 skills for Claude Code and Codex

    Create pages, templates and forms, translate content, review a change. They live in the repository, versioned with the code.

  • Its own MCP server

    Pages, posts, media, settings and menus over JSON-RPC and REST. Your agent writes drafts with the same authorization as the panel; publishing is a separate call.

  • Conventions linter and tests

    Conventions are checked by a linter and every screen and every flow has its test.

  • Claude Code
  • Codex
  • Cursor
  • GitHub Copilot
  • Windsurf

I wanted AI tools to work with the same structured content that a person edits.

Built on Laravel, not improvised

Ruweb does not reinvent security, authentication or infrastructure. It stands on Laravel, a framework with more than a decade of maturity and a huge community, and builds only what is specific on top.

  1. Laravel
  2. Ruweb core
  3. Project
  4. Editor
  5. Client
  • Standardized structure, not improvised
  • Clear, self-documenting conventions
  • Any developer can pick up a project and understand it
  • Less risk of a project depending on one person

Laravel 13, PHP 8.3, Tailwind 4 and MySQL.

It installs like any Laravel app

These are the real commands from the README. The installer creates the database if your user has permission, runs the migrations, creates the admin and links the storage.

# requirements: PHP 8.3+, Composer, Node 20+ and MySQL
$composer install
$cp .env.example .env
$php artisan key:generate
$npm install
# creates the DB, migrates, creates the admin and runs storage:link
$php artisan cms:install
# server + queue + logs + Vite
$composer run dev
# app on localhost:8000, admin at /admin

16 plugins you no longer install

Each one had to be configured, maintained, updated and prayed over. In Ruweb those functions are the system's own code: no third parties, nothing to install, nothing to configure per project.

16plugins per project

  • Elementor
  • Rank Math
  • WP Rocket
  • WP Mail SMTP
  • Wordfence
  • WPS Hide Login
  • ShortPixel
  • Redirection
  • Really Simple SSL
  • Site Kit
  • WP Activity Log
  • reCAPTCHA
  • JetEngine
  • JetElements
  • JetFilters
  • JetWooBuilder

What used to be the launch checklist is now the starting point.

What the core already ships

This comes from the repository, not from a promise.

  • Per-page SEO

    Title, description, canonical, Open Graph and sitemap generated from the content.

  • Redirects and 404 monitor

    301 and 302 rules, CSV import and a list of the 404s that receive traffic.

  • Optimized images

    WebP and responsive variants on upload, with a placeholder per aspect ratio.

  • Forms with anti-spam

    CSRF, honeypot, rate limiting and reCAPTCHA v3 on every public form.

  • Configurable admin login

    The access path changes from Settings, no plugin.

  • Header, footer and contact

    Business data and social networks in one place, editable by the client.

  • Multilanguage

    Content per language, with admin text parity checked by tests.

  • Live editor

    Page and blog editing with preview, with admin and editor roles.

  • MCP server

    Your AI agent reads and writes drafts with the same authorization as the panel.

Stores arrive with Ruweb Commerce (see the roadmap below).

Light HTML from the architecture

With a theme, a builder and plugins, even a simple landing page can end up loading 1 to 3 MB, several stylesheets and an unnecessarily deep DOM. That is why a whole category of patches like WP Rocket exists: they compensate for a base that is born heavy.

WordPress + ElementorRuweb
Initial weight of a simple landing page
1 to 3 MB, even on basic pagesMuch closer to what is strictly needed
DOM and markup
Extra layers, wrappers, generic CSS and JS to cover every caseHTML, CSS and JS written for that project
Cache plugins
They end up part of the stack: cache, minify, deferNo need to patch what is born light
Time spent on performance
Extra work after buildingSolved from the architecture
Technical SEO
Another front to configure and watchClean, semantic, controllable base

In Ruweb I do not start from a generic abstraction that then has to be tamed. I start from custom code: if a page needs a title, a grid, a form and an animation, that is exactly what loads.

Ruweb pays off more in the right hands

AI is not magic: you cannot ask it for a professional site in a single prompt. It works when the right tool is in the hands of the right profile.

Traditional team: 3 people

  • DesignerMakes mockups in Figma and the content. Their work stays an image.
  • Project managerRuns communication, estimates tasks and coordinates handoffs.
  • DeveloperRebuilds in WordPress, fights Elementor and solves things with plugins and hacks.

Three people, three tools, three languages.

Team with Ruweb: 1 person

  • Lead creativeUnderstands the client's intent, has visual judgment and turns a blank canvas into something approvable, then keeps to that line in every new view and in support.

One person, one tool, one file: code.

The creative designer-developer

Someone with real experience and their own judgment, who understands what the client wants and turns it into proposals. That good taste used to need a developer to exist. Now it is part of the deliverable. AI is not good at inventing style, but it is very good at following one that is already defined: once the five base views are approved, replicating the pattern is trivial.

The alternatives, one by one

Pick what matters most to you and see who wins on it.

What matters most

WordPress + patchesCode from scratchRuweb
Development speed
MediumSlowFast
Makes use of AI
Poorly (patches)Yes, but inefficientlyYes, from the ground up
Reusable base
Yes (limited)NoYes (without those limits)
Security and authentication
Third-party pluginsImprovise itInherited from Laravel
Customization
LimitedTotalTotal
HTML and performance
HeavyIt dependsLight by design
Post-delivery support
HighVariableMinimal
Standardization
MediumLowHigh

Ruweb does not compete by being the extreme. It competes by removing the unnecessary friction of both extremes.

Where the platform is heading

Every project built on Ruweb feeds the base. What gets solved once becomes available to every project that follows.

  1. Today

    Ruweb CMS

    Pages, blog, forms, media, menus, multilanguage and an MCP server.

  2. Next

    Ruweb Commerce

    Online stores on the same base.

  3. Future

    Quickstarters by vertical

    Ready-made starting points for each industry.

What people ask

An open source CMS I built on Laravel 13 and PHP 8.3, with Tailwind 4 and MySQL, designed so an AI and a person build sites on the same code. The repository is on GitHub under the MIT license.

Yes. It works with Claude Code, Codex, Cursor, GitHub Copilot, Windsurf and others. The project ships documentation for agents, 12 skills and an MCP server.

Stores will arrive with Ruweb Commerce. Today you can see in the cases how I solved stores and WhatsApp orders on Ruweb.

On hosting with PHP 8.3 and MySQL. The repository includes guides for cPanel and for your own server.