S
Supio
Supio is an agentic AI platform built only for plaintiff personal injury and mass tort firms, covering the case from intake through litigation. It was founded in Seattle in 2021 by Jerry Zhou, chief executive, and Kyle Lam, chief technology officer. The platform ingests whole case files, including large volumes of medical records, and produces MedChron medical chronologies, demand letters, case economics ledgers, litigation drafts, deposition analysis and firm analytics.
Its underlying technology, CaseAware AI, is said to distinguish facts from opinions across large volumes of records. Supio Agent, launched in the first half of 2026, takes natural language instructions such as adding a life impact report to a demand section or rechecking a medical bill total. Output cites the source page for each claim, and for high value cases human experts verify bill totals and damage calculations before delivery.
Named integrations include Litify, MyCase and CasePeer, plus Westlaw Advantage through a Thomson Reuters partnership. The vendor states SOC 2 Type II certification, HIPAA, PHIPA and GDPR compliance, and data centers in the US, UK and Canada. It has raised about $85m to $91m. Pricing is not published.
Supio, head to head
Side by side on the same 15 capability axes and 12 legal signals: where the two part company, and what neither one publishes.
Alternatives to Supio
Vendors in the same categories as Supio whose graded profiles look most alike, with a line on what each product does.
Similar is not the same, so check that each one does the job you need. No vendor pays for placement.
- TTavrnTavrn is an AI case preparation platform for personal injury litigation, founded in 2022 and built around medical record retrieval, on the premise that records are where cases stall.
- EEvenUpEvenUp is a vertical AI platform built only for plaintiff personal injury firms, marketed as a Claims Intelligence Platform.
- AAnytime AIAnytime AI is an agentic AI platform sold only to plaintiff law firms, covering a case from intake through settlement.
- CCodes HealthCodes Health retrieves and reviews medical records for plaintiff personal injury and mass tort firms.
- DDigitalOwlDigitalOwl analyzes medical records with AI for both legal and insurance professionals.
- EEveEve is an AI platform for plaintiff law firms, covering the case from intake to resolution.
Ordered by how closely the graded profiles match across the 15 capability axes, inside the same categories. See how each axis is graded in the methodology.
Capability grades
All 15 axes, graded from public sources on the date shown. Hover a grade to see what the letter means on that axis.
AI Centrality
How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.
Supio was founded in 2021 to build this product, with no earlier product to attach models to. CaseAware AI is named as its proprietary technology, described as distinguishing facts from opinions across large volumes of records, which is a claim about what the model does. Every deliverable is generated: chronologies from raw medical records, demand letters, case economics ledgers, litigation drafts and deposition analysis.
Supio Agent, launched in the first half of 2026, is directed by natural language instruction rather than configured through forms, an agentic design rather than an assistant added to a case system. Without the models there is no product, only a connection to case management systems the firm already owns.
Citation Accuracy and Hallucination Disclosure
Whether the vendor publishes measured accuracy on citations and assertions, grounds output to primary sources, and says plainly what its system does when it does not know. Legal has a documented public record of fabricated citations reaching filed briefs, so an untested claim of accuracy is not evidence.
Grounding is built in, with no published measurement. Citations point to the page of the source document for any claim in a demand, the right level of detail for medical records, where one treatment note in a 400 page file may be the evidence. Checking is also built into the workflow: for high value cases, human experts verify medical bill totals and damage calculations before delivery, targeting the arithmetic most likely to be wrong and most costly if it is.
Nothing measured is published: no extraction accuracy, recall on treatment events, error rate on bill totals, or evaluation of CaseAware's separation of facts from opinions. Nothing says what happens when records are illegible, contradictory or incomplete. The one circulating figure, 80 or more hours saved per case, measures speed, not accuracy, and independent material reporting it notes that most such figures come from vendor marketing.
Autonomy and Oversight Model
What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.
Oversight varies with case value, and this is published plainly. For high value cases, human experts verify medical bill totals and damage calculations, so the human check targets the numbers that drive settlement. The agentic layer works on the attorney's explicit instructions. Published examples show the lawyer specifying what to emphasize and asking the system to recheck a medical bill total, which keeps the attorney in the loop by design.
Every output is presented as a draft with linked sources for checking. The boundaries are undefined: nothing says what makes a case high value enough for expert review, what the experts check or against what standard, whether generated content carries any confidence signal, or what Supio Agent may do unattended once instructed.
Operational and Outcome Evidence
Named, dated evidence that the product works in production at real firms or legal departments. Case studies with figures and identified customers count. Unattributed testimonials and launch announcements do not.
Company milestones are well evidenced, and customer outcomes are not. Supio has raised about $85m to $91m across three rounds: a $25m Series A on leaving stealth in August 2024 and a $60m Series B in April 2025 led by Sapphire Ventures, with investors including Thomson Reuters Ventures, Mayfield, Greylock and Menlo Ventures. A strategic partnership with Thomson Reuters, expanded in 2026, is meaningful outside validation, since that company is also an investor.
Supio Agent launched in the first half of 2026. No law firm is named in the material located, and there is no case study with a method and no usage figure. The one outcome claim, 80 or more hours saved per case when combining chronologies with demand letters, has no baseline, sample or definition, and independent material notes that such figures generally come from vendors. Funding is not evidence that the product works.
Privilege and Confidentiality Posture
How client confidences are handled: attorney client privilege and work product treatment, segregation of one client matter from another, whether client data trains any model, and what the vendor commits to in writing rather than in marketing.
Health privacy credentials are broad, and legal privilege is not addressed. The vendor states SOC 2 Type II certification and compliance with HIPAA, PHIPA and GDPR. PHIPA, Ontario's Personal Health Information Protection Act, governs health information custodians in Canada. Naming it alongside Canadian data centers shows the vendor addressed a specific regional health privacy law rather than treating HIPAA as enough everywhere.
For a platform holding complete medical records of injured claimants, protecting a third party's health information under the right law is the core confidentiality question, and it is answered. Nothing addresses legal professional privilege or attorney work product, although demand strategy, case economics ledgers and litigation drafts are work product.
UPL and Professional Responsibility Posture
Whether the vendor is clear that it supplies a tool rather than legal advice, who its audience is, and how it addresses unauthorized practice of law, competence and supervision duties, and jurisdiction limits. ABA Formal Opinion 512 is the reference point. Where the advice line is not the duty a product raises, the axis is read through the nearest professional duty it does raise: judicial conduct rules and the reviewing duty for products sold only to courts, and the duty to bill for time actually spent for products that draft time entries.
Not located. The platform drafts demand letters sent under the firm's name to adverse insurers, produces litigation drafts, and generates case economics that inform settlement advice to an injured client. Nothing published addresses the supervising attorney's duty over machine drafted advocacy, the professional responsibility dimension of relying on generated damage calculations when advising a client whether to accept an offer, or any bar guidance.
The human expert verification tier is a quality control mechanism operated by the vendor rather than a statement about the attorney's own professional obligations.
AI Governance and Bias Disclosure
Published governance over model behavior: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.
Nothing is published about how the models are governed, evaluated or monitored: no AI policy, model card, bias or fairness testing, evaluation method or result, accuracy monitoring, drift statement, named governance body or ISO 42001. The product produces case economics ledgers and damage calculations that shape what an injured claimant is told their case is worth. Any systematic tendency in how the models weigh treatment, life impact or pain and suffering evidence would fall on claimants rather than on the firm, and nothing indicates it has been tested.
CaseAware is named for separating facts from opinions in medical records, an interpretive judgment about clinical documents, and nothing indicates that judgment has been evaluated.
AI Safety and Data Stewardship
Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.
Data handling is backed by several credentials, and the training question is unanswered. SOC 2 Type II, HIPAA, PHIPA and GDPR compliance show that safeguards over health and personal data have been addressed, and data centers in three countries suggest a deliberate design. Nothing says whether medical records, case files, demand drafts or deposition transcripts submitted by firms are used to train or improve CaseAware, how long client content is kept, or whether a firm can require deletion when a matter closes.
GDPR implies rights for data subjects, but an injured claimant whose records sit in the platform is not a party to the customer relationship, which makes deletion harder to arrange. A credential about how data is protected says nothing about how it is used.
AI Liability and Recourse
What the vendor stands behind contractually when its output is wrong. Indemnities, caps, carve outs, insurance, and whether any of it is published or only reachable through a negotiated agreement.
No published position located. Nothing was found on liability for AI output, warranty, service levels or remedy. The exposure is specific and asymmetric: an understated medical bill summation or a missed treatment event flows into a demand and can settle a claim below its value, and the person who bears that loss is the injured claimant, who is not a party to the contract between the firm and the vendor and has no visibility into how the number was produced.
The vendor's own answer to this risk is operational, being human verification on high value cases, rather than contractual, and no contractual position is public.
Practice Systems Integration Depth
How deeply the product reaches into the systems legal work already lives in: document management such as iManage and NetDocuments, Word and Outlook, contract lifecycle management, matter management, e-billing, and court filing systems.
The integrations a plaintiff firm needs are named. Litify, MyCase and CasePeer are case management systems where plaintiff firms keep intake, treatment tracking, deadlines and the matter file. Westlaw Advantage is integrated for legal research through a strategic partnership with Thomson Reuters, giving generated documents an established citation source. Document management integration is stated in general terms. The vendor says the platform connects to a firm's case management, records and intake systems rather than replacing them.
Depth is not documented: nothing says what moves in which direction for any named system, no authentication or permission detail or API documentation is published, and nothing says whether finished work returns to the matter file automatically.
Deployment Model and Data Residency
Where the software runs and where the data sits. Multi tenant cloud, single tenant, private deployment, on premises, and whether region of residence is a published option or an enterprise conversation.
A substantive residency statement is published. The vendor names data centers in the United States, the United Kingdom and Canada and pairs them with the matching health privacy regimes: HIPAA for the US, PHIPA for Canada, and GDPR. That suggests residency was designed around regulation, and it answers the first question a firm's compliance review asks about a vendor holding claimant medical records. The detail stops at the country list.
No hosting provider is named, nothing says whether a customer can choose or is guaranteed a region, no single tenant or dedicated option is described, and nothing says whether processing, backup and model inference all happen in the same country as storage.
Security Certifications and Trust Center
Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.
Four regimes are named, none is evidenced, and there is no route to the underlying documents. The vendor states SOC 2 Type II certification and HIPAA, PHIPA and GDPR compliance, a set that matches its data center locations. No auditing firm is named, and no examination period, scope or certificate date is published, so currency cannot be established. No trust center, security page or self serve route to request documents is published, and nothing suggests a gated one exists.
Model Supply Chain Disclosure
Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.
Nothing located. CaseAware AI is named and presented as the vendor's own technology, which is an ownership statement rather than a supply chain disclosure. No foundation model provider is named, nothing states whether third party models sit underneath CaseAware or process any part of the pipeline, and no subprocessor list is published. The Thomson Reuters and Westlaw Advantage integration establishes at least one external data relationship, and the stated three country data center footprint implies infrastructure providers, and none of those parties is identified.
For a platform processing protected health information across three regulatory regimes, the identity of every processor is a question a customer's HIPAA and PHIPA diligence asks directly and it cannot be answered from public material.
Commercial Transparency
Whether a buyer can learn what this costs without entering a sales process: published rates, the unit being charged, what sits behind an enterprise tier, and what implementation adds.
No pricing published at any level. No price, no range, no unit of charge, and no indication of whether the model is per case, per seat, per page of records processed or per demand produced, which matters because those scale very differently for a plaintiff firm and determine whether the cost is a case expense or firm overhead. Independent review notes the product is sold entirely behind a demo with no published pricing.
Every route is a sales conversation. The absence carries the same additional weight noted on EvenUp: contingency fee firms advance case costs and recover them from a claimant's settlement, so undisclosed per case pricing is undisclosed cost to an injured person.
Firm and Practice Coverage
Who the product is actually built for. AmLaw, midlaw, small firm and solo, in house departments, government and courts, and which practice areas are supported rather than merely claimed.
The scope is deliberately narrow and stated honestly, with real depth inside it. The vendor says the platform is built only for plaintiff law and is of no use outside it, and independent review agrees. Within that scope it covers the whole case lifecycle: intake, medical chronologies, demand letters, case economics ledgers, litigation drafting, deposition analysis and firm analytics. Mass tort is named alongside personal injury, a different workload of thousands of claimants against common defendants.
Coverage is not described at the level a buyer would check. Nothing says which record types, providers or formats ingestion handles, what jurisdictions the litigation drafting covers, or how deep the mass tort support is compared with single plaintiff work.
1 public document
The public pages on file for Supio, with the recorded signals each one supports and the date it was last read. Open any of them and check the reading against the record.
-
Client Data in Training
Read Aug 29, 2026
Legal Signals
What each signal meansA signal records what public sources say on the date shown. It is not a grade and it is not a recommendation. Where a signal reads Not addressed, it means the index did not locate the material in public sources on that date, which is a statement about disclosure rather than about the product.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
A published agreement or policy exists and none of it addresses the question either way, or the document that would answer it could not be read and the summary names the retrieval limit. The summary states which shape the silence takes: an improvement right granted that never names training, or no improvement right granted at all.
Silent. No vendor statement on model training was located, so the quoted phrase comes from the demand letter page and shows the level at which the vendor describes data handling: checking output rather than use of input. Nothing says either way whether medical records, case files, demand drafts or deposition transcripts submitted by firms train or improve CaseAware. SOC 2 Type II, HIPAA, PHIPA and GDPR compliance describe how data is protected, not what it is used for.
There is also a third party dimension. The health information belongs to an injured claimant who is not a party to the contract between firm and vendor, so a training use they cannot see or object to differs from a customer consenting for itself. Checked the product pages, the demand letter page, the press page and the site navigation on 29 Aug 2026.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
No located public material states how long prompts and outputs are retained.
Not addressed. No retention period is published for ingested medical records, generated chronologies, demand drafts, case economics ledgers or agent instructions, and nothing indicates whether a firm can require deletion at matter close or settlement. Stated GDPR compliance implies erasure machinery exists for personal data, and nothing published describes how it operates for claimant health records held on a customer's behalf. Checked the product pages, the press page and the site navigation on 29 Aug 2026.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
No located public material addresses walls or matter level segregation.
Not addressed. No permission model, matter level access restriction or tenant segregation description was located. The mass tort dimension makes this sharper than for a single plaintiff product: a mass tort workload involves thousands of claimants against common defendants, often with multiple firms coordinating, and nothing published describes how one firm's claimant records and work product are separated from another's inside a platform serving the same litigation from both sides of a co counsel arrangement.
Integrations exist with case management systems that hold their own permission models, and nothing states whether Supio inherits them. Checked the product pages and the site navigation on 29 Aug 2026.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
No located term or policy addresses third party requests for customer data.
Not addressed. No government or law enforcement request clause, no commitment to notify a customer before producing their data, and no transparency report were located. The stakes are high: the vendor holds claimant protected health information, unsent demand material and litigation drafts across three jurisdictions with different legal process regimes, and a request served in one country against data stored there is not the same event as one served on the firm.
Nothing published addresses any of it. Checked the product pages, the press page and the site navigation on 29 Aug 2026.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
No located public material identifies the corpus behind the product’s answers.
Not addressed, and mostly not applicable, with one open question. The platform works on the customer's own case files, medical records and transcripts rather than a published legal collection, so there is no outside legal source to name or license. Legal authority arrives through the Westlaw Advantage integration, whose content belongs to Thomson Reuters. The open question is what CaseAware was trained on. Separating facts from opinions in clinical documents implies a large body of medical records, and nothing says whether it was licensed, synthetic, public or built from customer matters.
No settlement or verdict database is named as a separate asset. Checked the product pages, the press page and the site navigation on 29 Aug 2026.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
No located public material addresses whether authority is checked for subsequent history.
Not addressed, and the question does apply. The product writes litigation drafts and integrates Westlaw Advantage for legal research, so legal authority reaches its output. Nothing says whether cited authority is checked for current treatment before it appears in a draft, whether the Westlaw integration carries KeyCite treatment data or only citations, or whether an overruled or superseded case would be flagged. Checked the product pages, the press page and the integration references on 29 Aug 2026.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
No located public material addresses what the product does when it cannot ground an answer.
Not addressed. Nothing describes a no answer path, abstention behavior or confidence signal. CaseAware is named for separating facts from opinions in medical records, which is a sorting capability, not behavior under uncertainty. Nothing says what happens when a record is illegible, when two providers record contradictory findings, or when a gap in treatment cannot be explained from the file. Human verification on high value cases is a check after generation, not a behavior of the system, and it does not cover every case.
A chronology that reads as complete over an incomplete record is the dangerous output here, and nothing indicates it would be flagged. Checked the product pages, the demand letter page and the site navigation on 29 Aug 2026.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
No court order, opinion or disciplinary record addressing fabricated or hallucinated legal citations produced by this product has been located as of the date shown. This is a statement about the public record on that one subject, not a finding about the product, and this signal is not a litigation history.
None located, with the instrument named. General web searches combining the vendor and product names with court, order, sanction, fabricated citation and demand letter terms returned nothing on 29 Aug 2026, and no named docket database or court record tracker was searched. This is a statement about what this search found, not a clearance. The exposure shape is broader than for a demand only product because Supio also generates litigation drafts, which are filed with courts rather than sent to insurers, so a defective citation in that output would reach a docket directly.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
No located public material engages with bar or ethics guidance.
Not addressed. No named ethics opinion, no ABA Formal Opinion 512, no state bar guidance and no engagement with professional conduct rules was located. Relevance is direct: the platform produces litigation drafts filed under an attorney's signature and case economics that inform settlement advice, both of which sit inside the competence, candor and supervision duties that bar guidance on AI addresses. Checked the product pages, the press page, the company material and the site navigation on 29 Aug 2026.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Public materials claim time savings without addressing billing or disclosure, and the product sits inside a fee relationship between a lawyer and a client where those savings would change the bill.
Savings claims only. The published figure is 80 or more hours saved per case when combining AI chronologies with demand letters, which describes the firm's own labor and has no baseline, sample or definition; independent material notes that most such figures come from vendor marketing. Nothing addresses the claimant's side, which matters most in contingency work, where the firm advances case costs and recovers them from the settlement.
Nothing says whether platform cost is a case expense or firm overhead, how it is disclosed to the client, or what record could show how much of a demand was machine generated. Checked the product pages, the demand letter page and independent review material on 29 Aug 2026.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
No located public material supports a client side disclosure obligation.
Not addressed. Four compliance regimes are named, SOC 2 Type II, HIPAA, PHIPA and GDPR, along with data center locations, which gives a firm real content for a client questionnaire. Nothing underneath was located: no trust center, security page, request path for the SOC 2 report, subprocessor list, named model provider or business associate agreement material. A firm could repeat the vendor's claims but could not evidence them or say which third parties process claimant health data.
A list of claims without a way to request the documents is not a disclosure pack. Checked the product pages, the press page and the site navigation on 29 Aug 2026.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
Some elements of the record are available, short of a document level export.
A partial record exists, with a strong source trail. Citations point to the page of the source document for any claim, so a party can show the exact page of a medical record behind a factual statement in a demand or litigation draft, which is what an opposing party or a court would test. For high value cases, human experts verify bill totals and damage calculations, so a verification step does occur. Two gaps remain: nothing indicates that output records which model produced it, and no record of the human verification reaches the customer, so a firm cannot show the check happened even when it did. Litigation drafts bring this into the courtroom, not only the claim file.