Operate Linux infrastructure from one control plane
Sysaro brings sites, runtimes, databases, systemd processes, DNS, TLS, deployments, backups and infrastructure services into one Control Plane backed by a privileged Go Agent and typed operations.
The public site describes implemented boundaries only. Roadmap items are not presented as shipped features.
Typed operations
The Agent receives explicit contracts instead of a universal root command.
Transactional config
Preview, native validation, readiness and rollback for managed configuration.
Service Fleet
18 service profiles under one inventory, health and lifecycle layer.
Managed stack
From the web stack to observability and render workers, with management depth stated explicitly.
| Service | Depth | Surface | Managed scope |
|---|---|---|---|
| nginx | Deep | Web Stack | Inventory, site config, validation, reload and rollback |
| PHP-FPM 8.5 | Deep | Runtime / Sites | Version policy, pools, isolation and structured tuning |
| PostgreSQL 18 | Deep | Data Services | Inventory, lifecycle, DB/access/backup and version policy |
| Valkey | Deep | Data Services | Redis-compatible lifecycle, topology and health |
| Temporal Server | Preview + ops | Service Fleet | Readiness and typed PostgreSQL deployment profile; apply awaits canonical OCI ownership |
| ClickHouse | Typed config | Service Fleet | Sysaro-owned fragment, validation, readiness and rollback |
| S3-compatible storage | Typed + endpoint | Object Storage | Local MinIO typed config; external S3 endpoint and SigV4 health |
| Node.js LTS | Deep | Runtimes | LTS verification and exact runtime binding |
| FFmpeg + FFprobe | Operations | Service Fleet | Completeness and inventory |
| Remotion render worker | Managed process | Processes | Preset, Node runtime and systemd/cgroups |
| OpenTelemetry Collector | Typed config | Observability | Contrib profile, validate, readiness and rollback |
| Prometheus | Typed config | Observability | promtool validation, readiness and rollback |
| Grafana | Typed config | Observability | Managed environment and declarative datasources |
| Loki | Typed config | Observability | Config verification, OTLP topology, readiness and rollback |
| Tempo | Typed config | Observability | Config verification, OTLP topology, readiness and rollback |
| systemd | Deep | Processes | Managed units, timers, cgroups and journald; PID 1 lifecycle is blocked |
| Docker / OCI runtime | Operations | Service Fleet | Canonical OCI workload lifecycle; generic container command is blocked |
| GitLab Runner | Operations | Service Fleet | Inventory/lifecycle/readiness; typed registration/config remains on roadmap |
Control Plane + Go Agent
The web Control Plane does not receive direct root privileges. The privileged Agent executes constrained operations and returns verifiable results.
- mTLS Agent identity
- RBAC + audit trail
- managed config ownership
- health/readiness verification
- rollback on failure
Quick start
One command installs Sysaro on a local AlmaLinux 10 server; no domain or public IP is required.
$ curl -fsSL https://sysaro.webrove.tech/install.sh | sudo shA tagged production release still requires a real composer.lock and bundled vendor; production-beta is not presented as final certification.
Direct answers for operators
The wording is intentionally precise so humans can scan it and search/AI systems can extract it without losing context.
Does Sysaro require SSH for daily operations?
Routine operations are designed to be UI-first. SSH remains an administrator tool for emergency diagnostics and tasks outside supported typed workflows.
Is Sysaro a SaaS?
No. The Control Plane is self-hosted. Vendor endpoints are limited to the public product site, optional bootstrap and the signed update registry.
Can Sysaro adopt an existing server?
Yes. Discovery and adoption are separate: passive scan and fingerprint first, review second, managed takeover only after that.
From individual services to operational stacks
Focused pages explain how services fit together and state the actual management depth without inventing production guarantees.
PHP + PostgreSQL + Valkey
Site, runtime, data services, deployment, backup and aggregated health.
Open use case →Temporal + PostgreSQL
Readiness and typed deployment boundary without unsafe assumptions about existing installs.
Open use case →Remotion + Node + FFmpeg + S3
Managed worker, exact runtime binding and object storage.
Open use case →Public technical evidence
Architecture claims are exposed as indexable documents with version/dateModified metadata so they can be checked and cited accurately.