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.
From your agent: two cited changes, not two consolidations of the Act.
queryFindings($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.
DocumentEmployment Standards Act, 2000 · S.O. 2000, c. 41
VersionAs it read from 2009-11-06 · immutable
ClusterPart VII › Hours of work › s. 17
Clause17 (1) The provision text, with its stable identity
TagsAttached 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.
Clausehound · AI Insights
Welcome
How do you want to review?
Both run the same prompts against the same documents. Guided stops at every one and can change your text; autonomous runs straight through and reports back.
Guided
Guided review
Work one prompt at a time. Read the response beside its source clauses and approve each change before moving on.
ReportPick a saved prompt set.
PromptsQueue the ones to run.
AnalyzeResponse, sources, findings, per prompt.
ApplyApprove changes.
Best for a first run of a playbook, or contracts you have to get exactly right.
Get started →Writes to your documents
Autonomous
Autonomous analysis
Runs every prompt against every document, then checks each suggestion against the paragraph it came from. You read the findings in one place and export them.
ReportPick a saved prompt set.
AnalyzeEverything runs unattended.
ReviewRead the findings and the comparisons.
Export & ShareDownload the report.
Best for sizing up a portfolio, or a playbook you already trust.
Read a whole report →Read-only, ends in a .docx
Pick a flow: step through each prompt, or run a whole playbook built from your team's own precedent. Watch the walkthroughs
Guided review · Services Agreement Playbook
Report
Prompts
Analyze
Apply
In review
Information security
Response
Sources
Findings
Summary
Vendor may use aggregated, anonymous or de-identified data derived from the Client's
data solely for analytical purposes, in any manner Vendor shall see fit; however, Vendor shall not use the Client's data for training or improving any artificial intelligence models without the Client's prior written consent.
Approve changeRejectApproved edits are applied together in Step 4.
Guided: the suggested change as a redline. Nothing is written until someone approves it.
Autonomous analysis · NDA review · read-only
Report
Analyze
Review
Export & Share
Step 3 · Review
10 findings to review
Read every finding beside the paragraph it was compared against.
7
Inadequate
3
Aligned
Definition of confidential informationInadequate
Return of materialsAligned
Liability for breachInadequate
WordReport, plus one .docx per document with suggested edits as tracked changes
Choose folder…
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."
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.
ESA 2000, Part VII, s. 17 · version 2004-03-01Weekly hours capped at 48 without an agreementVerified
ESA 2000, Part VII, s. 17 (3) · version 2004-03-01Excess hours need written agreement and Director approvalVerified
ESA 2000, s. 74.19 · not in version 2004-03-01Temporary help agency obligationsFlagged
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.
Or point any agent at Clausehound from its settings.
MCP tools find_statutes, list_statute_versions, search_statute_text, compare_statute_versions, fill_schedule and more, over JSON-RPC.
Documents in PDF, Word and official statute consolidations, parsed into the clause tree.
Results out CSV, JSON and Excel of any analysis, or Word with suggested edits as tracked changes.
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.
2016
Clausehound starts: contracts as structured clauses, not files.
2018
Joins Seneca HELIX, the start of a long research partnership with Seneca.
2020
Machine learning on clauses with Seneca College: flagging problem clauses against a client's own precedent.
2022
Patent filed for the clause taxonomy: breaking legal documents into typed, nested clauses that can be versioned, compared and analysed as data.
2023
Large language models built into the platform, with people verifying every result.
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
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.
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.