Windows kiosk launcher

Product overview

The whole Windows session, on your terms.

OLOID Windows Launcher turns a shared PC into a managed kiosk. Windows signs itself in, OLOID takes over the session, and the worker sees a launcher holding only the applications they are entitled to — each one opened already signed in.

The OLOID launcher asking a worker to scan their badge at the reader, filling a workstation screen in a clinical corridor.
01The machine is already signed in to Windows. What the worker meets is OLOID, asking who they are.

Where it lives

Not a login screen. The session itself.

Windows Login replaces the lock‑screen prompt. Launcher goes further: the Windows account is signed in automatically at boot, and OLOID owns everything the worker sees from that point on. There is no desktop to wander, no Start menu to search, and no second credential to remember.

  1. 01

    The machine signs itself in

    Windows auto‑logs into a managed local account at boot. Nobody types a Windows password, because nobody needs one.

  2. 02

    OLOID takes the session

    The launcher shell starts in place of the desktop and stays in front. The worker identifies themselves to OLOID, not to Windows.

  3. 03

    Their apps appear

    The launcher shows the applications that worker is entitled to — and nothing else.

  4. 04

    Apps open signed in

    OLOID supplies the credential each app expects, so the worker moves straight into the work.

Per‑user app catalogue

You choose what each worker sees.

The launcher is configured centrally, per user or per role. A nurse on a ward station and a picker on a packing line can share the same hardware and the same image, and still open to entirely different sets of applications.

  • Tiles are assigned per user group, and a worker gets the union of every group they belong to — so entitlements compose rather than conflict.
  • Installed applications and web destinations sit side by side as tiles. Web tiles open in a throwaway browser profile that leaves nothing behind, and can close themselves after a set time.
  • Anything not assigned is not shown. The catalogue is the entire surface area of the session.
A launcher session showing tiles for Edge, Epic Hyperspace, Excel, the User Portal and two intranet sites, with the Choose Background dialog open.
02Assigned tiles down the left — installed applications and web destinations together. Backgrounds are picked from a set the organisation approves.

Identity

One session token, into the IdP you already run.

When a worker identifies themselves at the launcher, OLOID issues a session token for that person. That token federates with the identity provider the organisation already operates — so the worker is a real, named identity in your directory for the length of their session, on a machine that is signed into a shared Windows account.

  • Microsoft Entra ID
  • Okta
  • Ping Identity
  • No new directory to maintain: entitlements keep living where they already live.
  • The session ends when the worker does — the next person starts a session of their own.
WORKER Identifies at the kiosk OLOID Session token Issued for that person, for that session only Microsoft Entra ID Okta Ping Identity
The machine holds a shared Windows account; the worker is still a named identity in your directory.

Credentials

A password and passkey manager, built in.

Not every application can be federated. Launcher carries its own vault so the ones that cannot still open signed in: it holds passwords and passkeys for a worker and fills them in on their behalf — in browser‑based applications and in native Windows applications that predate SSO entirely.

  • Autofill reaches legacy native applications, not only web forms — which is usually where shared logins and sticky notes survive.
  • Passkeys are supported alongside passwords, so an application can be moved forward without waiting for every application to move.
  • The worker never sees or types the secret, so it cannot be shared, written down, or carried to the next shift.
OLOID VAULT Passwords Passkeys Held for the worker, never shown AUTOFILL Browser-based applications Intranet, SaaS, anything reached through the browser Legacy native Windows applications Thick clients written long before SSO existed
Federation covers what it can. The vault covers the rest, so nothing falls back to a shared password.

Workflows

Configurable, end to end.

What happens at sign‑in, during the session and at hand‑over is configuration, not a fixed product opinion. One image can serve every site you run.

  • An ordered list of actions runs at login — open a portal, launch a particular application first, or run a site‑specific script before the worker starts.
  • Sessions can sign themselves out after a set period of no input, so a walked‑away workstation does not stay open.
  • Lock and logout each have their own hooks, so cleanup runs on the way out rather than being left to the next worker.
  • Wallpaper, backgrounds and the lock and logout screens carry your branding — and can offer workers a set of approved backgrounds to choose from.
01BootWindows auto sign-in02IdentifyWorker proves who they are03On-loginOrdered actions run04SessionAssigned apps only05Hand-overIdle, lock and logout hooks
Every step is configuration, so one build serves sites with different rules.

See it running

Watch a shift start.

Recordings from a working deployment — signing in at the kiosk through to an SSO session, and handing a live clinical application from one worker to the next.

Sign in to Entra ID. A worker identifies themselves at the launcher, and the session carries straight through to a Microsoft Entra ID sign‑in without a second credential.

Video loads only when you press play.

Lockdown

A kiosk that stays a kiosk.

Owning the session is only useful if the worker cannot step outside it. The machine is hardened at provisioning, and the browser is fenced in by policy rather than by convention.

  • Browsing can be restricted to an allowed list of domains, so the browser reaches your applications and nothing else.
  • Downloads are forced into a controlled folder with no save prompt, keeping files off the desktop and out of user profiles.
  • Task Manager is blocked at provisioning time, so the shell cannot simply be ended.
  • A diagnostics view exists for the people who deploy this, and is off unless you turn it on.
INSIDE THE KIOSK Assigned application tiles Allowed domains only Downloads to a controlled folder Optional inactivity sign-out OUT OF REACH The Windows desktop Start menu and search Task Manager The open web
The shell cannot simply be closed: Task Manager is blocked when the machine is provisioned.

At a glance

What the launcher does.

Runs asA managed shell on a Windows PC that auto‑logs into a local account at boot. OLOID owns the session in place of the desktop.
Best forShared and kiosk workstations where many people use one machine across a shift.
App catalogueAssigned per user or per role. Workers see only what they are entitled to.
IdentityA per‑worker session token federated with Microsoft Entra ID, Okta or Ping Identity.
CredentialsBuilt‑in password and passkey manager with autofill into web applications and legacy native Windows applications.
LockdownBrowsing restricted to allowed domains, downloads forced to a controlled folder, Task Manager blocked at provisioning, optional inactivity sign‑out.
CustomisationCatalogue, branding, backgrounds, login actions, and lock and logout behaviour are configured per tenant, per device and per user group.
RelatedWindows Login — the credential provider for machines that keep a normal Windows desktop.