Change the page and it's live.
Add a column or drag a row around, and every change syncs live to your team.
Each save strips out the editing tools, so visitors only see a clean, fast page.
Your interface, data, and application logic travel together in a single portable file you can inspect, diff, or run offline.
Add one script tag and the live DOM becomes the source of truth.
Start with a regular HTML file and add ClayJS: the file edits and saves itself in place, so your team can shape the live app directly.
Because the page itself holds the app and its state, saving the HTML file is all it takes to publish a change.
One HTML file. Your application and its state live together in a single file.
Edit in place. You shape the live DOM directly in the browser, right on the page.
Persist clean HTML. Saving copies the live DOM, strips owner-only editing controls, and writes clean HTML as the next version while your tab stays open.
Because state, interface, and data rules live in the same HTML document, editing on the page, publishing clean JSON, and running offline are all side effects of saving one file.
Add a column or drag a row around, and every change syncs live to your team.
Each save strips out the editing tools, so visitors only see a clean, fast page.
Describe what on your page is data with a small rules tag, and Hyperclay publishes clean JSON at a stable URL on every save.
Double-click your downloaded file on your laptop and it opens, edits, and saves back to itself completely offline.
AI can build a full-stack app in a day, and when a tool needs a database and a server, you should build one. Most ideas are not there yet, and you will not know which ones matter until people actually use them. An HTML file costs nothing to start and nothing to throw away, so you can try ten ideas with your team today and grow the winners into full applications later.
Let Claude Code, Cursor, or your own coding agent read and edit your HTML files on Hyperclay from the command line or through an MCP server.
claude mcp add clay -- npx -y @panphora/clay-agent mcp
You see what would make your software better. Yet the real app sits behind a brick wall, wired to servers, databases, accounts, APIs, and templates you cannot touch.
Leaving an existing system forces you to coordinate databases, APIs, accounts, and templates yourself. All that machinery pushes you back when all you want is to edit the page.
Imagine a single HTML file that travels with you and holds its own interface, behavior, and content. User actions, UI state, and app logic all live right inside the page.
With ClayJS, an HTML file becomes software that edits and saves itself. Cut the wires to separate servers, databases, and templates, and own the working app.
See my full thinking: Why I built Hyperclay