Service Level Objectives are specific, measurable targets the operator aims to maintain. Unlike the SLA — which describes how the service operates and what happens when things go wrong — the SLO gives concrete numbers to set expectations against.
These targets are best-effort goals on residential infrastructure, not contractual commitments. They exist so users have a realistic picture of what the service is designed to deliver. Falling below an objective triggers investigation and best-effort correction — not compensation of any kind.
Key targets across all service categories at a glance:
| Service Tier | Target Uptime | Max Downtime / 30 Days |
|---|---|---|
| Core (VPN, auth, networking) | 95%+ | ~36 hours |
| Standard (Emby, Jellyseerr, File Browser) | 95%+ | ~36 hours |
| Experimental (AI, dev, test) | No target | No guarantee |
Planned maintenance windows and ISP or power events outside the operator's control are excluded from uptime calculations. Actual uptime typically exceeds these targets during stable periods.
| Objective | Target | Notes |
|---|---|---|
| Concurrent streams per user | 1 (default) | Additional streams available by operator approval only |
| Default playback quality | 1080p | Clients should prefer direct play at this resolution |
| 4K playback | Direct play only | 4K transcoding is not supported and will not be accommodated |
| Transcoding availability | Best effort | High-load sessions may be throttled to protect system performance |
| Total simultaneous transcodes | 2–3 max system-wide | Subject to hardware capacity — direct play is always preferred |
| Data Type | Backup Frequency | Retention Target | Recovery Guarantee |
|---|---|---|---|
| Media Library | None | None | None — content may be lost |
| User Files | Daily | 7 rolling days | Best effort on request |
| System Configuration | Daily | 7 rolling days | Operator-managed — not user-facing |
The 7-day retention window means a backup from 8 or more days ago may no longer be available. Do not rely solely on this platform for anything you cannot afford to lose.
| Priority | Trigger | Response Target |
|---|---|---|
| P1 — Critical | Full system offline — VPN and all services unreachable | 12–24 hours |
| P2 — Major | Emby, Jellyseerr, or File Browser down | Within 24 hours |
| P3 — Minor | Degraded performance, slow streaming, isolated feature broken | Best effort — no committed timeline |
The operator is a single individual with other personal and professional commitments. Response times may be longer during evenings or travel. Reporting issues via Discord gives the fastest path to resolution.
If a service consistently falls below its availability target or response objective, the operator will:
There is no compensation, credit, or service guarantee tied to these objectives. They exist to set honest expectations, not to create entitlements. If the service is not meeting your needs on a sustained basis, the appropriate path is to discuss it with the operator or request account removal.