Signet gives a group of brands one shared block library and one deployment pipeline. Each site looks like itself — because the brand is a token pack, not a fork.
One library, every brand site
Azure, S3, GCS or local
Immutable, traceable to a commit
The runtime cannot rewrite itself
The block library is the design system. Everything below ships with every site.
Every block carries a machine-readable spec, so an agent can compose a page the same way an editor would.
Code ships as a signed container image. Nothing on the server can rewrite itself — the injection problem disappears.
Add a brand as a token pack. The blocks restyle themselves; nobody forks a component.
Assets are served from object storage behind short-lived signed URLs, never from the web root.
Landing pages route through an approval queue, and the control plane always fails safe.
A new brand site starts as a fork and a brand pack, not a new codebase.
The same three steps whether a person or an agent is driving.
Copy the repo, drop in a brand pack: colours, type, logo, tagline. The tokens are stamped into the build.
Pages are assembled from the shared library. Agents read the block manifest and write valid content directly.
CI builds a single image, the platform deploys it, and the control plane records exactly what is running.
A brand pack is a small file of design tokens plus an identity: colours, radii, type weights, logo and tagline.
Swap the pack and every block in the library restyles itself — the same hero, the same card grid, a different company. No component is ever duplicated per brand, so a fix lands everywhere at once.
Why this platform exists.
Every brand site was administered by hand, dependencies lived in git with no manifest, and nobody could say which commit was live.
Fifty-seven ad-hoc blocks became a single reviewed set, documented for both editors and agents.
Each app ships as a container built in CI. The filesystem is read-only, so a compromise cannot persist.
Sites register with the DXP, heartbeat their version, and route landing pages through approval.
"The blocks are the design system. When we fix one, every brand site gets the fix on its next deploy."
"A new brand used to mean a new build. Now it means a brand pack and a deploy."
Yes. Pages are composed from the block library in the CMS admin, with the same blocks agents use. Nothing is hard-coded per page.
Nothing. Approval and heartbeats are advisory and fire-and-forget — a site keeps serving and keeps publishing if the DXP is unreachable.
In the DAM, backed by object storage. The site receives short-lived signed URLs, so binary content never sits in the application root.
Fork the repo, add a brand pack, point the capsules at it. The platform code is identical across customers by design.
We will walk you through the block library, the brand system and the deployment model.
