Clausehound · Legal knowledge engine

Tracks the clauses that matter.

Clausehound turns statutes, regulations and contracts into a versioned clause model: git for the law. It runs where your data needs to live, and you connect from the AIs you already use and tokens you've paid for. No lock-in, and every answer comes back with its source.

Looking for lawyers, not software? Cobalt is the law firm that runs on Clausehound.

tools/call compare_statute_versions
{
  "citation_code": "00e41",  // Employment Standards Act, 2000 (ON)
  "from_version":  "2004-03-01",
  "to_version":    "2009-11-06"
}

← structuredContent
{
  "changes": [
    {
      "change_type":  "amended",
      "section_path": "Part VII › 17",
      "to_text":      "…48 hours in a work week…"
    },
    {
      "change_type":  "added",
      "section_path": "Part XVIII.1 › 74.1",
      "to_text":      "\"assignment employee\" means…"
    }
  ]
}

From your agent: two cited changes, not two consolidations of the Act.

query Findings($report: Uuid!) {
  searchAnalysisWorkspace(searchQueryUuid: $report) {
    verdict
    rationale
    approvalStatus
    contractVersion { name contract { name } }
  }
}

← data
{
  "searchAnalysisWorkspace": [
    {
      "verdict":        "inadequate",
      "rationale":      "No prior consent before customer
                         data is used to train AI models…",
      "approvalStatus": "approved",
      "contractVersion": {
        "name": "Signed 2026-04-29",
        "contract": { "name": "Master Services Agreement" }
      }
    }
  ]
}

From your code: the findings your lawyers reviewed, with their sign-off.

Git for the lawevery amendment kept, dated and diffable, clause by clause
Your serversor ours: runs where your data lives, no shared cloud, no lock-in
Any AIbring the model you've already approved, over MCP or GraphQL
Since 2016patented (US 12,670,200), not a ChatGPT wrapper
What it is

One model for every legal document.

A statute, a regulation and a supply agreement are the same thing to Clausehound: a document with versions, broken into a tree of clauses that can be tagged, compared and cited. Think of it as change control for legal documents: git for rules and regs. Your originals stay untouched; the model is a layer on top.

  1. Document Employment Standards Act, 2000 · S.O. 2000, c. 41
  2. Version As it read from 2009-11-06 · immutable
  3. Cluster Part VII › Hours of work › s. 17
  4. Clause 17 (1) The provision text, with its stable identity
  5. Tags Attached at any level and inherited down the tree
Three ways in

The app for your lawyers. GraphQL for your code. MCP for your agents.

MCP is one door, not the only one. Here's what your end users see: search every document at once, compare any clause with every similar one, spot what's missing, and run a playbook of prompts with a person reviewing every result. The same findings reach your systems over GraphQL, and your agents over MCP.

Pick a flow: step through each prompt, or run a whole playbook built from your team's own precedent. Watch the walkthroughs
Guided: the suggested change as a redline. Nothing is written until someone approves it.
Autonomous: a whole playbook across a portfolio, out as Word with tracked changes.
In production

Lawyers run real matters on it, every day.

Cobalt, a tech-focused law firm, runs its legal services on Clausehound: Diligence Monster for due diligence, DealPrep for deal knowledge and Policysaurus for policy research, plus records retention schedules, with its lawyers verifying every finding in the app. It's the platform's toughest user, and the reason every feature here was built for work that has to be right.

Want the same for your own legal team? If you're in-house counsel or run a legal team, we'll set up an engagement that puts the platform Cobalt uses in your hands: your documents, your playbooks, your deployment (behind your own firewall if you like), run by the engineers who built it. Set up an engagement →

Architecture

Hyper-efficient, by design.

You won't sign up, start small, and burn through your compute and AI budget in a week because the platform wastes tokens. The hard work happens once, at ingest. After that, a question is a lookup over structured clauses, not a model rereading documents from scratch. And the same design that keeps it cheap is what keeps answers grounded.

Distributed

Yes, behind your own firewall.

No shared Clausehound cloud: the data layer runs where you need it, hosted by us, in your cloud or on your own servers. Already approved your AI provider? Clausehound adds no new party holding your documents. UUIDs everywhere and WebAssembly builds keep it portable.

Speed

Tiny latency, tiny hosting bill.

The core is Rust: compiled, memory-safe and lean. Answers come back in milliseconds, and a full deployment runs comfortably on modest servers. It's how we run it ourselves.

Tokens

Agents ask for clauses, not documents.

A tool call returns only the provisions that answer the question, with their sources. Your agent's context stays small, so every call costs less and runs faster than pasting whole Acts into a prompt.

Guardrails

Less to read, less to get wrong.

A model handed three cited clauses has far less room to invent than one handed a 400-page PDF. Efficiency and accuracy come from the same place: structure.

Change control

Git for rules and regs.

Every amendment is a new, immutable version, chained to the last. Diff any two dates clause by clause, see what changed and why, and get flagged when a clause you rely on moves.

Security

SOC 2, and files boxed in.

SOC 2 audited. PDF parsing and OCR run in their own service on an isolated network. Single sign-on through Azure AD and OpenID Connect.

Verification

Cited, and checked against the law as it stood.

AI is genuinely useful in legal work, and used carelessly it can hurt you. Language models are fluent and sometimes wrong, and in law a confident wrong answer is the expensive kind. We provide the platform, the tooling and the support to use AI responsibly.

"AI tools promise efficiency; however, their indiscriminate use in drafting legal arguments constitutes a pernicious threat to the integrity of the judicial process. Fabricated case citations distort and corrupt the case law."

Justice Roger Lafrenière, Federal Court of Canada, September 2026, rejecting a filing built on citations to cases that don't exist. National Post
  • Grounded in the source. Every answer resolves to a specific clause, in a specific version, with its section path and source. The model doesn't get to paraphrase the law from memory.
  • Citations are checked. A section the model cites has to exist in the version in force on the date asked about. If it doesn't, the answer is flagged, not passed through.
  • AI proposes, people verify. Tags and findings carry a review state. Lawyers confirm or correct them in the app, and who verified what, and when, is kept.
Findings · Ontario employer, 2004 2 verified · 1 flagged
  1. ESA 2000, Part VII, s. 17 · version 2004-03-01 Weekly hours capped at 48 without an agreement Verified
  2. ESA 2000, Part VII, s. 17 (3) · version 2004-03-01 Excess hours need written agreement and Director approval Verified
  3. ESA 2000, s. 74.19 · not in version 2004-03-01 Temporary help agency obligations Flagged

Illustrative example. The flagged row cites a section that wasn't in force on the date asked about.

The knowledge base

Not US-centric. Built for wherever you work.

Most legal AI tries to one-shot answers from a model trained mostly on American law, and treats everywhere else as an edge case. Clausehound reads each jurisdiction's own official consolidations, with every historical version kept, so the answer comes from the law that actually applies. Our deepest corpus today is Canadian, because that's where we do the most work. The same pipeline takes on the EU, the UK or anywhere else that publishes its law.

Our largest corpus: Canada

  • Federal
  • Ontario
  • Québec
  • British Columbia
  • Alberta
  • Saskatchewan
  • Manitoba
  • New Brunswick
  • Municipal bylaws

Subject areas

  • Occupational health and safety
  • Employment standards and labour
  • Corporate and securities
  • Real estate and construction
  • Privacy and access to information
  • Income and corporate tax
  • Sales and property tax
  • Environmental
  • Limitations
  • Building and fire codes
  • Insurance and financial institutions
  • Pensions
  • AML and evidence
  • Workers' compensation
  • EI and CPP
  • IP
84
versions of Ontario's Employment Standards Act since 2002, every one kept
71
consolidations of Ontario's Insurance Act, each navigable on its own
~4,000
statutes and regulations in the corpus, every version kept
Yours
your own contracts and precedent, in the same model, alongside the law
Integrations

Bring your own agent.

For agents, Clausehound speaks MCP, the open standard AI assistants use to connect to tools. Point Claude, or any MCP client, at your endpoint and it can search, compare and cite the law directly. For everything else there's GraphQL and exports.

Add Clausehound to Claude as a connector.
Or point any agent at Clausehound from its settings.
Runs alongside
  • SharePoint
  • Amazon S3
  • Kafka
  • RabbitMQ
  • Docker
  • Kubernetes
Track record

Not a wrapper. A decade in the making.

Clausehound isn't a thin layer over someone else's chatbot, built last year to chase a funding round. We've been structuring legal documents since 2016, doing machine learning on contracts with academic partners before anyone called it AI, and we patented the core. What we sell is what already works in production, not what's trending.

  1. 2016

    Clausehound starts: contracts as structured clauses, not files.

  2. 2018

    Joins Seneca HELIX, the start of a long research partnership with Seneca.

  3. 2020

    Machine learning on clauses with Seneca College: flagging problem clauses against a client's own precedent.

  4. 2022

    Patent filed for the clause taxonomy: breaking legal documents into typed, nested clauses that can be versioned, compared and analysed as data.

  5. 2023

    Large language models built into the platform, with people verifying every result.

  6. Now

    Patented: Clause Taxonomy System and Method for Structured Document Construction and Analysis, US Pat. No. 12,670,200. Point-in-time law, MCP for agents, and Rust from end to end.

Who builds it

Engineers and lawyers, since 2016.

Joshua Koudys

Joshua Koudys

Chief Technology Officer · Co-inventor

Joshua leads Clausehound's engineering and co-invented its patented clause taxonomy. He has built the platform since 2016: its Rust services, its version model and its MCP server, with one rule for AI in legal work: every result tied to its source.

He started at IBM, inside the DB2 database engine and later as a web-security subject-matter expert, work that earned him a patent. In 2011 he founded Qaribou, building geodata, document-processing and fintech products for civic nonprofits and large enterprises alike. B.Eng., Western University.

More about Joshua
Rajah Lehal

Rajah Lehal

Founder · Co-inventor

Rajah is a legal technologist and a technology and M&A lawyer, trained at Stikeman Elliott. Before law he spent a decade in IT, as a developer and then an information systems manager. He founded Clausehound, co-invented its patented clause taxonomy, and leads Cobalt, the firm that runs on it.

M.B.A. and J.D., Western University (Ivey and Western Law).

With engineers Ian Hume and Isaiah Liu.

Talk to us

See it run on your documents.

Licensing the platform, connecting your stack, or an engagement where our engineers set it up and run it for your legal team: we'll walk you through the app, the API and the MCP server, and talk about a deployment of your own, including on your own infrastructure.

Already a customer? Log in. Or email [email protected]. Need a lawyer? Talk to Cobalt.

Opens Calendly's booking calendar here. Calendly may set cookies.

Book a call on Calendly