23 self-hosted services in one dashboard. Pi-hole, Proxmox, Home Assistant, Plex, OPNsense, and 18 more. On iPhone and Apple Watch. No server, no signup, no telemetry.
The app talks straight to your services over your network. No relay, no proxy, no Stacklight-operated server in the middle. Your traffic never touches us, because we have no infrastructure for it to touch.
No email, no password, no signup screen. Open the app, add a service, you’re using it. The only credentials anywhere are the ones for the services you choose to connect.
No analytics, no crash reports, no third-party SDKs. The app ships with zero code that phones home. Whether you open it once a week or twice a minute stays between you and your iPhone.
Your credentials live in your iOS Keychain. Your service list syncs across your devices through your own iCloud account. The only thing that knows about your homelab is your homelab.
Native API integrations for the homelab stack. Not screenshots of a web UI, not a generic terminal. Each one gets a detail view designed around the data that matters: pool health, container state, CPU under scrub, who’s streaming, what just got blocked.
Proxmox VE
Docker (Portainer)
Synology DSM
Unraid
TrueNAS Scale
Linux host (Glances)
Jellyfin
Plex
qBittorrent
Transmission
Overseerr / Jellyseerr
Pi-hole
AdGuard Home
Nginx Proxy Manager
OPNsense
Immich
Paperless-ngx
Home Assistant
Gitea / Forgejo
Uptime Kuma
ScrutinyServices tagged iOS-only have no native iPhone counterpart anywhere else.
Use the swatches in the top right to try each theme on this site. That’s what they look like in the app.
The Stacklight Watch app is a real watchOS app, not a stretched iPhone scene. Every service you’ve added on the phone shows up on the Watch with the same status and the same live data.
Glance at your wrist to see if anything’s on fire. Tap a service for the same detail view, scaled for the smaller screen. Read-only by design: destructive actions stay on the phone.
No. Stacklight talks to the APIs your services already expose on their normal ports. No agent, no proxy, no helper container. If your service has a web UI you log into, Stacklight can reach it.
Yes. Each service in Stacklight can have multiple endpoint URLs, typically a LAN URL and a VPN or public URL. The app probes them in order and uses the first one that responds, so the same service works at home, at the office, and anywhere your phone gets connectivity to one of those addresses.
Supported, with explicit user trust. On the first connection to a self-signed endpoint, Stacklight shows you the certificate fingerprint and asks you to confirm. After that, the pin is remembered. It also syncs via your iCloud to your other devices, so you don’t have to re-trust on the Watch or a new iPhone. If the certificate ever changes, you’re prompted again.
Through your own iCloud account, using Apple’s CloudKit. Stacklight has no servers, so there’s nothing for us to sync to. Add a service on your phone, it appears on the Watch within seconds. Same goes for a second iPhone, an iPad, or a new device you sign into iCloud later.
Not at the moment. The architecture, including the “no backend” design and the credential handling, is documented on this site and in the Privacy Policy, and the App Store privacy nutrition labels make the data practices contractually binding.
No. That isn’t the product. The whole point of Stacklight is to avoid pointing a SaaS at your home network, which isn’t how self-hosters want to live.
Stacklight is built by an indie iOS developer. iPhone and Apple Watch shipped first because that’s what we run. An iPad version is coming. An Android version is on the roadmap; we want to ship one that does the platform justice, not a hasty port of the iOS app.
