BrandStack
The brand management OS for modern teams
9 followers
The brand management OS for modern teams
9 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.
How does it handle versioning when a client needs to compare older brand guidelines against the updated ones? Would that history be visible to collaborators too?
@azat825266 Honest answer: there's no real version history yet. Right now BrandStack tracks an activity log (who changed what, and when) but there's no way to actually view or restore an older snapshot of the brand guidelines, and no side-by-side comparison between versions.
This is actually the second time this exact question has come up today, which tells me it's a real gap, not an edge case. Version history + the ability to compare an old guide against the current one is now on my v2 list.
On visibility to collaborators — once it exists, my instinct is yes, it should be visible to anyone with edit access on that brand, since the whole point is keeping a team aligned on what changed and why. Would that match what you'd expect, or would you want some version history restricted to admins only?
Finally something for this exact headache. The one-click CSS and Tailwind export from a saved color role is genuinely useful, saved me a Solid mess of tokens. Curious how it handles multi-brand workspaces.
@halimez69340 Really glad the export saved you from that mess — that's exactly the pain point I built it around.
On multi-brand workspaces: right now each brand is fully separate — its own colors, typography, logos, tokens, all scoped independently, so nothing bleeds between them. Switching between brands is instant from the sidebar. If you're managing client work, each client's brand stays cleanly isolated from the others.
What I don't have yet is anything shared across brands (like a global component library reused across multiple client brands) — is that closer to what you're asking about, or more about how many brands one account can hold?
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.