Where it runs
Your hardware, on-premise. Single-tenant. The core pipeline is air-gappable.
Deployment & Security
Your documents never leave your hardware.
BDS ingests, searches, and builds an entity knowledge graph over large document sets — OCR, semantic search, and named-entity analysis — using AI models that run locally on your own machine. On the core pipeline, no document ever leaves your infrastructure.
Self-hosted
Safe by default
Local model inference
No corpus egress
Firewall-controlled access
At a Glance
Where it runs, where data lives, who can reach it.
The short answer to the three questions a security reviewer asks first.
Where data lives
Local disk only — the source documents, the search index, and the entity graph.
Who can reach it
Loopback by default; any access beyond the host machine is firewall-gated.
Data Residency & AI Processing
Read, indexed, and analyzed in place.
Your documents are processed on your own machine — nothing is sent to an external AI provider.
All AI inference is local
Text understanding, vision/OCR, embeddings, and entity extraction all run on models hosted on your own GPU. No third-party AI service receives your documents or prompts.
text · Qwen3.8-27B-Instruct vision/OCR · Qwen3-VL-8B embeddings · BGE-large-en-v1.5 entities · GLiNER
All storage is local
Source files, the OCR'd text, the vector search index, and the entity knowledge graph are written only to disk on the host machine. Nothing is uploaded to any cloud store.
Analytics telemetry is off
The vector-database component's usage telemetry is disabled at startup. The core pipeline makes no outbound calls, so it can run fully air-gapped.
OSINT enrichment — a separate, disclosed egress feature
An optional module looks up public open-source intelligence on entities BDS finds. It is the one part of BDS that reaches third-party sources on the internet — disclosed as such — so a deployment that uses it is no longer air-gapped. It is invoked deliberately and separately from the core ingest / search / graph pipeline, which makes no outbound calls; only the entity identifiers you select are sent, never your documents.
Access Control
Controlled at the network layer — by design.
Safe by defaultThe BDS server binds to
localhost (127.0.0.1) only — reachable solely from the machine it runs on. A deployment that installs BDS and changes nothing is already closed to the surrounding network.Exposing it to other machines is a deliberate change you make and place behind your firewall. This is a simplicity choice, not a shortcut: there is no separate identity store to stand up, breach, or leak credentials from. Access reuses the perimeter controls you already operate — BDS is reached the same way as any other internal service.
Shared Responsibility
A clear line, the standard on-premise way.
What BDS delivers, and what your environment provides.
BDS provides
- Local-only AI & storage — no corpus ever leaves the host.
- Safe by default — loopback-only bind out of the box.
- No telemetry — an air-gappable core pipeline.
You provide & operate
- Network security — firewall / segmentation for any access beyond localhost.
- Host security — a patched, hardened OS; controlled physical & admin access.
- Encryption at rest — full-disk / volume encryption (e.g. BitLocker) on the data drive; strongly recommended for a confidential corpus.
- Backups & recovery of the data directory.
Before an install is scheduled, you complete a short security attestation — host on a segmented / firewalled network · OS patched · physical & admin access controlled. Disk encryption on the data drive is strongly recommended, though not required to schedule. The hardening guide defines what each item means in practice.
What This Means For You
Your data stays yours.
Your data stays yours
Because inference and storage are local, sensitive or privileged documents never transit a third party. BDS can be deployed on an isolated network with no internet access.
You control the perimeter
Access is governed by your existing firewall and network segmentation. The default configuration is closed — the server is reachable only from itself until you decide otherwise.
Single-tenant by design
One trusted deployment — no user-management overhead and no credential store to maintain.
Private AI. Local Data. Human Judgment.
Bring us your security review.
BDS is a self-hosted document-intelligence system: all AI runs locally, all data stays on your hardware, and access is loopback-closed by default and controlled by your network perimeter.