Run it for any purpose
Changed it and serve it to others? Publish your changes. Or ask for a commercial license.
Ask on GitHubWHY OPEN SOURCE
Why we built the DAM and brand manager in the open, and why AI makes it matter.
THE OLD DEAL
Most brand libraries are closed. You can't see how they work or run them yourself, and when you leave, your tags, credits and rules stay behind.
THE REAL PROBLEM
Which logo is current? Which photo is licensed for paid social in Germany? What are the rules, really? Artbucket writes the answers down, as data, next to the files.
WHY AI NEEDS IT
Agents now make and ship brand work. They need a source of truth they can query and you can inspect, host and take with you, not a vendor's black box.
{
"allowed": false,
"reason": "superseded",
"suggest": "Blender logo mark"
}
SO WE BUILT IT IN THE OPEN
The whole core, free to self-host: library, guidelines, portals, API and MCP. Your metadata is written back into your files, so leaving costs nothing. Cloud runs the same code.
$ git clone https://github.com/pwnera/artbucket.git
$ cd artbucket && pnpm install
$ docker compose up -d
$ pnpm dev
✓ Open http://localhost:3000
WHAT'S IN THE CORE
THE ROADMAP
Library, rights, brand rules, SSO.
Lifecycle, white-labeling, stable API.
Guidelines as a site, built by people or agents, and brand as code.
Insights is in: release adoption, the use-check log. Next, where and by whom.
Leave Bynder, Canto or Frontify in an afternoon.
Your files in your own bucket, on a server someone else runs.
LICENSE AND CONTRIBUTING
Changed it and serve it to others? Publish your changes. Or ask for a commercial license.
Ask on GitHubOpen an issue before building on the roadmap.
Contributing guideYOUR BRAND. YOUR CHOICE.
Same core either way.