|
<< Click to Display Table of Contents >> Raynet One > 2026.1 > Installation and Operations Guide > Raynet One On-Premises Installation and Operations Guide Service Overview |
The on-premises deployment of Raynet One consists of the following services that together provide the full functionality of the system.
The following table gives an overview of the main services, their container names and primary responsibilities:
Service |
Container Name |
Description |
|---|---|---|
Nginx Proxy |
•nginx-proxy |
•Entrypoint for all HTTP/HTTPS traffic. Handles SSL termination and routing. |
Keycloak |
•keycloak |
•Identity and Access Management (IAM). Handles Single Sign-On (SSO). |
Backend |
•server-backend |
•Core application logic and API. |
Frontend |
•server-frontend |
•Web user interface. |
Scheduler |
•server-scheduler |
•Handles background jobs and scheduled tasks. |
DataHub |
•datahub |
•Data integration and inventory management service. |
MinIO |
•minio |
•S3-compatible object storage. |
Vault |
•vault |
•Secrets management. |
Databases |
•server-database, keycloak-database, mongodb, redis |
•Persistent storage for various services. |
RabbitMQ |
•rabbitmq |
•Message broker for inter-service communication. |
Service names, container names, and persistence mappings are fully defined in compose.yml. For details on how these services interact, refer to the sections Setup and Configuration, Deployment and Troubleshooting.