hyperclay - frontend and done

Imagine having a portable HTML file that not only displays information but is malleable and shareable.

No complicated server setups, no extra dependencies, just a lightweight HTML file that you can open, modify, and view from anywhere.

Hyperclay hosts these powerful HTML files so you can create personal, malleable software easily.

  1. Own Your Stack: The behavior of your HTML apps is defined client-side. No magic backend. No vendor lock-in. Download and host them yourself.
  2. Familiar Workflow: HTML apps feel as lightweight as Google Docs. Open it, modify it, then share the results. Or clone it with a click.
  3. Safe Backups: Every HTML app retains its entire version history, so all your work is safe from mistakes.
  4. Future-Proof: No framework or database needed. This is a return to the core idea of the web: hackable hypermedia documents you fully control.
picture of founder, david, and his signature

Example HTML apps:

Example HTML app: development log Example HTML app: writer Example HTML app: kanban Example HTML app: landing page

The why and the how

I build several dozen web things a year

When I’m in flow, coding a website feels like writing a story

A hand creating digital things

But it’s better than a story, because I can interact with it as I’m coding

Most of the things I build transform some data into a more useful format

Producing a result from website input

For example,

Example HTML apps

Static websites are the obvious place to host these simple tools

Static websites require less code and have free hosting

But static websites fall short in one annoying way: changes to them are ephemeral

But when you refresh a static website, its results disappear

This is frustrating because the problems I want to help solve are not ephemeral

A series of 3 solutions built on top of each other in sequence

With physical objects, ephemerality is shocking — changes are supposed to persist

A real orange sliced in half becomes half an orange

But there's no obvious digital counterpart to physical objects

A digital orange sliced in half becomes half an orange

Static websites are great, but changes users make to them reset

A digital orange resetting back to a full orange

To get digital objects to act more intuitively, we need to build a whole persistence layer around them

A digital orange being worked on by a giant machine

In practice, this means a server with a database, API, templates, and user accounts

A diagram of user accounts, database, API, HTML

That’s a lot of effort to mimic what we take for granted with physical objects

Invincible meme: Look what digital things need to mimic a fraction of physical things' power

This is frustrating because I want to focus on making the actual thing, not the persistence layer

A person holding up a small boulder labeled 'the actual thing' while propping up a larger boulder called 'persistence layer' with their foot

I'm like a writer who wants to create experiences for readers, but I have to keep fixing typewriters

A person frustrated with a disassembled typewriter

It would be a great to ignore all the noise of modern web dev and just build the experience I want

Drake No/Yes meme with the first panel a full web app backend and the second panel a single, shapeable thing

What I need is a primitive concept that's so obvious it feels like a single, shapeable object

A real shapeable thing, in between a static document with no moving parts and a full web app with too many moving parts

Let’s take an example: a personal dev log I can update over time

A dev log web document

There’s a surprising amount of work in getting this simple digital object online

A progress bar showing the status of setting up a new project

Updating it can be a cumbersome process too, when it should be natural and instant

An equation showing a new thought being added to a web document and producing an updated web document

The best workflow I can imagine is the ease-of-use of a local desktop app you open and edit, but its changes are persisted online

Transmitting a local document to planet Earth

If only my UI had the power to permanently update itself

A local web document with edit controls

When I’m done updating it, people can view it

People impressed with a web document

It would be a better digital object: malleable, shareable, cloneable, persistent

A malleable, shareable, cloneable, persistent web document

Think about how many digital objects are designed specifically for this workflow:

Common digital workflow: 1. You open it, 2. You modify it, 3. You share it

This is the lifecycle of:

  1. Website builders
  2. Docs, spreadsheets, presentations
  3. Multimedia editors
  4. Business dashboards
  5. Blogging platforms
  6. Work management tools
  7. Survey, poll, quiz builders
  8. Knowledge base builders
  9. Mind mapping tools
  10. Invoice generators
  11. Data visualization tools
  12. Financial modeling apps
  13. Creative asset generators
  14. Interactive course builders
  15. Project brief generators
  16. Resume builders
  17. Wireframing tools
  18. Product roadmap makers
  19. Etc etc etc
A guy saying wow

What kind of thing could encapsulate this workflow in a single, small package?

The phrase 'an HTML file?' surrounded by hiding creatures

Of course! Most web apps already use HTML, with a few extra steps in the middle

A depiction of the web app update and render cycle, including HTML, JSON, SERVER, TEMPLATES, HTML

What if we cut out the middle steps?

A depiction of the web app update and render cycle, including HTML, SERVER, and HTML, but skipping JSON and TEMPLATES

We’d be left with a simple, easy-to-think-about stack:

self-updating HTML

HTML becomes the all-in-one database / API / UI, flattening all levels of the stack into one layer

It's a lot less to worry about:

A diagram of user accounts, database, API, HTML, with DB and API crossed out

We’d get a full web app with the same amount of code that a static website requires

A table comparing a static website to a single-file HTML app, they both use the same tech, but the latter persists its changes

It’s easy to think about!

A diagram of a simple stack, showing sending html on a user request and saving HTML when a page owner changes the page

It's a new primitive: a single, shapeable object

A real shapeable thing, in between a static document with no moving parts and a full web app with too many moving parts

Introducing Hyperclay, a place to host self-modifying HTML files (e.g. HTML apps)

Hyperclay + HTML = HTML Web App

Hyperclay gobbles up ordinary HTML pages and makes it so changes made to them persist

A creature gobbling up HTML documents and creating digital objects

Here’s how simple your online, editable, shareable journaling app could be:

<div contenteditable>
My new blog!
</div>

Or you could build a way to track the extra hours you worked this week:

<h1>Extra Hours</h1>
<input type="checkbox" persist>
<input type="checkbox" persist>
<input type="checkbox" persist>
(persist writes the checked attribute to the DOM)

For something more complex, see my personal dev log:

(To persist changes, request access to Hyperclay)

A screenshot of panphora.com, my personal dev log

The types of HTML documents Hyperclay makes possible unify UI, state, and behavior into one

Cracked pieces of a circle forming back into one

But best of all, shaping these HTML documents feels like shaping something real, like a physical object

A hand squeezing an orange

Not in the mood to go down endless rabbit holes just to build a simple idea that pops into your head?

Avoid rabbit holes, like a deploying a server, database, and user accounts
Hi, I’m David, I’d love to introduce you to a lightweight way to build web apps.
Introducing Hyperclay:
Single-file HTML apps
hyperclay newsletter
© 2025 Hyperspace Systems LLC
3 Rules Privacy Pricing Changelog Docs