Scirium: Product Overview

Status: PLANNED Audience: everyone (technical and business). Read this first.

1. One-liner

Ask your company anything. Get a cited answer from your own documents, scoped to the exact department you are talking to.

2. What Scirium Is

Scirium is a self-hosted, white-label, multi-tenant knowledge assistant for internal staff. A company points Scirium at its own document libraries (SharePoint, OneDrive, employee handbooks, policies, procedures). Staff ask questions in a chat window. Scirium answers using only that company's documents, and every answer carries inline citations pointing to the source.

Scirium is pronounced "sigh-ree-um", from the Latin "scire" (to know) plus the -ium element suffix.

3. Who It Is For

Audience	What they need from this product
Staff (end users)	Correct, cited answers to policy, procedure, and how-to questions without interrupting a human.
Practice / business admins	A way to turn existing documents into a scoped, auditable Q&A assistant per department.
MSP / reseller partners	A white-label product they sell under their own brand on infrastructure they control.
IT Pro Partner (operator)	A multi-tenant service that runs on existing netcup infrastructure with high gross margin.

4. The Core Invariant

One channel equals one knowledge domain plus one agent plus one scoped source. This is a hard rule, enforced in the data model, not a policy.

Bound item	Meaning
One knowledge domain	Employee Resources, Billing, IT Help, or similar.
One agent	A domain-tuned persona that answers only within that domain.
One scoped source	A set of M365 document libraries mapped to one vector namespace.

A channel cannot span two domains, and an agent cannot serve two channels. If a business needs a second domain, it creates a second channel, a second agent, and a second scope.

5. Why This Is Not Just Another Chatbot

A regular chatbot is one undifferentiated model with no grounding in your documents, no audit trail, and no scoping. Scirium is the opposite on every axis a business cares about.

Axis	Regular chat	Scirium
Grounding	May hallucinate, no source	Every answer cites its source documents inline with a Sources footer
Scoping	One model answers everything	One channel equals one domain plus one agent plus one scoped source. Billing answers billing, HR answers HR.
Data residency	Sent to a vendor's cloud	Self-hosted, white-label, data stays in the company's M365 and your infra
Audit trail	None	Every question and answer logged with citations, model, tokens, latency
Identity	Anonymous	Each domain is a named agent persona (for example "Scirium Billing")
Failure mode	Confident wrong answers	If the answer is not in scope, it says so instead of guessing
Tenancy	N/A	One deployment serves many isolated tenants

The difference is trust. A regular chatbot is a tool. Scirium is a scoped, grounded, audited answer layer over documents the company already owns.

6. Architecture at a Glance

Layer	Responsibility
Rocket.Chat	Chat transport only. One workspace per tenant. Zero intelligence.
FastAPI orchestrator	All intelligence. Tenancy, agents, scopes, M365 connector, retrieval, LLM.
Postgres + pgvector	State and vectors. Tenants, channels, agents, scopes, documents, chunks, messages.
admin-ai	LLM. DeepSeek V4 Pro primary with a configured fallback chain.
Wasabi S3	Object storage. Sync staging, backups, agent assets, audit exports.

This split is fixed. Rocket.Chat never holds intelligence; the orchestrator never renders chat UI.

7. Hard Scope

Internal staff documentation only. No patient records, no PHI, no HIPAA scope, no medical or vision AI. This boundary is permanent and is not a roadmap item.

02-v1-scope.md: exactly what v1 ships.
03-v2-scope.md: what v2 adds.
04-admin-guide.md: provisioning and go-live.
05-user-guide.md: how staff use it.
06-roadmap.md: v1 through v4 and the autonomy curve.

4.0 KiB Raw Blame History