Running a law firm on Free software
A small UK tech-focused law firm running almost entirely on Linux and free, self-hosted software has prompted wider reflection on how viable this model is for legal practice. Commenters weigh the benefits of cost control, data sovereignty, open formats and customization against worries about maintenance burden, solo “DevOps-lawyer” risk, and compatibility with de facto standards like Microsoft Word and big SaaS tools. The exchange also surfaces broader anxieties about cloud legal tech and AI platforms, from client confidentiality and metadata harvesting to whether relying on proprietary ecosystems is itself becoming a professional liability.
Free / open-source tooling choices
- Many commenters list FOSS stacks for small firms: InvoicePlane and Kimai for invoicing/time; ERPNext for ERP/accounting; EspoCRM for CRM; Nextcloud, Outline, Vaultwarden, Docuseal, Cal.com, etc.
- Some use simpler setups: GnuCash, beancount+fava, or just LibreOffice plus manual tracking.
- Consensus: FOSS can cover most back-office needs, but multi‑user accounting and polished UX can be weak spots.
Accounting and practice management
- Questions about what “money software” and ERP are used and whether external accountants are doing the books.
- People suggest GnuCash, plain‑text ledgers, ERPNext, or sticking with mainstream tools to keep CPAs and regulators happy.
- Some note malpractice or cyber‑insurance policies may effectively require practice-management platforms and structured calendaring, billing, and document retention.
AI tools and data/privacy
- Strong concern that tools like Harvey (and analogies to Carta/OpenAI/Anthropic) could vertically integrate, using firms’ data/metadata to capture the legal market.
- Debate over whether enterprise contract terms and “no training on customer data” promises are sufficient; skepticism about future policy changes and breach risks.
- Lawyer–client privilege with LLMs is seen as murky; many think using such tools for privileged data requires solid contracts and risk assessment.
- Some recommend starting with AI for research and summarizing public documents; others warn that relying on LLM drafting without careful review now leads to sanctions.
Microsoft Word vs LibreOffice and alternatives
- One reported claim: not using Word might approach malpractice; others call this exaggerated.
- Practical argument: courts and counterparties often expect .docx and complex tracked changes; compatibility failures that hurt clients could be hard to defend.
- Counterpoint: many lawyers successfully use LibreOffice or OnlyOffice, exporting .docx with few real issues.
- Some courts still demand editable Word files for proposed orders, but most filings are PDFs.
- Stronger consensus that paid research tools (Westlaw/Lexis) are closer to “must have” than Word itself.
Solo practices, FOSS, and IT burden
- Some worry a small firm with custom FOSS and minimal DevOps is fragile, especially if the one technical person is unavailable.
- Others respond that a two‑person tech‑focused firm or solo practice doesn’t need heavy DevOps; email, basic hosting, and backups suffice.
- For clients, concerns include continuity if a nonstandard stack fails; defenders point out that open formats ease migration and avoid SaaS lock‑in and rising subscription costs.
Self‑hosting infrastructure
- Commenters discuss running Postfix, Unbound, Pi‑hole, rspamd, etc.
- Self‑hosting email is seen as viable but requires tracking changing deliverability rules from large providers; some prefer hosted mail for reliability while keeping self‑hosted fallbacks.