9 docs tagged with "services"

The chat service keeps a database of threads, messages and file assets associated with them. Chat messages are the primary user interface of LLMs and other AI architectures.

The Config Svc stores public, non-sensitive and end-user-facing data.

The container service maintains containers on a node. It currently only supports Docker. It expects the Docker socket to be mounted.

The Data Service (Data Svc) is designed to facilitate backendless applications, allowing data to be saved and queried directly from the frontend, similar to Firebase.

The deploy service is responsible of launching containers on whatever infrastructure the 1Backend is running on (eg. Docker Svc) and registering them into the Registry Svc.

The File Service handles file-related operations, including downloading files from the internet (to cache them for faster access), accepting file uploads, and serving both downloaded and uploaded files.

The model service can start, stop AI models across multiple runtimes (eg. Docker) and maintains a database of available models on the platform.

The prompt service provides an easy to use interface to prompt LLMs and use AI models. Aims to serve humans and machines alike with its resilient queue based architecture.

The Secret Svc stores sensitive or internal (non-end-user-facing) configuration. Aims to store all configuration not required at bootstrap, both for internal and external services.