doc.haus is a local legal-document workspace built on OpenCode: upload documents into matters, ask source-grounded questions, prepare drafts and redlines for lawyer review. Covers local start via ./start.sh (web at localhost:5174, engine/ingest on separate ports), the Docker Compose self-host option (only web published, loopback only), settings/storage layout, opt-in provider capture, and links to contributing, security, licensing and attribution. Read first when installing, launching, or describing what doc.haus is.
doc.haus
A local legal-document workspace built on OpenCode. Upload documents into matters, ask source-grounded questions, and prepare drafts and redlines for lawyer review. Generated work requires professional review.
Start locally
Install Git and Bun 1.4.0 or newer, clone this repository, then run:
git clone https://github.com/sure-scale/doc-haus.git
cd doc-haus
./start.sh
The launcher installs frozen dependencies and opens the web app at http://localhost:5174. It runs engine, ingest and web on separate local ports. A new installation needs no credentials to boot. Accept the launch notice, choose a provider (detected options appear first), connect with its offered sign-in method and detected defaults, then confirm primary/fast models in setup. Research and firm or jurisdiction details are optional. Opening setup does not make a paid model request; connection tests run only when requested. Provider access and quota remain subject to the provider's account and organization policies.
Install Deno 2 for the shipped Python tool. For document conversion, install Python 3, Poppler, Tesseract and LibreOffice Writer as needed. The container includes these tools. See setup.
Local container
docker compose up --build
Open http://localhost:5173. Only web is published, on host loopback. Engine and ingest stay on container loopback behind /engine and /ingest proxies. Named workspace and runtime volumes retain documents, native credentials, sessions and settings across recreation. This is a local self-host configuration. Internet-facing or team hosting needs a separate deployment design.
Settings, data and updates
Saving settings leaves the shipped dochaus/opencode.json unchanged. User model and provider options and agent/skill toggles live in runtime configuration; credentials use native storage. Custom builder definitions have separate backup requirements described in the storage guide. See storage and backup and upgrades, including the explicit migration path for older installations with tracked settings.
Detailed provider/tool captures are off by default. Troubleshooting capture requires DOCHAUS_PROVIDER_CAPTURE_DIR set to a private absolute directory; DOCHAUS_PROVIDER_CAPTURE_DIR=off disables it without deleting prior captures. Captures can contain confidential document and model content. Ordinary native sessions and sanitized failure diagnostics remain durable independently.
Contributing · Security · Licensing · Attribution · Atlas (searchable doc navigator, runs on port 7121)
The root install script belongs to upstream OpenCode. Use start.sh for doc.haus.