Launching today
BrandStack
The brand management OS for modern teams
4 followers
The brand management OS for modern teams
4 followers
BrandStack is a Brand Operating System for designers and agencies β one place for your colors, typography, logos, voice, and brand guidelines. No more digging through old PDFs, Drive folders, or half-updated Figma files to find the right hex code. Every asset is stored with context (roles, usage notes) and exports instantly to CSS, Tailwind, or JSON. Built solo by a graphic designer who got tired of scattered brand files.
Curious how you handle collaboration when multiple designers need to tweak the same brand system at once, and is there any sort of version history to roll back mistakes?
@sunakphhΒ right now, BrandStack doesn't have live multi-user collaborative editing (like Figma-style simultaneous editing) or full version history yet. Team members can be invited to a brand and make changes, but two people editing the exact same field at once isn't handled with conflict resolution today, and there's no rollback/undo history beyond what's in the activity log.
This is honestly one of the most important things on my list for v2 β multi-brand support just shipped, and proper collaboration + version history is the next big piece I want to get right rather than rush.
Really appreciate you asking this directly β it's exactly the kind of question that tells me what to prioritize next. Is this something you'd need on day one, or is single-editor-at-a-time workable for how your team actually operates?
as a designer this looks like exactly what i needed last week, one thing though would be huge if you could add a way to generate a shareable client portal link with view only access so stakeholders can browse approved assets without needing an account
@rfan1463852Β This is exactly the kind of feedback I was hoping for, thank you. A view-only shareable client portal is honestly a fantastic idea β removes the friction of clients needing to create an account just to see approved assets, which is a real pain point I hadn't prioritized yet.
Adding this to the roadmap now. Rough shape I'm thinking: a public read-only link per brand (or per specific sections you choose to share), no login required on the client's end, revocable anytime from your side.
Out of curiosity β when you say "approved assets," do you also want a distinction between draft/in-review vs. finalized items, so clients only ever see the polished version? That would change how I'd structure the permissions layer.
Really glad it's landing well for you as a designer β that's exactly who this is built for.