Skip to content

Your code, your repo, your AI, with a visual editor

Xodia runs your own dev server and writes each visual edit as a small, readable change to your source: no Xodia package, no config file, no export. Your AI connects over MCP with Xodia's tools and skills, and you can work from a folder on your own computer.

Free plan. 14-day Pro trial. No charge unless you choose a plan.

The Style panel: a pointer sets the heading's weight to 700 Bold, the heading on the canvas turns bold, the change shows as 1 unsaved and the class font-bold appears in the Code tab.

Sound familiar?

Keep your tools, lose the busywork

The trade-offs developers usually face with visual tools and AI, and how Xodia avoids them.

  • Visual tools want your site on their platform

    Xodia edits your repo as it is. Saves are commits with only the lines that changed, and your host deploys them as it does today.

    See how it works
  • Every small tweak costs a prompt

    Nudge spacing, swap a colour or fix a line break on the canvas. The Style panel writes Tailwind classes with your theme tokens, or edits your CSS rule.

    See the visual editor
  • Your AI can't see what it built

    26 MCP tools let it read your selection, run checks, read logs and take screenshots of the live preview, and 39 skills show it how to work.

    See your AI in Xodia
  • You'd rather work on your own machine

    Open the folder on your computer with xodia dev: the preview runs locally, uses no preview hours, and you commit with your own git.

    See local folder mode

A typical week

A week with Xodia in your toolbox

Code where code is quicker, click where clicking is quicker, and let your AI do the long parts.

  1. MondayImport a repo from GitHub; Xodia detects the framework, styling, package manager and host.
  2. TuesdayRun /xodia:build in Claude Code for a pricing page, then review it on the canvas.
  3. WednesdayFix the spacing yourself in the Style panel instead of writing another prompt.
  4. ThursdayOpen a pull request from Xodia; your CI runs on it as usual.
  5. FridayOpen the folder on your laptop with xodia dev for a bigger change in your own editor.

Settings, Code and Git: the project's GitHub repository and branch, and Open on this computer, using a folder on the computer with its own git.

The right plan

Start free, add Starter for more sites

Free includes the full editor, MCP access and the skills for 1 project. Starter adds 3 projects, branches and pull requests, and host connections.

  • Free

    The full editor with your own AI, free.

    $0 / month

    • 1 project
    • 1 seat
    • 3 preview hours a month
    • 1 preview at once
    • 5 SEO tests a month
    • MCP access
    • 39 core skills
    • Local folder mode
    • Branches and pull requests: Main only
  • Starter

    Best fit

    CMS editing, branches and host connections.

    $15 / month

    • 3 projects
    • 1 seat, up to 3 at $12 each a month
    • 25 preview hours a month
    • 1 preview at once
    • 50 SEO tests a month
    • MCP access
    • 39 core skills
    • Local folder mode
    • Branches and pull requests
    • Host connections
    • CMS and host packs

Every plan is billed monthly in US dollars. Compare every plan and limit.

Questions

Questions from developers

Do I need to change my config or add a package?

No. An imported site needs no Xodia package or config file. Xodia runs your own dev server, and each save contains only the lines you changed.

Which AI apps can I use?

Claude Code, Claude app, Cursor, Codex and VS Code and any other app that speaks MCP, on your own subscription. See the setup for each.

Can I keep using my own editor?

Yes. Open the folder on your computer with xodia dev and keep VS Code open beside Xodia: changes from either land in the same files.

What does Xodia commit?

Only what you save, as a commit on the branch you choose, with the lines that changed. Unsaved work is autosaved to a private ref, never to your branch.

Keep exploring

Open your repo in Xodia.