Aller au contenu

Roadmap

Ce contenu n’est pas encore disponible dans votre langue.

What shipped in each tagged release of Artist Alley, and what each open GitHub milestone plans next. Planned releases follow the milestones and can change; nothing here says when a release will ship.

Release and milestone status from GitHub data captured 2026-11-16 04:45 UTC. Descriptions last reviewed 2026-11-16.

Latest release

v0.11.1, released 2026-11-16

Public CI datasets

Next planned release

v0.11.2, planned

ArchivePub and archival standards

0 of 4 tracked issues and pull requests closed

Coming up

v0.11.2 · planned · ArchivePub and archival standards

A cleanup of the ArchivePub specification, and an asset contract that carries each file's checksums, formats, rights and preservation history using established archival standards, with the matching ADR amendments. It follows v0.11.1 and comes before v0.12.0.

  • An archival asset contract for ArchivePub Shared files carry checksums, formats, rights and preservation history aligned with BagIt, PREMIS, PRONOM, Dublin Core and IIIF, together with the specification cleanup and ADR amendments this needs.
v0.11.3 · planned · Optional update notices

A planned opt-in daily check to tell administrators when a newer release is available. It would be off by default and send only the installed version number. The work includes an ADR 0017 amendment for this check and the separate v0.11.4 installation-count opt-in. It follows v0.11.2 and comes before v0.11.4.

  • Optional daily update notices An optional daily release check for administrators, off by default, sending only the version number, together with the ADR amendment covering this and the separate installation-count opt-in.
v0.11.4 · planned · Optional installation counts

A planned, separate opt-in that would add a random install ID to the daily request, allow an instance to request that it be forgotten when turned off, and publish installation totals. It builds on v0.11.3 and comes before v0.11.5.

  • A separate opt-in for installation counts A separate opt-in setting for a random installation ID, a request to remove that ID when the setting is turned off, and public totals.
v0.11.5 · planned · Official federation directory

A planned official directory for instances whose operators choose to list them. The work includes deploying the directory, suggesting it on the admin directories page, listing the demo instance and showing how many servers have opted in. It follows v0.11.4 and comes before v0.12.0.

  • An official directory for opted-in instances An official directory deployment, suggested from the admin directories page, with the demo instance listed and a count of servers that choose to be listed.
v0.11.6 · planned. No description has been written yet.
v0.12.0 · planned · Review and collaboration: shared sessions, a shared canvas and inspectors

The review tool becomes a shared workspace: presentation rooms and synchronised review, frame-accurate annotation on video, a full whiteboard, and inspectors for textures, colour and file formats. The real-time transport for shared sessions is not decided yet.

  • Presentation rooms and synchronised review Live presence and synchronised playback in a review session, with one person driving. The real-time transport is not decided yet.
  • Frame-accurate review player Draw on a frame, see annotation markers on the scrubber, show strokes from neighbouring frames, and keep every note tied to the frame it was made on.
  • Player quality of life Transport controls built for animators, frame stepping, in and out loops, playback rate and safe-area guides, and a cleaner full-window viewer.
  • A full collaborative whiteboard A shared canvas built on the same drawing foundation as the review player.
  • Texture, colour and format inspectors Split texture channels and inspect mip levels, extract palettes and pick colours, and read the header and encoding details of a file.
  • Version comparison and timeline assembly Compare two versions with a wipe and a difference view, and assemble takes into a review cut.
  • Image sequences Play a numbered image sequence as one item, with frames held in memory and an always-on-top review window.
  • Review queue Track what has not been reviewed since your last session, and pick up where you left off.
  • Project workspace Group review work by production.
  • Send work to and from DCC tools Push and pull between Artist Alley and the DCC tools artists already use.
  • Heavy 3D formats Convert heavy 3D formats on the server for viewing, and add USDZ with Apple Quick Look.
  • Realistic 3D materials PBR lighting and environment control in the 3D viewer.
  • Review with a paired instance Share review work with a partner studio's instance.
v0.13.0 · planned · Articles and 3D animation

Two self-contained additions. Articles let you publish long-form writing as a kind of post, and 3D models gain named animation clips that can be shared between models with compatible rigs.

  • Articles Long-form posts such as devlogs and write-ups, written in Markdown with a dedicated reading page.
  • Shared animation clips Play an animation clip from one 3D model on another with a compatible rig. Whether clips can move between different rigs is still being researched.
v0.14.0 · planned · Community, moderation and engagement

Tools for running a community instance: moderation, feeds, brand kits, homepage curation and announcements. Ad slots are an operator option and are off by default.

  • Moderation A moderation queue and reports, with a retention window before content is removed from disk.
  • RSS and Atom feeds Subscribe to collections and public work in a feed reader.
  • Brand workspace Access-controlled brand kits and guidelines shared across teams and paired instances.
  • Homepage curation Featured collections and a curated front page, with new kinds of featured cards.
  • Announcements Operator announcements on the home page.
  • Ad slots Placements an operator controls, off by default.
  • A fuller account area The account pages that are still placeholders get real screens.
  • Private teams Teams that only invited members can see, with graded read and write access.
v0.15.0 · planned · Sharing, bulk actions and asset workflow

Share links for people without an account, more bulk actions on top of the selection that shipped in v0.10.0, gating for sensitive and NDA work, and workflow rules. It also carries the remaining storage operations.

  • Share links Links that let people without an account see work you choose to share with them.
  • More bulk actions Delete, move to a collection, change state and export to CSV across a whole search result. Selecting many items (v0.10.0) and editing their metadata together (v0.11.0) have already shipped.
  • Gating for sensitive and NDA work Blur, a recorded reveal, and timed embargo lifts for sensitive assets, built on the scheduled-actions engine from v0.5.1.
  • Storage operations An orphan cleanup that checks again before deleting, a per-asset view of stored versions, and job concurrency changes that apply without a restart.
  • Workflow rules and notifications Triggers, notification rules and scheduled exports, and an editor for workflow states.
  • Bulk import, export and reprocessing Import and export in bulk, regenerate previews and re-read file metadata.
  • Watermarked previews A brand or viewer stamp on previews, applied on the server and set by the operator.
v0.16.0 · planned · Privacy, audit, observability and reporting

Privacy and consent tools, a fuller audit trail, insight for operators into how their instance is running, reports, and storage tooling for duplicates, re-import and backup.

  • Storage tooling Find duplicate files, re-import from storage, and back up and restore.
  • Privacy and consent A consent banner, and tools to answer a person's request to export or delete their data.
  • A personal-data switch for operators Choose how IP addresses are captured and kept, and redact personal data.
  • Audit log and change history A history of what changed on each record, and who changed it.
  • Observability for operators Insight into how the instance is running, and errors that are always logged.
  • Reports Reporting and analytics for operators.
  • Library health Find material that is stale, duplicated, at risk on rights, or inconsistent in its metadata or permissions.
  • Report a problem A button that builds a diagnostic bundle, with personal data removed, for the user to review before sending.
v0.17.0 · planned · Platform and extensibility

Single sign-on and webhooks, plugins, a registry for optional add-ons, imports from other systems, chat notifications, and an MCP server and client. The add-on registry is what the planned paid add-ons in v0.18.0 depend on.

  • Single sign-on and webhooks Sign in through LDAP, SAML or OAuth, register OAuth apps, and send webhooks. Single sign-on is not available yet.
  • Plugins Extensions an operator installs, run in a sandbox so they cannot reach what they are not given.
  • Add-on registry A registry and installer for optional capabilities, such as reading text in images.
  • Connections to other platforms Publish to and pull from external platforms.
  • Chat notifications Send notifications to team chat, starting with Slack.
  • Imports from other systems A common way to bring content in from external systems.
  • MCP server and client Let AI tools read the catalogue through MCP, and let Artist Alley use other MCP servers.
  • Optional Blender converter An optional worker that converts 3D formats browsers cannot load, such as .blend and USD, so they get preview thumbnails again.
v0.18.0 · planned · Paid add-ons, planned and not offered today

Mostly planned paid add-ons, which depend on the add-on registry planned for v0.17.0. None of them is offered today: Artist Alley is AGPL-3.0-only and free to self-host. This release also plans viewers for file formats from proprietary DCC tools.

  • Licensing for paid add-ons Planned and not offered today: the licence checks that paid add-ons would need.
  • Selling your own work Planned: Stripe and Shopify storefronts for operators who sell what their studio makes.
  • Paid DCC integrations Planned: deeper integrations with the heavier DCC tools.
  • Hosted service add-ons Planned: hosted AI, translation and transcription for operators who would rather not run them.
  • Viewers for proprietary DCC formats View files from proprietary DCC tools without converting them first.
v0.19.0 · planned · AI and creative tools

Optional AI features that an operator chooses to connect: automatic tagging, creative editing, captions generated from speech, and a choice of model for searching by similarity. None of them is required to run Artist Alley.

  • Automatic tagging Suggested tags for new work, from an AI model the operator connects.
  • AI creative editing Generation and variation as an optional capability the operator installs. An experimental image-editing bridge to ComfyUI is already part of the app, off by default.
  • Captions generated from speech Generate captions from the speech in video and audio, correct them in a cue editor, and serve them in several formats. Attaching your own subtitle files has worked since v0.1.0.
  • A choice of model for similarity search Operators choose which AI model powers searching images, video and 3D by similarity. Search by image is partly built but not available yet, because the image model service it depends on has no supported setup.
v0.20.0 · planned · Moving from ResourceSpace

A migration tool for studios moving from ResourceSpace: a companion plugin on the old system, a guided wizard and the migration engine, and checks before switching over.

  • Companion plugin for ResourceSpace A plugin installed on the existing ResourceSpace system to prepare its content for export.
  • Migration wizard and engine An admin wizard that guides the move, and the engine that copies assets and metadata across.
  • Validation and cutover Checks that everything arrived before the old system is switched off.
v0.21.0 · planned · Physical archive mode

Tools for institutions that also look after physical objects: accession records, loans, provenance and condition reports, and common archive standards for exchanging records.

  • Accessions and physical objects Record physical objects with accession numbers and where they are kept.
  • Loans Track objects lent to and borrowed from other institutions.
  • Provenance and condition reports Keep an object's ownership history and record its condition over time.
  • Archive standards Exchange records with other collection systems using common standards.
  • Feature switches for operators An admin screen to turn individual features on and off.
v0.22.0 · planned · Distribution and packaging

Ways to install Artist Alley beyond Docker: native binaries and packages, Windows and macOS installers, a first-run installer, and short-lived demo instances for visitors. Until then Docker is the only way to install it.

  • Native binaries and packages Static binaries plus .deb, .rpm and Homebrew packages.
  • Windows and macOS installers MSI and MSIX packages for Windows, and an app bundle with a disk image for macOS.
  • A first-run installer An installer that works before the database exists, for every way of deploying.
  • Personal demo sandboxes Short-lived demo instances for each visitor, beyond the one shared public demo.
v0.23.0 · planned · Federation between many sites

More of the ArchivePub protocol between studios. Today pairing shares nothing by itself, and likes and comments reach a paired studio only for posts explicitly shared with it; this release plans sharing files between instances, moderation for shared content, an optional directory of instances, and presentation rooms that span instances.

  • Sharing files between instances Paired instances exchange files identified by their content, so a file shared with a partner studio arrives intact and is stored once.
  • Moderation for shared content Hooks that let an operator review and act on what arrives from other instances.
  • An optional directory of instances A curated, opt-in list that helps studios find each other. Instances can already subscribe to a discovery directory and ask to be listed in one, and an official directory is planned for v0.11.5. A directory only suggests studios to pair with; each pairing is still set up by hand.
  • Presentation rooms across instances Review sessions that include people on a paired instance. The real-time transport is not decided yet.
  • Basic fediverse discovery WebFinger and NodeInfo support, so public fediverse software can find an instance and read what it is.
v1.0.0 · planned · Out of beta

The release that ends the beta. Its gates include native packages, full Spanish and French translations, and a contributor agreement for any future relicensing. It also gathers follow-up work on search, IIIF and the phone layout.

  • Full Spanish and French translations Translations of the interface and of server messages beyond the English baseline.
  • A contributor agreement for any future relicensing Contributions are accepted under AGPL-3.0-only today. If commercial licensing is introduced later, a contributor agreement or permission will be in place before any outside contribution is relicensed commercially. No such agreement exists yet.
  • Search follow-ups Synonyms and boosts, and alerts for saved searches.
  • IIIF follow-ups Page-by-page PDF images and text search inside documents for IIIF viewers.
  • A focused phone layout The phone gets a deliberately smaller app; the full set of tools stays on larger screens.

Released

v0.11.1 · released 2026-11-16 · Public CI datasets

Work on the project's test infrastructure rather than the app: public sample datasets pinned by release hash, every automated check moved to GitHub-hosted runners, and a fixed corpus for rerunning flaky tests. It also resolved open security advisories in web dependencies.

  • Reproducible public test datasets Public site_a and site_b sample corpora pinned by release hash and verified before every run, all CI jobs moved to GitHub-hosted runners, and a fixed corpus for repeated runs of flaky tests.
v0.11.0 · released 2026-10-05 · Making and describing work

Helping artists create, describe, organise, find and manage their work without turning the archive into paperwork. Posts gained drafts and scheduling, custom fields gained rules, and changes to many files at once are previewed before they apply.

  • Drafts and scheduled publishing Posts have drafts that stay private until you publish, a full post editor, scheduled publishing and per-post comment controls, with a full-page creation flow beside the quick upload dialog.
  • Custom fields with rules Fields can be required, read-only, conditionally shown, grouped into tabs and validated, and stay editable after upload.
  • Edit metadata across many files Every change is previewed first, with safeguards against stale edits and edits you are not allowed to make.
  • Search by file kind Search understands kinds such as video, 3D, audio and PDF, and richer queries on fields. Advanced search and saved searches also accept commands such as !lastN, !list and !nopreviews; the main search bar is unchanged.
  • 3D models keep their textures A model uploaded with its referenced texture files keeps them together, pages refresh after quick uploads, and owners can see where their files are used.
  • Declared AI provenance Artists can declare work as AI-generated, AI-assisted or made without AI, and browsing can hide purely generated work without hiding mixed or undeclared work.
  • Protected field values stay on the server A field value you may not read is no longer sent to your browser.
v0.10.2 · released 2026-08-19 · Mature-content samples and a roomier cover editor

A patch release. The sample library now shows the mature-content controls working, and the collection cover editor uses the space it has.

  • The sample library shows mature-content controls Twelve public-domain classical works are labelled mature in the sample library, so a fresh install can demonstrate the opt-in, the operator switch, and work staying out of view for viewers who have not opted in.
  • The cover editor uses its room Choosing a cover fills the dialog instead of one clipped row, and the crop area grows once a picture is chosen.
v0.10.1 · released 2026-08-18 · Fixes from two days of real use

A patch release built from working in the app and writing down what got in the way: 28 fixes and refinements across search, browsing, collections and accessibility.

  • Search waits for Enter Suggestions appear as you type and results change when you press Enter. A suggestion never offers a word that finds nothing, and the search button opens a dedicated Advanced search page.
  • Browsing keeps up Endless scrolling loads far enough ahead that fast scrolling never lands on blank space, grid tiles ask for a picture sized to the tile, and the type filter looks inside posts.
  • Visitors can browse public work Marking a post public works, instances that allow it serve public work to visitors without an account, and signed-in members see public work in their own feed.
  • Collections hold posts Loose files stay in your own space until you make them into a post.
  • Covers you choose and crop One cover for the collection card and another for the featured strip, each framed by dragging a crop box with zoom, from the collection, your files or a fresh upload.
  • Every menu works from the keyboard Menus that could not be reached by keyboard, including sign-out, can now, and a test walks the page to keep it that way.
v0.10.0 · released 2026-08-16 · Browsing, discovery and mature content

The browse wall was rebuilt, each view mode got its own design, and mature content became a choice for artists, viewers and operators. Search stopped revealing the titles of work you cannot open.

  • A browse wall that stays put The masonry view places every tile deliberately: no growing gaps, no losing your place when more work loads, no reshuffling under your cursor.
  • Each view mode has its own design Grid is a visual wall with details on hover, thumbnails are a working surface, list is for metadata with resizable columns, and the feed is for reading.
  • Mature content is a choice at every level Artists mark a work at upload, each account chooses whether to see marked work, and the operator chooses whether the instance allows it. Administrators see mature work without opting in, so they can moderate.
  • Teams and tags filter the feed A rail above browsing filters the feed by team, tags can be followed the same way, and the rail is yours to curate.
  • Featured collections and a promo band Featured collections ride a slider at the top of browse, and operators can place a promo band in the feed for signed-in readers or for everyone. A band for everyone reached signed-out visitors from v0.10.1, when they could first load the feed.
  • Select many items at once On the browse feed, drag a box around tiles or shift-click a range and act on all of it. Inside a collection, list view supports a shift-click range but no drag box.
  • Search stopped leaking what it hides A work you are not cleared to see no longer shows up through its withheld title in text search, in tag suggestions, or in counts.
v0.9.1 · released 2026-08-12 · A security patch

A security patch with no functional changes.

  • A fixed YAML parser in the image A YAML parser inside the 3D preview tooling could be made to use too much CPU by a malformed document. Nothing in the product gave it untrusted input, but the copy in the published image is now the fixed version.
v0.9.0 · released 2026-08-11 · One permission rule, reversible deleting and fuller surfaces

Being allowed to change something no longer implies being allowed to see it, deleting can be undone, and surfaces that were half built, such as the feed, were filled in. The image pipeline also stopped running out of memory.

  • Editing no longer implies seeing A team lead can correct a title without being cleared for the artwork behind it, and editing or deleting a file now checks ownership. Team-scoped managers can use that through the API; the web app offers those controls to a file's owner and to instance-wide managers.
  • Deleting is reversible Every account has a trash page with what it deleted and how long is left to recover it, deleting offers Undo, and you can ask for removed work back.
  • A real feed and fuller surfaces The feed shows who made each post with likes, comments and sharing; operators choose which browse layouts their install offers; studios have a home page you can follow; and files have an edit page.
  • Save someone else's post to your collection What lands in your collection is a reference to their post, not a copy, and it changes nothing about who can see it.
  • The image pipeline stopped running out of memory Measured rather than guessed: the same workload went from being killed at its memory limit to finishing with room to spare, at no cost in speed.
v0.8.0 · released 2026-08-03 · Operator configuration

Operators can shape metadata, interface wording and email without forking or restarting, and can delegate field administration without handing over the whole install.

  • Editable vocabularies The options behind select and hierarchical fields are editable in place. Keywords is an open vocabulary: a new term is added as you type it, and keywords are also read from the IPTC metadata in uploaded files.
  • A tree editor for hierarchical fields Nested terms are edited in a tree. The country field ships as a closed tree of 24 countries under 5 continents.
  • Rich-text fields Formatted text is a field type of its own, cleaned on the way in and on the way out.
  • Change the interface wording Operators can override the text the interface ships with, with no restart.
  • Edit the emails the instance sends Every email has an editor, a list of the fields it can use, a sandboxed preview and a way to revert.
  • Field administration can be delegated Creating, editing and deleting field definitions is a capability of its own, granted to the built-in Admin role.
v0.7.0 · released 2026-07-28 · Browse correctness, visibility fixes and a bigger sample library

Cards render at their true proportions, four visibility leaks with one shared cause were closed, the sample library doubled, and the server image halved in size.

  • Cards that render correctly Tiles follow their image's true proportions, the masonry wall stops reshuffling tiles you are looking at, every asset type fades up from a blur, and assets with no preview get a designed tile naming the format.
  • Form controls meet the contrast floor Form control borders now meet the WCAG 2.2 contrast requirement in both themes, with a standard focus ring.
  • Four visibility leaks closed Four read paths had written out the rule for who may see something themselves instead of asking the one component that owns it. Each now asks it. Two further fixes limit who can see session IP addresses.
  • The sample library doubled From 971 assets at v0.6.0 to 1,947, with real work for every studio and the source of every item recorded.
  • A server image half the size Blender is no longer packaged: 3.64 GB to 1.82 GB. Formats with no three.js loader, such as .blend and USD, get no generated thumbnail for now; the files still upload and download normally.
v0.6.0 · released 2026-07-23 · Public profiles and faster 3D previews

Every user has a profile page, the same view controls appear wherever assets are shown, and 3D previews moved to a faster renderer that also works on arm64.

  • Public profile pages A profile page for every user, showing the work a viewer is allowed to see. Owners could opt out of being shown to logged-out visitors only through the API.
  • The same view controls everywhere The view switcher and sort appear on profile and post pages too, not only on the main browse.
  • Faster 3D previews glTF, FBX and OBJ previews render through a headless three.js worker, much faster, and arm64 servers get 3D previews for the first time. Multi-file glTF models render correctly. At this release Blender remained as a fallback; it left the image in v0.7.0.
  • IIIF tiles respect permissions Full-resolution IIIF image tiles are refused to anyone who may not read the asset's content.
v0.5.2 · released 2026-07-21 · Read-only viewers see the whole catalogue

A patch release with a read-only content capability, so the public demo login sees every sensitivity tier without being an administrator.

  • A read-only content capability A role can read asset content at every sensitivity tier and nothing else: no admin screens and no writes.
v0.5.1 · released 2026-07-21 · Shareable asset pages and accumulated groundwork

A patch number but a substantial release: real asset pages, 3D previews on published images for the first time, audit-log retention and export, and the engine behind scheduled actions.

  • Shareable asset pages Every asset has a page that opens, reloads and shares correctly, with a build-time check against dead internal links.
  • 3D previews on published images Turntable thumbnails for 3D models had never generated on released images, because the published image lacked the renderer. This release added it for amd64.
  • Audit-log retention and export Retention periods are stored per event category with a nightly purge that skips events on legal hold, but no screen or API to change them yet. The whole log exports as CSV or NDJSON over a date range.
  • The scheduled-actions engine An engine that runs a stored action at a future time, with an admin API to list and cancel pending actions. Operators could not create scheduled actions in this release.
  • Visibility hardening Deleted collections no longer appear to signed-in non-owners, and the IIIF image path follows the same visibility rule as browse.
v0.5.0 · released 2026-07-21 · Public mode

Content can be reached without an account, on the operator's terms and off by default. A shared visibility rule and stricter checks on content routes also closed three older access holes.

  • Public browsing is the operator's choice A setting, enforced by the API and off on a fresh install, decides whether anonymous visitors are served at all.
  • A shared visibility rule Collections gained a public tier and read paths gained one shared rule to apply. Posts could not be made public through the API until v0.10.1, and some read paths adopted the rule in later releases.
  • Browsing without an account Listing and opening public assets and collections, and loading public images, work without signing in; every write still needs an account.
  • Sensitivity tiers guard content downloads The routes that deliver an asset's files now check the caller's access, including its sensitivity tier, and answer 404 so a hidden asset's existence is not confirmed.
  • Featured work for logged-out visitors Curated content can be featured on the front page for a public audience. Featuring is a placement with its own order, and it never widens who can see an item.
  • Audit-log IP addresses need their own capability Seeing what happened and seeing where it came from are separate grants, enforced by the API.
  • Three older access holes closed Asset and collection details, the collection list and collection contents now all run the same visibility decision.
v0.4.0 · released 2026-07-18 · Operator visibility into jobs and storage

The background job pipeline and the storage layer can be watched and managed from the admin area, and read-only operators can see them without full administrator rights.

  • Jobs admin The queue, workers, live view, failures, per-type concurrency and schedules of the background pipeline are readable with a read capability; requeue, cancel and concurrency edits need full administrator rights.
  • Storage admin Bytes on disk without duplicates, split by originals and derived files, content type and backend, and an inventory of stored versions.
  • Storage integrity sweeps Scans for orphaned files and re-checks stored bytes against their content address. Findings are advisory; no destructive cleanup shipped.
  • The real version in About About reads the running version from a public endpoint, and shows the licence as AGPL-3.0-only.
  • Help for read-only operators Documentation, shortcuts, about, release notes and support are open admin tiles on desktop and mobile.
v0.3.1 · released 2026-07-18 · Admin screens for read-only roles

The admin interface caught up with the read capabilities added in v0.3.0, so a read-only role can browse what its capabilities allow.

  • Admin menu for read-capability holders The admin menu and route guard show each tile to roles holding a matching capability, and the server still enforces every write. One tile, the system log, asked for a different capability than the log it opens.
v0.3.0 · released 2026-07-17 · Thumbnails for seeded content, read-only admin and a responsive interface

Seeded instances get real thumbnails, roles can hold read-only admin capabilities on the server, and the interface works from a phone to an ultrawide screen.

  • Thumbnails for seeded assets Seeding now queues the same preview jobs that uploads have run since v0.1.0, so a seeded instance shows real thumbnails and video hover previews.
  • Read-only admin access on the server Six admin surfaces answer read-only requests without full administrator rights. The admin menu caught up in v0.3.1.
  • A responsive, accessible interface Browsing works from a 390px phone to a 3840px ultrawide with no layout jumps, adds a single-column feed view, and meets WCAG 2.2 AA target sizes for touch.
  • Featured content on a fresh seed The admin Featured rail and the public featured tab both show content on a freshly seeded instance.
v0.2.0 · released 2026-07-16 · First admin tiles and the public demo

The admin area gained its first working tiles, and a public read-only demo started running the release image.

  • The first working admin tiles An audit-log viewer, sessions and capability grants per user, resource requests, trash with restore, and an API explorer served by the server. 37 tiles were live and 65 were still marked as future work.
  • Demo mode An environment switch that adds a sign-in hint and a read-only banner for everyone signed in. Off by default, with nothing left behind on real installs.
  • A public read-only demo At this release, demo.artist-alley.org ran the release image behind a write-blocking edge, seeded and set to redeploy on each release.
v0.1.2 · released 2026-07-15 · Brand palette and job fixes

A patch release with the final brand palette, a fixed install quickstart, fixes to job concurrency and saved-search scheduling, and dependency upgrades.

  • The brand palette The final chevron mark, the burnt and steel colours checked for contrast, and the configured site name used throughout.
  • A working install quickstart The quickstart's master-key instructions, image path, signing identity and database extension setup were corrected.
  • Job and saved-search fixes Per-type job concurrency limits apply in the worker pool, and the saved-search scheduler no longer spins.
v0.1.1 · released 2026-07-13 · Media processing fixed

A patch release that fixed background processing on fresh installs, fixed release image publishing and cleared open dependency advisories. Anyone on v0.1.0 should upgrade.

  • Media processing works on a fresh install The worker pool never claimed jobs on a fresh install, so no thumbnails, previews, transcripts or search embeddings were made.
  • Release images publish again Edge and release image builds failed after the organisation rename and were fixed.
  • Dependency advisories cleared Every open advisory in the shipped image and the optional image-search helper was fixed.
v0.1.0 · released 2026-07-12 · The first tagged release

The versioned baseline: one server binary, accounts and roles, upload with posts and collections, custom metadata, a viewer for many file kinds, and the first studio-to-studio connection. Released under AGPL-3.0-only.

  • One server binary One Go server with the web app built in, plus Postgres and a storage volume, which can be a filesystem or any S3-compatible bucket.
  • Accounts, roles and capabilities Sessions, API tokens, roles and capabilities, and password policy. A token carried its account's own capabilities; scopes could be recorded on a token but were not enforced. A screen for single sign-on providers existed, but none could sign anyone in.
  • Upload, posts and collections Drag-anywhere upload with a background queue and per-file tags and metadata. Posts wrap assets, collections wrap posts, and full-text search spans all of it.
  • Custom metadata fields Operators define typed custom fields for asset types and for collections, with audit history. Each field can name read and write capabilities; the write capability was enforced from this release, the read capability on asset fields from v0.11.0.
  • One viewer for many file kinds Images including HDR and EXR, HLS video with frame-accurate scrubbing, audio waveforms, multi-page PDF, font specimens, and 3D viewers for glTF, GLB, OBJ and FBX. 3D preview thumbnails did not reach published images until v0.5.1.
  • Subtitles and sprite sheets Video and audio show subtitle tracks in the player, including subtitle files in SRT, SSA, ASS, SUB or VTT uploaded through the API and converted to WebVTT. Sprite sheets play frame by frame.
  • The studio-to-studio connection (ArchivePub) Instances could pair with each other over ArchivePub, with requests signed per instance, one inbox per instance, a delivery worker and admin views of the delivery queues, and accounts could rotate their own keys. Signatures for individual accounts were placeholders. The protocol spec stood at v1.0-rc1. No user action crossed instances in this release.
  • Admin and account areas, themes and languages An admin menu for full administrators with real settings screens, an account area with profile, theme, language and API tokens, light and dark themes, and English with Spanish and French placeholders.
Terms used on this page
AGPL-3.0
The open-source licence Artist Alley is released under. Anyone can run, study and change it; changes offered to others over a network must be shared under the same licence.
ArchivePub
The open protocol Artist Alley instances use to talk to each other, defined by the project. It borrows ActivityPub's model, with additions for sharing assets, but doesn't connect to ActivityPub servers such as Mastodon.
arm64
The processor type used by many newer servers and by Apple and Raspberry Pi hardware, as opposed to the older amd64 (x86) type.
Capability
A named permission, such as reading the audit log, that a role can be granted. Artist Alley checks capabilities on the server.
DCC tools
Digital content creation tools: the 2D and 3D programs artists make work in, such as Blender, Maya or Photoshop.
Federation
Separate Artist Alley instances, each run by its own studio, connecting to each other directly. Today pairing shares nothing by itself: likes and comments reach a paired studio only for posts explicitly shared with it, and sending assets and posts between instances is planned.
Fediverse
The wider network of independent social servers that speak ActivityPub, such as Mastodon.
glTF
An open file format for 3D models and scenes (also GLB, its single-file form).
HLS
HTTP Live Streaming: video split into small pieces at several qualities, so playback adapts to the connection.
IIIF
The International Image Interoperability Framework: an open standard that lets image viewers used by museums and libraries load images from any server that supports it.
IPTC
A standard for descriptive metadata, such as keywords and captions, embedded inside image files.
MCP
The Model Context Protocol: an open way for AI tools to read from, and act on, other software.
Mature content
Work an artist marks as mature. Each account chooses whether to see it, and the operator chooses whether the instance allows it at all.
NDA
Non-disclosure agreement: work that may only be shown to people cleared to see it.
Operator
The person or team who runs an Artist Alley instance and administers it.
Paired instance
Another studio's Artist Alley instance that yours has agreed to connect with over ArchivePub.
PBR
Physically based rendering: lighting and materials in a 3D viewer that behave like real surfaces.
ResourceSpace
An open-source digital asset management system that some studios use today and may move from.
Sensitivity tier
How an asset's content is restricted: public, team, restricted or embargo. Restricted and embargoed content can be read by its owner, administrators and roles explicitly granted access across all sensitivity tiers.
WebVTT
The standard text format web browsers use for subtitles and captions.

The full development log, with every phase, arc and pull request, is docs/roadmap.md in the repository.