KEMS
Cloudflare Access GH

Private property access

One sign in. Only the KEMS properties you are allowed to see.

KEMS uses Cloudflare Access as the identity boundary. The public KEMS website does not keep its own password database, Home Assistant credentials or property access tokens.

How sign in works

Authentication and property permission are separate on purpose.

1

Sign in with Cloudflare

Your identity is checked by the Cloudflare Access policy configured for KEMS.

2

Cloudflare checks access

Each property remains its own protected application. Being signed in does not automatically grant access to every property.

3

Open an authorised property

The launcher presents only what your identity is allowed to open, then routes through that property's outbound tunnel to its read-only KEMS dashboard.

What remote users can reach

The property dashboard.

Live DataCompareKEMS Agile PlanRead-only property evidence

What stays local

Maintenance and credentials.

Home Assistant credentialsPi update/admin controlsRemote Access setupHardware-control surfaces

Ready to open your property?

Continue to the Cloudflare App Launcher.

If your identity has access to one or more KEMS properties, they will be available after authentication.

Sign in to KEMS