For CIOs, CDOs & IT Leaders
Your data doesn't move. We build intelligence on top of where it already lives.
OpsGrid reads from Business Central using your existing BC credentials and permission model. Nothing is extracted to an external data store. QHub Wiki runs entirely on your own server. Both products are designed for organisations where data sovereignty is non-negotiable.
Data architecture
What OpsGrid reads, where it reads it, and what it never touches.
How OpsGrid accesses Business Central
OpsGrid connects to your BC tenant using the BC API and the service account credentials you provide. It reads from the operational tables you configure — nothing more. Data is retrieved at query time to generate a decision or answer, then released. There is no persistent data copy, no ETL, and no external warehouse.
Write operations are strictly bounded. OpsGrid can only write to the specific action types you explicitly enable — and every write requires a human approval event in Teams before anything is committed to BC.
Architecture at a glance
- Connects via BC API using credentials you provision
- Reads from configured tables only — purchase, inventory, production, sales
- Read-only by default; writes require explicit configuration and human approval
- No data extracted to an external store — retrieval is query-time only
- Teams integration via webhook — no additional infrastructure
- All actions logged to an audit channel you specify
Integration model
Three integration points. All of them use infrastructure you already have.
OpsGrid is built for the BC schema and permission model, not a generic middleware layer. It connects to Teams using standard webhook infrastructure.
BC-native integration
OpsGrid is built for the BC schema — not a generic ERP abstraction. It uses BC's API, respects your existing permission model, and works with the table structure BC already uses. No schema mapping, no custom connectors, no middleware.
Teams via standard webhook
Decision cards and approval requests are delivered via Teams webhook. No new Teams apps, no additional licences, no changes to your Teams tenant configuration. Uses the notification and approval mechanisms Teams already provides.
Self-hosted, open source
QHub Wiki is fully self-hosted: WikiJS, Qdrant vector store, and the LLM connector all run on your own server. Apache 2.0 licence. Auditable codebase. No vendor-managed infrastructure involved in document retrieval or query answering.
What you control
Every configuration decision is yours.
OpsGrid is auditable at every layer. You define the scope, the permission boundaries, the routing logic, and what gets logged.
BC credentials and permissions
You provision the service account OpsGrid uses. You set the BC permissions. OpsGrid operates only within the scope you define — it cannot escalate its own access.
Which decision types surface and to whom
You configure which operational events trigger a decision card, which Teams channels receive them, and which users or roles see each type. No decisions surface outside the channels you specify.
Approval routing by decision type and value
High-value decisions can be routed to senior approvers. Routine decisions can be delegated. Escalation paths are defined in configuration, not hardcoded.
Audit log — every action, every outcome
Every decision surfaced, every approval or rejection, every BC write — logged to the audit channel you designate. Exportable. Retainable under your own data retention policies.
Compliance and sovereignty
Built for environments with strict data governance.
Four commitments to your data governance team
For organisations where a CIO or CDO must sign off on any AI deployment, these are the guarantees that matter.
Human-in-the-loop by design
$0 in BC writes without explicit human approval. The approval event is a prerequisite, not a courtesy — the write pathway is blocked until a named user approves in Teams.
LLM sees retrieved chunks only
The language model receives only the specific data chunks retrieved to answer a query. It has no persistent access to your BC data and does not store or train on your data between sessions.
Self-hosted option available
QHub runs entirely on your infrastructure. If full on-premises deployment is a requirement for OpsGrid, talk to us — we can scope an architecture that keeps everything inside your perimeter.
Open source and auditable
QHub is Apache 2.0. The full codebase is auditable by your security team. No proprietary black boxes in the document retrieval or query answering pipeline.
Common questions
What CIOs and IT leaders ask us first.
From our insights
See all insights →Talk to us about your architecture requirements.
We walk through your BC environment, data governance constraints, and Teams setup — and map exactly what deployment looks like for your organisation.
Request an architecture overview →