Your AI first visual editor.
Ask an assistant for a page, or change the one in front of you — both happen in the same editor, on the same draft, and a person approves what goes live. What comes out is a normal Astro codebase in your own Git repository: host it anywhere, take it with you, and it keeps working if you ever leave.
The gap this closes
Page builders give you good editing and a proprietary format. The modern static stack gives you a portable, fast, cheap site that only developers can operate. Webentor is the editing experience on top of the ownership model.
AI first, not AI added
Claude, ChatGPT, Cursor or any MCP client connects to your site and works with the same operations the editor uses — pages, blocks, media, forms, theme tokens, previews — on a line of its own. It reads back the preview it built; a person reviews it and publishes.
Own it, actually
Your content is JSON in a Git repository, not rows in someone's database. Clone it, read it, and build it with no part of this platform involved.
Edit it visually
Blocks, patterns, media, menus, forms and theme tokens — edited on the page, by people who do not write code. Drafts, review and approval when more than one person is involved.
Publish anywhere
A published site is a directory of static files. Cloudflare Pages, Netlify, GitHub Pages, S3, a zip, or hosting we run — and changing your mind later costs nothing.
Work together
Real-time co-editing, presence, per-document locks, roles and approvals. Two people can write in one document and both edits survive.
Branch your content
Take a copy of the site, redesign it, preview the real built output, then merge it back. The live site never sees it until you say so.
Four ways to run it
The stack is free and unlimited for one person on one machine — forever, by rule, not as a trial. What is paid is the orchestrator: the dashboard, many sites managed together, the queue, the fleet.
| Core | Studio Self | Studio Managed | Studio Cloud | |
|---|---|---|---|---|
| What it is | the stack, CLI and editor | the orchestrator, on a box you own | the same, and we run the box | the orchestrator, on boxes we run |
| Licence | MIT | proprietary | proprietary | proprietary |
| Who runs it | you | you | us | us |
| Who owns the hardware | you | you | you | us |
| Sites and people | unlimited | unlimited | unlimited | metered |
| Who it is for | anyone self-wiring, alone or in a team | a team that wants its own server | a team that does not want to administer one | anyone who does not want a server at all |
Getting started
This box is a Studio instance. If you have an account on it:
- Sign in app.studio.webikon.eu — sign-in is a link or a code sent to your email. A passkey, once you add one, confirms the actions that cannot be undone.
- Create a site Start from a template, or import an existing site from its sitemap, WordPress or Drupal.
- Edit it — yourself, or with your assistant Open the editor and change the page in front of you, or connect your assistant from the project's Settings → AI assistants: Claude Code, Claude and ChatGPT sign in; Cursor, VS Code, Gemini CLI and Codex get a token, and so does any other MCP client. Every change lands on a draft, not on the live site.
- Publish Review, approve, and publish to your own hosting — or to hosting this box runs.
Availability, stated plainly
The stack is MIT licensed and the rights are real. One person on one machine can do everything the product can do, with no account and no limits. That is a rule the codebase is checked against, not a marketing tier.
Distribution is still private. Nothing is published to
public npm until the first production release, so npm install
is not yet a way in — access is by invitation while the product is
finished in the open with real sites on it. If you want in, ask.
Pricing is not on this page because nothing is charged yet: there is no payment surface, and the plans above describe how the product is run, not what it costs.