📄️ User Svc
The user service is at the heart of OpenOrch, managing users, tokens, organizations, permissions and more. Each service and human on an OpenOrch network has an account in the User Svc.
📄️ Secret Svc
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.
📄️ Config Svc
The Config Svc stores public, non-sensitive and end-user-facing data.
📄️ Registry Svc
The registry service is designed to maintain a database of services, service instances and nodes.
📄️ Deploy Svc
The deploy service is responsible of launching containers on whatever infrastructure the OpenOrch is running on (eg. Docker Svc) and registering them into the Registry Svc.
📄️ Download Svc
The download service keeps a network local copy of files frequently accessed by services in the OpenOrch platform.
📄️ Policy Svc
The policy service provides features such as rate limiting of endpoint calls by user ip, user id, organization id and more.
📄️ Prompt Svc
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.
📄️ Model Svc
The model service can start, stop AI models across multiple runtimes (eg. Docker) and maintains a database of available models on the platform.
📄️ Dynamic Svc
The dynamic service is designed to help build backendless applications: the goal is to be able to save and query data directly from the frontend. Similarly to Firebase.
📄️ Docker Svc
The docker service maintains containers on a node. It expects the docker socket to be mounted.
📄️ Chat Svc
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.