Showcase
Uses & for whom¶
Who benefits from CatalogueCanvas, and the concrete jobs it does for them.
Who it's for¶
Artists & illustrators¶
Catalogue a body of work, keep notes and metadata per piece, and publish a clean public portfolio without building a website.
Generative & creative coders¶
Each ZIP can hold the rendered image plus the source (.py, .r, .js, .p5, .json, …), keeping output and code together as one item.
Designers¶
Organise design assets into collections, tag them, and share curated sets privately or publicly.
Studios, archives & small teams¶
A self-hosted, low-footprint catalogue that lives on your own hardware — no SaaS, no per-seat cost.
Self-hosting enthusiasts¶
Runs in one Docker container with SQLite; full export/backup built in.
What you can do with it¶
| Goal | How CatalogueCanvas helps |
|---|---|
| Keep a private master catalogue of work | Ingest ZIPs, tag, note, organise into collections |
| Pair finished work with its source files | Multiple files per item, viewable or downloadable |
| Auto-generate descriptions | Vision LLM (OpenAI-compatible, local or hosted) |
| Share a curated showcase | Public portfolios at /p/<slug> |
| Store work across discs | Multiple libraries |
| Protect your data | One-click database + full-asset backup |
When it may not be the right fit¶
- You're cataloguing a photo library — for that, use a dedicated photo manager like Immich. CatalogueCanvas is built for digital art, illustration, and generative/algorithmic work, not photo collections.
- You need fine-grained per-user permissions beyond the two built-in roles (multi-user mode offers Admin and view-only Reader, plus public portfolio viewers).
- You want a hosted/managed SaaS with no self-hosting.