Documentation · Service Catalog
18 services, one inventory, health and operations model
The catalog does not replace specialist managers: it unifies discovery, backend, version, readiness and constrained lifecycle at fleet level.
Verified against public version: 0.20.02026-09-15Factual boundary · roadmap is not presented as shipped
The Sysaro Service Catalog contains exactly 18 required profiles. Deep configuration for mature subsystems remains in Web Stack, Runtime, Data Services or Processes; the catalog provides a unified fleet-level view and operations layer.
Catalog
| Area | Current boundary |
|---|---|
| nginx | Deep · Web Stack |
| PHP-FPM 8.5 | Deep · Runtime/Sites |
| PostgreSQL 18 | Deep · Data Services |
| Valkey | Deep · Data Services |
| Temporal Server | Inventory/readiness + typed preview |
| ClickHouse | Typed config + readiness |
| S3-compatible storage | Endpoint + typed local MinIO |
| Node.js LTS | Deep · Runtime |
| FFmpeg + FFprobe | Inventory completeness |
| Remotion render worker | Managed Process preset |
| OpenTelemetry Collector | Typed config + validation |
| Prometheus | Typed config + promtool |
| Grafana | Typed environment + datasources |
| Loki | Typed config + verification |
| Tempo | Typed config + verification |
| systemd | Managed processes/units |
| Docker / OCI runtime | Backend-aware lifecycle |
| GitLab Runner | Inventory + constrained lifecycle |
Same surface, different management depth
A discovered service is not presented as fully managed. The UI exposes management depth, backend and readiness separately.
The Agent and Control Plane have an automated parity gate so required service IDs cannot silently diverge.