Artbucket Cloud is open, as a free beta.Cloud is in free beta. Start freeTry it

WHY OPEN SOURCE

Your brand's truth
should be yours.

Why we built the DAM and brand manager in the open, and why AI makes it matter.

01

THE OLD DEAL

Your brand, in
someone else's box.

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.

See how it works?Closed source
Run it yourself?Not an option
Leave with your metadata?Left behind
02

THE REAL PROBLEM

Finding files is easy.
Authority is hard.

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.

Which logo is current?Logo mark, v3
Paid social in Germany?Not until Oct 1
Primary color on dark?#e87d0d
03

WHY AI NEEDS IT

An agent can't read
authority from pixels.

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.

Current? Licensed? Allowed?
{
  "allowed": false,
  "reason": "superseded",
  "suggest": "Blender logo mark"
}
04

SO WE BUILT IT IN THE OPEN

Postgres and a bucket.
Nothing else.

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.

~/artbucket
$ git clone https://github.com/pwnera/artbucket.git
$ cd artbucket && pnpm install
$ docker compose up -d
$ pnpm dev
✓ Open http://localhost:3000
DockerKubernetesRenderFlyCoolifyVPSAWS S3R2B2MinIO

WHAT'S IN THE CORE

Nothing held back
when you run it.

THE ROADMAP

Opinionated
on purpose.

The full roadmap
  1. SHIPPED

    DAM, API and MCP

    Library, rights, brand rules, SSO.

  2. SHIPPED

    Portals and v1

    Lifecycle, white-labeling, stable API.

  3. SHIPPED

    Brand pages

    Guidelines as a site, built by people or agents, and brand as code.

  4. IN PROGRESS

    Analytics

    Insights is in: release adoption, the use-check log. Next, where and by whom.

  5. NEXT

    Migration

    Leave Bynder, Canto or Frontify in an afternoon.

  6. NEXT

    Bring your own bucket

    Your files in your own bucket, on a server someone else runs.

LICENSE AND CONTRIBUTING

Free to run.
Open to help.

AGPL-3.0

Run it for any purpose

Changed it and serve it to others? Publish your changes. Or ask for a commercial license.

Ask on GitHub

YOUR BRAND. YOUR CHOICE.

Run it yourself,
or let us.

Same core either way.