How privateaim/hub works
FLAME Hub coordinates federated analysis: users create projects and analyses in the web UI, the core API manages their configuration and participating nodes, and background workers build and distribute analysis images. Nodes execute analyses locally so underlying data stays at the institution; results and files are collected through storage, with logs and events handled separately. The README documents the product workflow and service capabilities; sampled controller code confirms core service wiring and storage, telemetry, and messenger service entry points. Some cross-service links reflect documented behavior rather than inspected implementation.
Main entry points: server-core Core API · client-ui Web application · controller.ts Core domain services · app Background worker
Components 23
User experience
- Web application
apps/client-ui - Projects and nodes
apps/client-ui/pages/projects - Analysis workspace
apps/client-ui/pages/analyses - Administration
apps/client-ui/pages/admin
Core coordination
- Core API
apps/server-core - HTTP controllers
apps/server-core/src/adapters/http/controllers - Core domain services
apps/server-core/src/app/modules/http/controller.ts - Core database
apps/server-core/src/adapters/database - Registry management
apps/server-core/src/app/components/registry
Analysis execution
- Background worker
apps/server-core-worker/src/app - Analysis image builder
apps/server-core-worker/src/app/components/analysis-builder - Analysis distributor
apps/server-core-worker/src/app/components/analysis-distributor - Docker integration
apps/server-core-worker/src/adapters/docker
Platform services
- Storage service
apps/server-storage - Telemetry service
apps/server-telemetry - Messenger service
apps/server-messenger
External infrastructure
- Authup identity
- Message broker
- SQL database
- Object storage
- VictoriaLogs
Other components
- Researcher / admin
- Institution nodes
Connections 27
- Researcher / admin → Web application: uses
- Web application → Projects and nodes: opens
- Web application → Analysis workspace: opens
- Web application → Administration: opens
- Projects and nodes → Core API: manages projects
- Analysis workspace → Core API: submits analysis
- Administration → Core API: administers
- Core API → HTTP controllers: routes requests
- HTTP controllers → Core domain services: invokes
- Core domain services → Core database: reads and writes
- Core domain services → Registry management: manages registries
- Core domain services → Background worker: dispatches tasks
- Background worker → Analysis image builder: builds images
- Background worker → Analysis distributor: distributes analyses
- Analysis image builder → Docker integration: builds containers
- Analysis distributor → Docker integration: pushes images
- Analysis distributor → Institution nodes: ships analysis
- Institution nodes → Storage service: uploads results
- Web application → Storage service: manages files
- Core API → Telemetry service: records events
- Core API → Messenger service: exchanges messages
- Core API → Authup identity: authenticates
- Core API → Message broker: publishes tasks
- Background worker → Message broker: consumes tasks
- Core database → SQL database: persists entities
- Storage service → Object storage: stores files
- Telemetry service → VictoriaLogs: stores logs