Book 3
Product Documentation
OPSQAI is a self-hosted operations and knowledge platform. It combines a grounded AI assistant with document, ticket, workflow, and reporting modules — all running on your own infrastructure.
1. Why OPSQAI exists
Regulated industries and mid-market operators need AI that stays inside their four walls. Public assistants leak data, on-prem stacks require a team to run. OPSQAI packages a private AI + knowledge base + workflow layer as a signed container stack you deploy in an afternoon.
2. Modules
- Chat — grounded conversational assistant with citations to your documents.
- Knowledge — document ingestion, versioning, and vector search.
- Tickets — internal helpdesk with AI triage and suggested replies.
- Workflows — declarative automations that can call AI steps.
- Reports — dashboards over usage, quality, cost and adoption.
- Admin — users, roles, SSO, license, doctor probes, audit log.
Modules are gated by the license token — buying a plan simply unlocks entries in the sidebar; no code redeploy.
3. How licensing works
An OPSQAI plan produces an Ed25519-signed license issued by the Management Center. The token embeds: customer id, modules, seat count, expiry, and any feature flags. The instance verifies the signature offline and refreshes entitlements daily. No customer data ever leaves the install.
4. Grounded AI
Every AI answer in OPSQAI is produced by embedding the user's question, retrieving the most relevant chunks from the tenant's own documents under RLS, and passing them as context. Answers include inline citations linking back to the source chunk. The model never sees another tenant's data.
5. Editions
- Self-Hosted — the product this documentation describes. Docker Compose, all data on your infrastructure.
- Managed Cloud — the same stack operated by OPSQAI on isolated EU-hosted infrastructure (single-tenant DB).