Lavern

Lavern's strongest idea is architectural, not model-related: it borrows a law firm's org chart — partners, associates, debate rooms, institutional memory — and implements it as 67 specialist agents with skill ratings, personalities and faces. Findings and challenges both have to cite text, the orchestrator resolves conflicts, and the audit trail falls out as a side effect rather than being bolted on. The ten-pass verification loop is the part that matters most for legal work: a single pass produces a draft, ten passes produce a deliverable, and pass seven (structure, evidence, preservation, placeholders) is where the rework actually happens. The context intake is the second real strength. Lavern interviews you before it acts — jurisdiction, deal size, risk appetite, intent — and the vendor's own framing is honest about why: "the model is not the bottleneck, context is." That matches how legal review actually works. The document output is typeset and cited at section level (the homepage example cites §1.2, §3.4, §5.1 across a twelve-state non-compete review), which is a different category of artifact than a chat transcript. Where it gets complicated is the operating model. Lavern is open source under Apache 2.0, currently v0.15.0, built by a law firm founder, and explicitly not a law firm and not legal advice. It installs via a curl command (~27 seconds per the site), you bring your own Claude or Mistral provider keys, and you either accept cloud inference (with EU data sovereignty on those providers) or switch to on-device mode where nothing leaves the laptop. Ollama is supported for fully local models. Clawern adds an autonomous tier: you point it at a folder, it watches on a thirty-minute heartbeat with precedent memory, cost forecasting and a hard budget cap. That's a genuine delegation model, not a chatbot feature. The downsides are real and stated by the vendor. There is no managed hosting, no SLA, no support desk, and no licensed attorney behind the output. Non-technical lawyers will hit a wall at the curl install and provider-key configuration. The instructions to verify AI output manually before sending anything are appropriate but also underscore that this is a power tool, not a service. And the open-source, demo-grade framing means you should expect version churn (0.15.0 is early) and to own your own reliability. Where it fits: solo practitioners and small firms that need cite-checked contract review with a traceable audit trail; in-house counsel vetting vendor DPAs and MSAs where every finding must cite section text; M&A attorneys reviewing non-competes or NDAs across multiple jurisdictions at once; legal teams with data-privacy constraints that require on-device processing; and developers building legal AI products on top of the Apache 2.0 codebase. Where it doesn't: anyone seeking legal advice from a licensed attorney, teams that need managed hosting or a vendor support desk, non-technical users who can't run a curl install or