Book 5

Technical Reference

Reference for teams operating and integrating the Windows Self-Hosted OPSQAI product.

1. Windows runtime

The signed installer provisions the application, supporting Windows services and local PostgreSQL. The desktop shell checks service health before opening the application and directs administrators to recovery information when a dependency is unavailable.

2. Local data

PostgreSQL — application records, configuration, audit data and vector-backed knowledge.
Installation storage — customer documents, backups and release assets managed within the customer boundary.
Backups — administrator-controlled backup and restore procedures for the local installation.

3. AI provider boundary

Self-Hosted application
  -> governed context retrieval
  -> configured AI provider
     (Ollama for a fully local model, or an approved compatible provider)
  -> source-grounded response

The selected provider is installation configuration. OPSQAI Cloud does not receive the customer's operational knowledge.

4. Signed entitlements

Licenses are Ed25519-signed JWTs. The validated profile, products, add-ons and legacy compatibility claims resolve the effective configuration and visible workspaces. Invalid or absent claims do not unlock capabilities.

5. Health and heartbeat

Local readiness checks report whether required application services are available. A separate installation heartbeat may report installation status to Management Center; it does not transmit operational knowledge.

6. Integration surface

Supported integrations use authenticated application functions or documented public endpoints. Public callbacks validate their caller, input and signature before performing work.

7. Release lifecycle

Authorized Windows packages are listed through Customer Portal. The installation's Updates area and operational tooling provide the local update path and health checks.