Skip to main content

Deployment and kiosk

Veridian Motion ships as a Progressive Web App (PWA) — a TanStack Start web application installable on facility tablets and workstations. Deployment at veridianhp.com (or an agency-specific domain) uses Lovable Cloud / Supabase for backend services.

PWA installation

Facilities install Veridian Motion on kiosk devices through the browser’s Add to Home Screen / Install flow (exact steps vary by OS). Installed PWAs launch full-screen without browser chrome, suitable for supervised intake stations.
Offline behavior is limited. Assessment submit and photo upload require network connectivity to Supabase. The app does not promise full offline clinical workflow.

App-level kiosk hardening

Veridian Motion implements the following in the application (not a substitute for MDM):
ControlBehavior
No external navigationExternal links and web egress blocked in kiosk context
Strict CSPContent Security Policy limits script and resource loads
Self-hosted fontsTypography served from the app; no Google Fonts or CDN font loads
Idle auto-resetInmate session clears after inactivity; returns to sign-in
No inmate external messagingMessaging is in-app only; no SMS/email to outside parties

Agency-provided lockdown

True locked kiosk operation in a correctional facility also requires agency-provided controls:
ControlOwner
MDM profile (single-app mode, disable browser, USB restrictions)Agency IT
Network firewall (allowlist only required endpoints)Agency IT
Physical supervision and escortCustody staff
Device procurement and replacementAgency
CJIS / FedRAMP / GovCloud hosting decisionAgency
Veridian Motion does not claim CJIS authorization or FedRAMP authorization. Agencies must host in environments that meet their compliance obligations.

Network requirements

Kiosk devices need stable HTTPS outbound access to:
  • The Veridian Motion application host
  • Supabase API and Storage endpoints (Lovable Cloud)
Block all other outbound traffic at the network layer when policy requires.

Self-hosted fonts and UI

The interface follows a plain, USWDS-aligned government tone — high contrast, accessible targets, minimal decoration. Fonts are bundled with the application build, supporting CSP and kiosk policies that block third-party resources.

Environment separation

Use separate Supabase projects (or equivalent) for pilot vs production. Pilot environments should use synthetic or de-identified data until BAAs and agency hosting are in place.

What’s next

Inmate kiosk flow

What inmates experience on the device.

Roles and access

Staff MFA and provisioning.

Security overview

Compliance split: app vs agency.