Wave 1 comes first
Proves the whole chain on one real site: a block running, a site plugged in, a message arriving.
- Alerts
- Titles and previews
- Contact inbox
- Annotation tool
My private control room. Contact forms, alerts, email and waitlists are built once as shared blocks, and every one of my sites plugs in.
See the blocks
A printer's type case, musée Champollion
of my sites built their own contact form. In BlockHub it becomes one block, Contact form inbox, in wave 1.
From a scan of 43 of my project folders, which found 23 features that kept coming back.
A printer casts each letter once and sets it on every page. BlockHub does that for the parts every one of my websites needs.


18 service blocks run once on the BlockHub server, and each site uses them with its own key. 7 skill blocks are recipes an AI coding agent installs into a site. None is built yet. Try the switches.
12 sites send their messages to one place. I get an alert, the sender gets a confirmation.
Service block, wave 1Sales, sign-ups and errors from 15 sites reach my phone, plus one daily summary.
Service block, wave 116 sites stop keeping their own email code. No email goes out twice.
Service block, wave 1Titles, share previews and discovery files, installed the same way in 15 sites.
Skill block, wave 110 sites share one waitlist, with invite codes for opening the doors.
Service block, wave 2Proves the whole chain on one real site: a block running, a site plugged in, a message arriving.
Each site has its own key, so its messages and sign-ups never mix with another site's.
Checked live when this page loaded. Full status