FAQs

•    A. INFLOWe goes beyond the status quo of traditional DAMs and Digital Archives. It is not a content management system — it is a creative research environment. Where a DAM organises and stores assets for retrieval, INFLOWe is built around exploration, inspiration and cross-pollination. It is designed for the way designers think — by image, by association, by visual intuition — not for the way IT systems catalogue files. The AI classification, the visual search, the moodboard tools: everything is built around the creative workflow, not the archival one.
  

•    A. Pinterest is a public discovery tool built around external content. INFLOWe is a private research environment built entirely around your brand's own visual identity and heritage. The logic of exploration may feel similar — intuitive, image-driven, associative — but everything else is different: the content is yours, the AI has been trained on your archive, and the platform goes far deeper, respecting the full complexity and semantic richness of your brand — its codes, its materials, its historical references, its visual DNA.
  
  INFLOWe doesn't show you what the world finds interesting. It illuminates what is already yours — connections, patterns and references that were always in your archive, waiting to be found.
  

•    A. INFLOWe uses AI exclusively for classification, search and discovery — not for generating content. Our models are not generic: each is fine-tuned on your brand's specific archive, trained on your visual identity codes and proprietary taxonomy.
  
  Concretely, we use custom-developed Machine Learning models to:
     - generate granular and highly accurate tagging of every visual asset
     - enable visual search — finding images using an image as the query 
     - surface connections and patterns across the archive that manual search would miss.
  
  INFLOWe's AI does not create images, does not suggest creative directions, and does not replace the designer's judgment. It makes the archive more accessible and more searchable — so the creative act remains entirely human.
  

•    A. Your heritage data is among your brand's most sensitive assets — and we treat it accordingly. Every INFLOWe implementation runs on a dedicated, isolated infrastructure hosted on AWS, with no data shared across clients. Access is governed by role-based authentication protocols that ensure only authorised team members can view or interact with your content.
  
  Your archive, your taxonomy, your Machine Learning models: they are yours exclusively. Brandcraft operates as a custodian, not an owner. We do not use client data to train shared models or for any purpose beyond delivering the agreed service.
  
  Security is not a feature — it is the foundation on which INFLOWe is built.
  

•    A. INFLOWe is provided as Software as a Service (SaaS) through the Web and does not require an on-premise installation. This modality facilitates software updating and the release of new functionalities.
  

•    A. INFLOWe is designed to be modular to tailor the investment to your actual needs.
  

• We start with a Core module that provides exploration of visual assets, creation and sharing of moodboards, and creation of Stories for internal use.

• We can modularise within the Core module based on resource type (e.g., Images or Videos) and product categories (Ready-to-wear, Bags, Shoes, Jewelry, etc.).

• The Press-Kit and Archive Item Loan modules are separate functionalities that can be activated immediately or at a later stage.

•    A. INFLOWe is designed to integrate with existing brand systems through API technology. The integration enables the automatic upload of new assets (e.g., new collections) and data alignment — avoiding inconsistencies and manual rework.
  

•    A. During the setup phase, the Brand team provides Brandcraft with all the relevant images and metadata. Brandcraft releases INFLOWe complete with all digital assets fully tagged by our AI models and integrated with the Brand's metadata. Brandcraft and the Client's IT team collaborate to configure the API protocol for automatic data exchange with local DAMs, PIMs, or other existing systems.