The workflow before the tools
This starting Recipe maps the work a creator is trying to do to the capabilities and Rolls that support it. The workflow does not publish, deploy or approve anything merely because the required tools are present.
Required capabilities: resolved · release/deployment authority: not evaluated
- 01Human review
Preserve the original
Accept the creator's asset into private storage while preserving the original bytes and durable asset/workflow state.
cap.asset-managementuramaki.lycheecap.object-storagefutomaki.rustfscap.databasefutomaki.postgrescap.workflowhosomaki.n8n - 02Automatic
Read source metadata
Extract embedded EXIF, IPTC and XMP facts without mixing inference into source metadata.
cap.image-metadatauramaki.exiftool - 03Automatic
Make working derivatives
Create thumbnails or normalized derivatives while keeping the original unchanged.
cap.media-processinguramaki.imagemagick - 04Human approval
Organize and review
Let the creator inspect metadata and derivatives, organize the work and decide what should continue.
cap.asset-managementuramaki.lycheecap.workflowhosomaki.n8n - 05Human review
Optionally add local intelligence
Generate creator-reviewable captions, tags, classifications or embeddings without changing source metadata authority.
cap.llm-api · optionalhosomaki.ollamacap.embeddings · optionalhosomaki.ollama - 06Automatic
Index approved searchable text
Index approved deterministic and creator-approved enriched text for semantic retrieval.
cap.vector-db · optionalfutomaki.qdrant
Adapt Creator Asset Studio.
You started from a complete Recipe, so the technology is already here for a human reason. Inspect those reasons, remove or replace anything you do not want, then save the result as the canonical Recipe or as your own explicit Variant.
Try the free Local Chat starter84 of 93 rolls are open both ways, so the choice stays open until you make it. Nothing is hidden from the shelf — the board warns instead.
Keeps albums, provenance, workflow state and normalized metadata durable.
Relational database with strong SQL conformance, MVCC transactions and an extension system. This image ships the pgvector extension, adding vector columns and approximate nearest-neighbour search.
Stores original and derivative bytes through the accepted portable S3 path.
Maintained Rust object storage with a tested S3-compatible API subset for bucket and object workflows.
Gives the creator a human place to upload, browse, organize and review assets.
Self-hosted photo and visual-asset manager for uploading, organizing, browsing and sharing media.
Reads embedded EXIF, IPTC and XMP facts without pretending inference is source truth.
Command-line metadata engine for reading, writing and normalizing EXIF, IPTC, XMP, GPS, ICC, maker notes and other embedded metadata across photographs, illustrations and many other file types.
Creates thumbnails and derivatives while leaving the canonical original unchanged.
Command-line image toolkit reading and writing over 200 formats, with conversion, resizing, composition, colour correction and effects, suitable for scripted batch processing.
Orchestrates ingestion, retries, organization and enrichment steps.
Workflow automation platform with 400+ service integrations, extensible in JavaScript. Runs event-driven and scheduled flows across APIs, databases and model endpoints.
Provides optional local model inference for creator-approved captions, tags and classification.
Local runtime that downloads, quantises and runs open-weight language models, exposing them over its own HTTP API and an OpenAI-compatible endpoint. Also serves embedding models.
Indexes approved/enriched text so assets can be found by semantic meaning.
Vector database written in Rust, pairing dense and sparse vectors with structured payloads so that metadata filters and nearest-neighbour search are resolved together in a single query.
Inspect Creator Asset Studio. Save when you are ready.
This starts from jubako.creator-asset-studio, so every Roll arrives with a human-readable reason. You can inspect or change it here without an account; the Recipe identity and your exact Roll choices are carried into the portal.
Every declared Roll requirement is currently satisfied.
1 Roll has a closed delivery path under the current delivery choice.