ATRIA Model Gateway operational overview

Operational workflow

The operational flow between an application (for the communication with aura-gateway-apì), atria-model-gateway, atria-rag-server and atria-rag-generate-db is schematically shown in the following figure:

• Application

  • Constructors must configure an application for a channel, skill or service to communicate with aura-gateway-api.
  • In the application, the constructor must set the access grants for this application and all the presets that this application can use, from the ones configured in atria-model-gateway.
    
    

• atria-model-gateway It contains:

  • The different accesses that are defined here for each preset.
  • The available presets. Each of them is associated to an AI model with specific parameters.
  • The available AI models.
    
    

• atria-rag-server

  • When using RAG (Retrieval Augmented Generation), atria-rag-server is in charge of managing the requests made to the RAG model.
  • The available projects that contain information required for the execution of the RAG pipeline are included here.
    
    

• atria-rag-generate-db

  • atria-rag-generate-db is in charge of feeding the databases the RAG works with.
  • The available projects that contain the data required for reading the information sources and feed the databases are included here.

Configuration

atria-model-gateway includes a default configuration. Constructors can use it as is or they can modify it to be adapted to their requirements or business models: Go to document ATRIA configuration.