Why Artist Alley
The problem
Section titled “The problem”The file is on a shared drive, the notes are buried in a chat thread, and the approved version went out through a transfer link that has since expired. Versions get tracked by hand in names like final_v3_really_final, and a few years later nobody can find the asset or explain why it changed.
Artist Alley brings that work into an open-source, self-hosted digital asset management (DAM) library. Artists upload files into posts. The browser previews images, video, audio, 3D models and documents, and reviewers comment on the work itself rather than in a separate thread. Custom fields keep a history of every change to their values, so the library also becomes the record of the project.
Studios work with each other too, so Artist Alley instances can connect directly. They talk ArchivePub, an open protocol we defined. It borrows ActivityPub’s model, but it doesn’t connect to ActivityPub servers like Mastodon. Right now, paired instances can exchange likes and comments using authenticated requests. Sharing assets and posts between studios is still to come. The spec is published and anyone can implement it, because a connection between two studios should belong to the studios, not to a vendor in the middle.
Who it’s for
Section titled “Who it’s for”Artist Alley is shaped around game and animation studios, and the features show it: a review canvas that zooms, pans and tiles, frame-by-frame playback, 3D viewers in the browser, and direct connections between studios that each run their own instance.
Game and animation work aren’t really separate worlds. A cinematics team reuses in-game art, the game team pulls finals back from cinematics, and the brand team owns the art bible both draw on. Files move in both directions between the same kinds of specialists (concept, modelling, rigging, animation, FX, lighting, comp, brand, cinematic editorial), so Artist Alley keeps them in one library instead of one tool per department.
Collections outside studios. A museum might not care about animation reviews, but it still needs to organize files, track changes to its records, and find things again. That part works today. The workflows that are specific to physical collections, like accessions, locations and loans, aren’t built yet. They’re planned, and the design is written up.
By role:
- Artists upload work, group their files into posts and read the review notes.
- Reviewers and leads open posts and leave feedback on the work itself, in the comment thread and on the review canvas.
- Studio operators run one Docker image next to their own Postgres, behind the reverse proxy they already have. There is real setup: two keys that must never change, a storage volume, and backups that cover the database, the stored files and both keys. The Install guide walks through it.
Artist Alley is pre-1.0 and in active development: releases are tagged, but it isn’t production-ready yet.
Still to come: a review queue for work you haven’t seen yet, version history and side-by-side comparison, live review sessions, share links for people outside the studio, and gating for NDA work. The roadmap has the order and the details.
How it’s licensed and priced
Section titled “How it’s licensed and priced”Artist Alley is open source: AGPL-3.0-only and free to self-host (ADR 0016). Commercial licensing and paid tiers are planned, but nothing commercial is offered today and no license can be obtained.
That matters in one place right now. Generic SSO (LDAP and SAML) is in the code but only switches on with a license feature, so it isn’t available yet. We’ve decided generic SSO should be free (ADR 0066), and that’s on the roadmap.
When paid options do arrive, the idea is that the AGPL core stays complete, tiers are about scale, and add-ons cover things that cost real money to run or that let operators charge their own users. Running your own AI models stays free. ADR 0017 and ADR 0038 have the thinking.
Until then: install it, run it, use it.
What we explicitly aren’t
Section titled “What we explicitly aren’t”- A general-purpose asset manager for archivists. We’re shaped for studios that actively produce art. The archive grows out of the production work; it isn’t the starting point.
- A pipeline integration platform. Artist Alley is where finished and in-progress art lives. It doesn’t replace version control, production tracking or the tools artists create in. Importing from those tools is planned.
- A hosted-only service. Self-hostable by design. A managed hosted offering may follow for indie studios without IT staff, but self-hosting will always be supported.
- NFT / crypto / blockchain anything. Different audience, different values. Not for us.
Non-negotiables
Section titled “Non-negotiables”- One binary, shipped as a Docker image. The server and the web app are a single program, packaged with the tools it calls at runtime, and it connects to your own Postgres.
- Two containers to run. The app and Postgres, behind the reverse proxy you already have if you want one. No add-on containers ship today; the optional AI integrations connect to model servers or provider APIs you run. For operators covers the setup.
- Postgres-only. No MySQL adjunct, no separate search index, no separate vector store: one database to run. A full backup covers that database plus the stored files and both keys (Backup).
- Open by default. The core is open source. If paid add-ons arrive, they are planned to be additive, never clawing back something already included.
Read on:
- Architecture: how the binary, database, and frontend fit together.
- Design pillars: the principles we use to make product decisions.