kakariko
Private app dashboard at apps.chrisalvis.me
🔒 How access works
Every app is protected by Cloudflare Access — a zero-trust layer that sits in front of the entire platform. There are no open ports, no shared passwords, and no way in without a verified device or identity. To use the dashboard at apps.chrisalvis.me, you first need to be granted access one of the ways below.
📱 Option 1 — WARP Recommended
Cloudflare WARP is a lightweight client that enrolls your device with the zero-trust network. Once enrolled, your device is recognized automatically — no login prompts, no re-authentication. Just open the app and everything works.
iPhone / Android
- Install the 1.1.1.1 / WARP app
- Tap the menu → Account → Login with Cloudflare Zero Trust
- Enter organization:
alvisleet - Sign in with your Google or GitHub account
- Toggle WARP on — you're in
Windows / macOS / Linux
- Download Cloudflare WARP for desktop
- Click the tray icon → Preferences → Account → Login with Cloudflare Zero Trust
- Organization:
alvisleet, sign in with Google or GitHub
🌐 Option 2 — Browser login
No VPN required. When you visit apps.chrisalvis.me without an enrolled device, Cloudflare Access will intercept the request and present a login page. Authenticate with:
- Google — any authorized Google account
- GitHub — any authorized GitHub account
Cloudflare issues a short-lived session token on sign-in. You'll need to re-authenticate periodically.
📺 Smart TVs & consoles
WARP doesn't have a native client for smart TVs, game consoles, or similar devices. Options:
- Router-level WARP — enroll your router so your entire home network is covered, no per-device setup needed
- WARP Connector — a lightweight VM or container that acts as a WARP gateway for a subnet
🛡️ Security model
The platform runs on a private Kubernetes cluster reachable only through a Cloudflare Tunnel — no ports are exposed to the internet. Cloudflare Access enforces policy at the edge before any request reaches an app. Enrolled WARP devices are verified by device posture; browser sessions are verified by identity provider token. Sessions expire and must be re-verified periodically.