SiteGlance
All posts

Umami Cloud vs Self-Hosted: Connect Both to a Mobile Dashboard

Published Sep 24, 2026 · 2 min read · Yichen Lab

Can you connect both self-hosted Umami and Umami Cloud to a single mobile analytics dashboard? Yes. With a native mobile client like SiteGlance, you can monitor self-hosted instances and Umami Cloud side by side on iPhone and Android. While both expose the same API, they authenticate differently: Cloud uses an API key, while self-hosted uses credentials over HTTPS. (New to the app? Start with checking Umami on your iPhone or Umami on Android.)

Umami Cloud: an API key

Cloud requests go to a fixed address, so there is no URL to type. You only need an API key.

  1. In Umami Cloud, click your profile in the side navigation and open Settings → API keys.
  2. Click Create key and copy it.
  3. In SiteGlance, add a connection, choose Umami Cloud, and paste the key.
What the app sends (for reference)
GET https://api.umami.is/v1/websites
Authorization: Bearer <your-api-key>

Self-hosted: address, username, password

For your own instance, SiteGlance signs in with the same username and password you use on the dashboard and receives a session token, exactly like the web login does.

  • HTTPS only. Plain http:// addresses are not accepted. If your instance has none, put it behind a reverse proxy with a certificate first.
  • Use the address where Umami lives. If Umami is served under a path such as https://example.com/umami, include the path.
  • The account needs read access to the websites you want to see.
SiteGlance add connection screen with self-hosted and Umami Cloud options
Adding a connection: choose self-hosted or Umami Cloud.

Connecting multiple instances and switching

If you manage multiple projects across both self-hosted servers and Umami Cloud, you can add each connection in Settings → Connections → Add connection. SiteGlance Pro saves multiple active profiles so you can switch between instances with a single tap, keeping separate visitor stats, real-time views, and widgets for each.

Common connection errors

SiteGlance tests every connection before saving it and tells you which step failed:

  • Username or password didn't get a token from the server — the server refused the login.
  • Login worked, but this account can't read websites — the account works but has no permission to view websites.
  • Host is up, but no Umami API here — usually a missing path or a reverse proxy that doesn't forward /api.
  • HTTPS certificate isn't valid — expired or self-signed certificate.
  • Can't reach this address or Timed out waiting for the server — check the domain and your network.
  • API key is invalid or revoked — create a new key in Umami Cloud.

Once connected, either flavour works the same way in the app, including home screen widgets.

Download on the App StoreGet it on Google Play

FAQ

Can I connect both Umami Cloud and a self-hosted instance?
Yes, with SiteGlance Pro, which lets you save multiple connections. The free version keeps one.
Why is my http:// instance rejected?
SiteGlance only connects over HTTPS so your credentials are never sent in plain text. Add a certificate, for example through a reverse proxy.
Where is my password stored?
On iPhone, in the iOS Keychain. On Android, encrypted with a key held in the Android Keystore. SiteGlance has no server and never sends it anywhere except your own Umami.

Keep reading