Local Sovereignty & Security

DAMS is built on a local-sovereignty principle: your source code, embeddings, and reasoning never leave the machine unless you explicitly opt in.

What stays on-device

VRAM budget (RTX 4090 / 16 GB)

ModelVRAM
qwen3-embedding:8b~2.5 GB
Qwen3-Reranker-8B:Q5_K_M~5 GB
Total~7.5 GB available of 16 GB

No Docker, no TEI container — both models run natively on Ollama.

Defensive guardrails

Opt-in telemetry

Error telemetry via sentry-sdk → GlitchTip is strictly opt-in. Enable by setting GLITCHTIP_DSN in the environment or .dams/config.yaml. Uptime monitoring (Uptime Kuma) watches /api/health and is also opt-in via the monitoring compose file. Neither is required to use DAMS.

Data isolation

The dev container isolates the project root, .dams/, the SQLite ledger, the Graphify cache, and the Ollama socket — nothing leaks into the host beyond the mounted workspace. Multi-machine sync uses rsync (or local transfer) with merge/overwrite semantics you control.

DAMS-FT: Enterprise-Grade Security Architecture

DAMS-FT (Fine-Tuned Edition) extends DAMS with zero-trust security enforcement specifically designed for enterprise environments, defense contractors, and financial institutions.

DAMS-FT Security Highlights:

Hardware Requirements:

ComponentSpecification
GPU1x NVIDIA RTX 4090 (24GB) or A10G (24GB)
VRAM5.2 GB (Model) + 0.8 GB (KV Cache) = 6.0 GB Total
RAM16 GB System Memory
Disk15 GB NVMe SSD

See the full DAMS-FT documentation for benchmark results and deployment specifications.