We built Cellpy because we were tired of a problem that shouldn't exist in 2026: copying and pasting the same HTML snippet into dozens of websites and then hunting down every instance whenever something needed to change.
If you've ever managed content across more than one site — a banner, a pricing table, a promotional hero section — you know the drill. Design makes a change. You get a Slack message. You update one site. Then another. Then you forget the third one. A week later someone notices the old pricing is still live somewhere. It's embarrassing, it's slow, and it scales terribly.
Cellpy treats web content blocks the way software engineers treat code: as a first-class artifact that has a version, a deployment, and a single source of truth.
You build a block once — in HTML, CSS, and optionally JavaScript — using our VS Code extension. You publish it. Then you drop a single <cellpy-block> Web Component anywhere you want it to appear. From that point on, when you push an update to the block, every site that embeds it gets the new version automatically. No deploys. No find-and-replace. No coordination overhead.
<cellpy-block id="your-slug" /> into any HTML page. One line. Done.Blocks can also be themed per-container so the same component looks right on every site it appears in, and the Marketplace lets you buy or sell blocks across teams and organizations.
This is just the beginning. We're building toward a world where non-technical teams can manage live web content with the same confidence and velocity that engineering teams ship code. Watch this space — and if you want to shape where we go next, sign up for free and tell us what you're building.