Stand-alone

HVC can run as a standalone / private installation — a tenant-hosted deployment where the clients point at the tenant's own server instead of the shared multi-tenant infrastructure. This is useful for customers that need their data to stay in-house.

How it works

• The tenant API exposes private-server configuration endpoints (hvc-api — Features/Tenants):
  • generatePrivateServerConfig — produces a PrivateServerConfig for a tenant.
  • generatePrivateServerConfigQrCode — encodes that config as a QR code.
• Clients import the config (scanning the QR or entering the server URL) and then talk directly to the tenant's API/Keycloak/Pexip instance.

Mobile & headset

• hvcmobile — Settings → "private-server config": scan the QR or enter the server URL; saved login profiles persist per tenant (SavedLoginProfile in ObjectBox).
• hvc-xr — same private-server config flow on login; the config defines the API base URL, Keycloak realm, and Pexip node used at runtime.

Admin console

• The admin console manages tenants and their connection settings, including the data/file-store connection strings used to build the standalone config.

Where the config lives

• API/GraphQL base URL, Keycloak realm + client, Pexip node — all resolved from the PrivateServerConfig at login time.

Notes

• The root README.md lists "make HVC standalone" as an ongoing effort; the private server config endpoints are the current implementation of that goal.

Related

• Api — Tenants & Admin — the endpoints that generate the config.
• Mobile settings — client-side import flow.