Confidential legal document analysis
Analyze matter documents with explicit control over where files, extracted text and model inference are processed.
Legal AI decisions need more than a product name. STACKELIER separates application, data and inference locations, then applies hard privacy and hardware constraints before a reference stack can qualify.
The useful configuration depends on what the work actually contains, not only on the profession label.
Analyze matter documents with explicit control over where files, extracted text and model inference are processed.
Retrieve from a matter-specific corpus while keeping ingestion, indexes, retrieved passages and inference inside the required boundary.
Use controlled internal knowledge sources without treating a self-hosted front end as proof that the full retrieval path is private.
Use this as a constraint when comparing reference stacks and when completing the Finder.
Use this as a constraint when comparing reference stacks and when completing the Finder.
Use this as a constraint when comparing reference stacks and when completing the Finder.
Confidentiality requirements can exclude otherwise capable configurations. STACKELIER treats mandatory privacy requirements as hard constraints rather than ranking penalties.
Where does the interface or service run?
Where are documents, embeddings and indexes stored?
Where does the model actually process the request?
Which authoritative sources support those claims?
These are verified launch configurations already used by the deterministic Finder. They are reference profiles, not universal recommendations.
PrivateGPT + llama.cpp + Mistral Small 3.1 24B
Open WebUI + Ollama + Mistral Small 3.1 24B
Open WebUI + Ollama + Qwen3-14B
Open WebUI + Ollama + Qwen3-8B
Hard constraints win: if a mandatory privacy or hardware requirement is incompatible, the stack is excluded rather than merely ranked lower.
Use the guides for the architecture questions, compare verified baselines side by side, or run the Finder with your exact privacy and hardware constraints.
Understand the decision boundary before choosing a specific stack.
Understand the decision boundary before choosing a specific stack.
Open the relevant reference configurations side by side.
Apply your exact task, privacy requirement and hardware instead of relying on a generic baseline.
The configuration must satisfy the required application, data and inference boundary and have enough evidence to support those claims. Hardware and model terms are evaluated separately from privacy.
No. The interface may be self-hosted while embeddings, storage or inference still use an external service. STACKELIER evaluates the complete path.
Compare ingestion, storage, retrieval, inference, hardware fit and evidence together. If a mandatory privacy condition is violated, the configuration should be excluded rather than merely ranked lower.