newsletter login

Underneath Hyperclay, every app is still one HTML file.

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.

  1. Strips admin-only tools
  2. Snapshots a clean HTML document
  3. Writes it back to disk or your server

How an HTML file saves itself

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.

  • Make one with AI or pick a free template.
  • One ClayJS script tag adds page editing, a visual CMS, and owner controls, each of them optional, so the file can stay lightweight.
  • No build, deploy, or database: on Hyperclay, saves go live right away and sync with teammates.
  • An open format, so you own the file: download your HTML anytime, or run files offline with Hyperclay Local and HTML Clay.

The interface is not a
picture of the software. It is the software.

  • Browsers turn HTML into a live tree of elements called the DOM.
  • Most web apps treat the DOM as a temporary picture of state stored somewhere else.
  • Self-saving HTML files treat the file itself as the truth.

How saving works

Because the page itself holds the app and its state, saving the HTML file is all it takes to publish a change.

  1. One HTML file. Your application and its state live together in a single file.

  2. Edit in place. You shape the live DOM directly in the browser, right on the page.

  3. 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.

4 layers of plumbing, removed
Database Migrate a schema
Server Coordinate backend
JSON API Update an endpoint
Build & Deploy Rebuild bundle & wait
Browser View The whole app

Built into every HTML file

Tailwind CSS, zero build

  • Write Tailwind classes straight in your HTML with no build step.
  • Edit source directly in browser DevTools or the built-in code editor.

Version history & guards

  • Restore in one click to the version created on every save.
  • Overwrite guards catch stale tabs before they clobber newer changes.

Collections & dashboards

  • Public submission form when you mark a folder as a Collection.
  • Private owner dashboard that updates live out of the box.

Multi-tenant HTML files

  • Turn on signups for any public HTML file.
  • On paid plans, every user who signs up gets their own editable copy on its own subdomain.

Fork & upgrade templates

  • Copy any public HTML file with one click to make it yours.
  • Pull new template versions when an author ships an update without losing your own data.

Open public-domain spec

  • Open specification with conformance tests.
  • Independent hosts so your HTML files outlive any single vendor.

How the file model works in practice.

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.

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.

Owner-only edit controls Instant publish

Change a number on the page and its JSON data updates.

Describe what on your page is data with a small rules tag, and Hyperclay publishes clean JSON at a stable URL on every save.

Public /_/api JSON endpoint No separate database

Download your HTML file and run it anywhere.

Double-click your downloaded file on your laptop and it opens, edits, and saves back to itself completely offline.

Self-contained HTML Free HTML Clay app Two-way desktop sync

Give more of your ideas a chance.

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.

Use the AI agent you already pay for.

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

Your software shouldn't live in a silo.

  1. You rarely control your own software.

    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.

  2. Building it yourself means fighting the stack.

    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.

  3. What if one file held everything?

    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.

  4. Self-saving HTML files cut the cords.

    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