Architecture overview
The customer installation is a complete application core. Feature visibility and entitlement are controlled separately by the signed License Authority policy.
Core customer services
| Component | Service / port | Responsibility |
|---|---|---|
| E4S Web | e4s-web.service / 18080 |
Panel, UI, API routes and application web runtime. |
| E4S Agent API | e4s-agent-api.service / 18081 |
Agent communication, telemetry and agent-facing operations. |
| E4S Worker | e4s-worker.service |
Background processing and asynchronous platform work. |
| PostgreSQL | 5432 | Persistent application data. |
| Redis | 6379 | Cache and runtime acceleration. |
| Nginx | 80 / 443 | HTTPS termination, reverse proxy and static delivery. |
External authorities
Layer1 Distribution
Publishes Universal installers, catalog metadata, SHA256 values, Ed25519-signed manifests and documentation.
License Authority
Returns signed feature entitlement, limits, subscription status, check interval and offline lease information.
Update Authority
Handles signed software update delivery independently from license feature changes.
Important filesystem paths
| Path | Purpose |
|---|---|
/opt/e4s-monitor | Main E4S application. |
/opt/e4s-frontend/public | Public frontend. |
/etc/e4s-monitor | System-level E4S configuration. |
/var/lib/e4s-monitor | Persistent runtime state. |
/root/e4s-install-credentials.txt | Fresh-install credentials. |
/backup | Operational backups created by platform tooling. |