Open components. One coherent system.
Kubernetes, Kubeflow, Argo Workflows, Harbor and MLflow form the platform layer. Model serving and retrieval connect through controlled APIs.
VFUSION AI / TECHNOLOGY
From document to answer, GPU to API. This is our reference architecture: components are selected for each engagement, with explicit boundaries and measurement points.
INSIDE THE BOUNDARY
This diagram is a reference design. Exact components, active layers and access boundaries are defined for each project.
Kubernetes, Kubeflow, Argo Workflows, Harbor and MLflow form the platform layer. Model serving and retrieval connect through controlled APIs.
Docling on GPU, extraction models for OCR and tables, and Gemma for visual interpretation. Dutch and English documents both matter.
OpenTelemetry and Loki make processing stages visible. Quality evaluation, versioning and access controls belong in the architecture.
A shared AI interface connects model serving, document processing and orchestration tools to websites and apps. Data scope, allowed actions, approval and audit remain explicit for each application. Financial amounts and state transitions are validated by the application.
WHAT YOU GET
gpt-oss, Gemma and an in-house quantised 72B coding model.
BGE-M3, Qwen3 embeddings, BM25 and reranking.
YOLO, vision-language models, Docling and OCR.
H100, Kubernetes, Slurm, NVMe-oF and RoCE.
LAYER 01 → 10
A reference for design and evaluation. No promise of infallible answers; every layer has a defined responsibility.
Docling, OCR and orchestration turn source documents into consistent text and metadata.
BM25 and dense embeddings combine exact search with semantic meaning.
HNSW search and reranking select the most relevant passages.
Relevance, freshness, authority and agreement determine whether there is enough evidence.
The model works with selected sources and a versioned instruction.
Claims connect to passages, documents and pages.
An additional NLI check can flag missing or weak support.
Evaluation sets, MLflow and alerts make changes visible.
Exact and semantic caches with versions and expiry.
Per-stage tracing with OpenTelemetry and Loki.
THE NEXT STEP
Start with the documents, the process or the technical question. We will help define a useful first step.