A private Unity Asset Store
An internal asset library for a research lab — with editor plugins that pull assets straight into Unity and Unreal.
Four repositories, one product: a NestJS API, a Next.js client, and native editor plugins for Unity and Unreal so an artist never leaves their tool to fetch an asset.
The interesting half is the pipeline. Every upload runs through BullMQ workers — analyser, antivirus scan, glTF conversion, thumbnail generation, search indexing, notification fan-out and archive purge — across Postgres, MongoDB, Redis, S3 and Meilisearch, with a WebSocket gateway pushing progress back to the browser.
Keycloak gates everything except the about page. Admin actions are audit-logged by interceptor, destructive ones need explicit confirmation, and the API ships as two images so workers scale separately from the request path.
where the effort went
the numbers
API · web · Unity · Unreal
PG · Mongo · Redis · S3 · Meili
built with
delivery record
Artists and developers needed one governed source for reusable assets without leaving Unity or Unreal to browse, download, and unpack files manually.
Web catalog and NestJS asset API
Native Unity and Unreal editor integrations
Eight-stage asynchronous analysis and publishing pipeline
Antivirus, glTF conversion, thumbnails, indexing, and archive cleanup
Keycloak access control and auditable administration
Independent API and worker images for separate scaling
The constraints mattered as much as the finished interface.
after shipping
An asset library is a processing and trust pipeline before it is a catalog.
Editor integrations succeed when authentication and downloads feel native to the tool where artists already work.