Skip to content

Design pillars

Artist Alley has two product pillars. When a design decision could go either way, we pick the option that serves one of them.

An archive only works if the work actually goes into it. Artists upload at the end of a task, when the next one is already waiting, so every extra step is a reason to leave the file on a desktop instead. The system should fill in what it can on its own.

  • Drag in a folder and the files upload in the background. You choose whether they become one post, one post per file, or just assets with no post.
  • EXIF and IPTC metadata, dimensions and color profiles are read on upload, and supported raw camera files show their embedded preview.
  • The set of required fields is small. An admin can add more for the studio.
  • Uploading, finding, commenting, publishing and copying a post’s link should each take as few steps as possible. If one takes more, that’s a design problem to fix.
  • Optional AI integrations are experimental and connect to services an admin sets up; no models come with the app. Searching by image is further off: some of the code exists, but there’s no supported way to set it up yet, and it’s planned to arrive with installable add-ons. Automatic tagging on upload is a later follow-up.

Upload should be quick and light. If a studio wants more metadata, an admin adds the fields; the artist shouldn’t have to fill in what the system or the studio can supply.

Artist Alley is designed for review that happens every day, so the tool is shaped around that loop: open the work, look closely, say what needs to change, and come back to it later.

  • Posts have comments with threaded replies, and a post’s owner can turn off new comments. Text documents can already take notes pinned to a line or passage; pinning a note to a frame, a timestamp or a spot on an image is planned.
  • The review canvas zooms, pans and goes fullscreen, and it can tile a texture so you can check that it repeats cleanly.
  • Video playback has the controls review needs: J, K and L to step back a frame, pause and play, frame stepping, speeds from 0.25x to 4x, and an in/out loop.

Still to come in this arc: a list of what you haven’t reviewed since your last session, picking up mid-review where you left off, and live review sessions where everyone watches the same playback together.

Review depends on the steps around it. Artists make the work in their own tools, a light upload brings it into the library, posts and collections keep it easy to find, and review sends notes back to the artist for the next pass.


The pillars describe how the product behaves. Three postures describe how it fits into a studio:

  • One library, not five tools glued together. A studio shouldn’t need a DAM, a review tool, a transfer service, a chat bot and a wiki wired together just to store, review and find its work. Artist Alley’s aim is to keep that in one library you host yourself. It sits next to the tools artists create in, version control and production tracking rather than replacing them; Why Artist Alley says where the line is.
  • Open by default. The core is open source: AGPL-3.0-only and free to self-host. Commercial licensing and paid tiers are planned but not offered today, and the plan is for them to add to the core, never take away from it. A few capabilities in the code, such as generic SSO, still only switch on with a license feature that can’t be obtained today, so they aren’t available yet. How it’s licensed and priced has the detail.
  • Federated, no rent. Studios that work with outside partners (co-development teams, marketing agencies, licensing partners, museums on loan) should be able to share work directly between their own instances, without a vendor in the middle, a per-outsider seat license, or an export and re-import that loses the metadata along the way. Pairing two instances sets up that connection; what each studio shares over it is a separate choice. Today a paired connection can carry likes and comments over authenticated requests. Sharing assets and posts between studios is still to come. The protocol is ArchivePub, which the Artist Alley project defined. It borrows ActivityPub’s model but doesn’t connect to ActivityPub servers like Mastodon, and the spec is published so other tools can implement it. We wrote it because we didn’t find an existing spec that fit, and because a connection between two studios should belong to the studios.

Each piece on its own is familiar: a library for files, a place to review them, a way to work with partners. The pillars are meant to reinforce each other. If uploading stays light, the work actually reaches the library; if review happens on the work itself, the notes stay attached to the file they’re about. And because the studio runs the system, its archive and its partner connections don’t depend on someone else’s service.