The designer · four surfaces, one document
Also in the product
The document · decisions written down, not implied
The suite · five products, one account
The designer · four surfaces, one document
Also in the product
The document · decisions written down, not implied
Read
The suite · five products, one account
Comlumen
Comlumen stands alone and you never need the others. If you already use one, you are already signed in here — and one of them is wired directly into the designer.
The parent company and the console. Where the account lives. Comlumen is a satellite of it, which is why one sign-in reaches all five products rather than five.
Client portal. Project status, async approvals, file delivery and billing, in one workspace shared with the people you build for.
The component library. The one Comlumen imports from. Its manifest renders every component to markup, which is what lets the designer preview and place them live.
Tools for the rest of the workflow. Auditing, checking and measuring — the jobs that sit either side of designing a page.
| Product | Comlumen's connection to it | Needed to use Comlumen? |
|---|---|---|
| Stacklumen | The Clerk instance this app is a satellite of — one sign-in reaches all five. | No — but it is where the account lives |
| Baselumen | Its manifest is proxied and cached server-side, and renders live in a designer panel. | No |
| Hublumen | None. Separate product, same account. | No |
| Kitlumen | None. Separate product, same account. | No |
Comlumen is a Clerk satellite of stacklumen.com rather than its own instance. A person who sets a dark rail in one product arrives here with a dark rail already set, because the preference keys are the suite's rather than ours — renaming them would create a second setting that merely looks like the first.
The tokens, the shape-and-elevation contract and the shared screens are vendored from Stacklumen and kept byte-identical by a sync whose check mode fails a build on drift. Exactly one file here is Comlumen's own: the accent ramp that makes this the blue product.
Baselumen's manifest is proxied server-side and cached, because the upstream renders every component on each request and opening a panel three times should not cost three full library renders. It serves stale rather than nothing when the library is briefly unreachable.
Comlumen is a fully custom deployment and the rest of the suite is not. That means no shared base path and no shared build assumptions — a difference worth stating, because the sibling repos look similar enough that the difference is easy to miss.
Comlumen stands alone. The suite is a convenience, not a dependency.