This SLA describes the operational expectations, infrastructure limitations, response procedures, and data handling practices for Lylexx Service Hosting. It is an operational document, not a legal contract, and creates no binding obligations or entitlement to compensation. For specific measurable targets refer to the SLO.
All services are hosted on privately owned residential hardware connected via a consumer ISP. This is a personal homelab — not a data center or commercial cloud environment. Downtime may result from:
Services are grouped into three operational tiers. Restoration priority follows this order in the event of an outage.
| Tier | Services | Stability |
|---|---|---|
| Core P1 | VPN, authentication, Cloudflare Tunnel | Restored first — required for all other services |
| Standard P2 | Emby, Jellyseerr, File Browser | Restored after core — best-effort uptime per SLO targets |
| Experimental P3 | AI/LLM systems, dev containers, test environments | No stability guarantee — may be removed without notice |
Admin-facing services (Radarr, Sonarr, Portainer, Grafana) are Priority 2 but are not user-facing and their availability does not affect user service access.
The operator targets 95% uptime or higher for Standard tier services on a rolling 30-day basis. This is a best-effort goal — not a binding commitment — and no compensation is offered for periods below this target. Planned maintenance, ISP outages, and power events are excluded from calculations where reasonable.
Service recovery is performed on a best-effort basis by a single operator. The following are goals, not guarantees.
| Severity | Example | Target Response |
|---|---|---|
| Critical P1 | Entire system offline, VPN inaccessible | 12–24 hours |
| Major P2 | Emby or core user service down | Within 24 hours |
| Minor P3 | Isolated degradation, single feature broken | Best effort — no guaranteed timeline |
The operator is a single individual with other personal and professional commitments. Response may be longer during evenings or travel. Reporting issues via Discord is the fastest path to resolution.
The system logs operational data to maintain stability and detect misuse.
| Data Type | Purpose |
|---|---|
| Device type & client app | Compatibility diagnostics |
| VPN connection metadata | Access monitoring, troubleshooting |
| Playback method | Performance and resource management |
| Media titles & timestamps | Usage patterns, abuse detection |
| Connection metadata | Network diagnostics |
Logs are not sold or shared with any third party. Access is limited to the operator for administrative purposes only. Logs may be retained for a reasonable period as determined by operational needs.
| Data Type | Backup Policy | Retention |
|---|---|---|
| Media Library | No backup | Not guaranteed to persist |
| User Files | Daily automated backup | 7-day rolling window |
| System Config | Daily automated backup | 7-day rolling window |
Service announcements, outage notices, and maintenance updates are distributed via the operator's Discord server. Users are responsible for monitoring that channel. For urgent issues, contacting the operator directly via Discord is most reliable.
Lylexx Service Hosting is a private, non-commercial service provided free of charge. No compensation, credit, refund, or alternative remedy is available for any period of downtime, data loss, or degradation regardless of cause or duration. If service quality is consistently unsatisfactory, the appropriate recourse is to request account removal.