GitBrand

For marketing and comms teams

Everyone starts from the same brand.

Campaign work moves fast and touches a lot of hands. A repository your team, freelancers and agencies all open before they start means fewer off-brand drafts, fewer “where is the logo” messages and a palette that stays consistent across channels.

  • Member-only for internal brands
  • Palette exports for designers and developers
  • AI tools read the same source
#marketingTuesday
  1. Jo
    Where is the logo? Need the dark version for the webinar slides by 10.
  2. Mika
    Same as always: it is all in the brand repo. Dark wordmark is under Logos, PNG export is on the card.
    North brand repositorygitbrand.com/north
  3. Jo
    Got it, and the HEX for the title bar too. Thanks.
    Pinning the link to the channel

Every channel

Each channel wants a different file. All of them come from one link.

People use whatever is closest. If the closest logo is in a chat thread, that is the logo they use. A repository gives every channel the right format without a request to design.

Website

Needs
SVG logo, HEX values, web fonts
From GitBrand
Download the SVG from the logo card; export the palette as CSS or Tailwind for the developer.

Decks

Needs
Transparent PNG, RGB values, font names
From GitBrand
Export PNG on demand from the same SVG; every color shows RGB beside HEX.

Social

Needs
Symbol on light and dark, HEX for templates
From GitBrand
Logo variants named by background, so the right one is obvious at 2am before a post.

Print

Needs
Vector logo, CMYK approximations
From GitBrand
SVG for the printer plus CMYK values on each color card. Confirm with the supplier; CMYK is an approximation.

Email

Needs
Small PNG, safe fallback font
From GitBrand
PNG export for signatures and headers, font notes that say which system font to fall back to.

Ads

Needs
JPG or PNG at platform sizes, exact colors
From GitBrand
JPG and PNG exports for ad platforms, one palette every agency copies from.

Two repositories

Internal for the team, public for the world

Most marketing teams need two links: a member-only repository with templates and unreleased work, and a public one with the approved subset for press, partners and AI tools. Both use the same slug format, and either can be embedded on your own site.

Internal brand

gitbrand.com/north-internal
Member-only
  • Slide masters, document and social templates
  • Unreleased campaign identities and drafts
  • Voice principles and example copy
  • Do-and-don’t examples as resources

Invited accounts only. Never indexed, never exposed to AI endpoints.

Team · freelancers · agencies under contract

Public brand

gitbrand.com/north
Public
  • Approved logos with SVG, PNG and JPG exports
  • Named colors with HEX, RGB, HSL and CMYK
  • Font names and downloads where licensed
  • Boilerplate and a press contact in the FAQ

Indexable. Optional AI access publishes brand.json, llms.txt and MCP.

Press · partners · directories · AI assistants

AI drafts in the right voice

Give AI tools the same source as your team

Teammates paste a prompt and get generic copy in generic blue because the tool never saw the brand. For a public repository with AI access enabled, GitBrand publishes brand.json, a Markdown version, llms.txt, llms-full.txt, a REST endpoint and an MCP endpoint. Point an assistant or agent at the URL and it reads the real palette, fonts and voice.

Private and password-protected repositories are excluded, so the internal brand stays internal. Read more about AI access.

# Public repository with AI access on
https://gitbrand.com/north/brand.json
https://gitbrand.com/north.md
https://gitbrand.com/north/llms.txt
https://gitbrand.com/north/llms-full.txt
https://gitbrand.com/api/v1/repos/north
https://gitbrand.com/mcp/north

# Private and password repositories: not published

Assign an owner

Is your brand actually owned?

0of 5

Tick what is already true. Each unticked item is a recurring message in your inbox.

GitBrand does not approve creative work; your review process does. A clear owner and a link in every place work starts keep the reference current, and a current reference is the one people reach for.

After a rebrand

The repository is the source. The rollout is still a project.

Update the repository, then find the places where the old brand hides. Because everyone has the link rather than the file, the announcement is one message.

  1. RepositoryReplace logos, colors, fonts and the written guidance together, then announce.
  2. Email signaturesSend the new PNG export and the HEX values with the announcement.
  3. Slide mastersUpdate the template resource in the repository and ask teams to re-download.
  4. Social profilesSwap avatars and covers from the new symbol variants.
  5. Ad accountsPause creatives that carry the old mark; agencies pull new exports from the link.
  6. Partners and pressOne message with the same link they already have. The URL does not change.

FAQ

Questions marketing teams ask

Can we keep some material internal and some public?

Yes. Use a public repository for the press-facing brand and a member-only repository for internal templates and unreleased work.

Is GitBrand an approval or review tool?

No. It is the source of truth for assets and guidance. Keep campaign approvals in the tools you already use for review.

How does the AI integration work?

Public repositories with AI access enabled publish brand.json, Markdown, llms.txt, llms-full.txt, a REST endpoint and an MCP endpoint. Point your assistant or agent at the URL and it reads the real brand. Private and password-protected repositories are never exposed.

Can we see who downloaded what?

You can see what, not who. Insights show views, unique visitors, referrers and download counts per asset, plus a version history of every publish. If you need named audit trails and rights management, an enterprise DAM is the better fit.

Do freelancers and agencies need a GitBrand account?

Not for public or password-protected repositories. Member-only repositories require a sign-in, which is the right choice for internal brands with unreleased work.

Writing brand guidelinesHow much to write, and where to put it so people read it.AI accessbrand.json, llms.txt, REST and MCP for public repositories.Brand asset managementWhat a lightweight brand library does, and what it leaves to a DAM.

Pin one link. Retire the thread.

Create the internal repository, invite the team and put the link where work starts. Free for up to five repositories.