Ironclad vs Sirion: how they compare in 2026

I
Ironclad profile
S
Sirion profile
Last verifiedOctober 8, 2026

Ironclad and Sirion are two enterprise contract lifecycle platforms that meet in the same procurement, and very little separates them. Both publish their customer terms. Ironclad's Enterprise Services Agreement caps liability at a year of fees, triples the cap for data breaches and indemnifies customer data leaks it causes. Its subprocessor list names Anthropic, OpenAI and Extend. Sirion's SaaS terms also cap liability at a year of fees, and its data processing addendum sets deletion within 30 days of termination and a 72 hour incident notice. What differs is emphasis. Ironclad publishes more of the control surface. Administrators set who may view, create and edit the playbooks that drive AI behavior. Its certifications name SOC 1 and SOC 2 Type II with their trust categories, alongside four ISO standards. Sirion publishes more of the plumbing, with nine connectors documented by direction. On training, Ironclad makes it opt in by contract, while Sirion's terms let its systems process customer data to inform machine learning.

At a glance

Category
IroncladContract Review & Drafting
SirionContract Review & Drafting
Founded
Ironclad2014
Sirion2012
Headquarters
IroncladSan Francisco, California, United States
SirionLehi, Utah, United States
Last verified
IroncladOct 14, 2026
SirionOct 8, 2026

All 15 axes, side by side

The same grid applied to every vendor in the index, graded from public sources. 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.

Ironclad
BB on AI CentralityThe models are the engine of a core capability, layered on a product that would still function without them as a document or workflow system.

Intake, the no code Workflow Designer, approvals, signature, the repository and analytics run without AI, and Ironclad sells that system of record as the base of the platform. Ironclad AI sits on top of it. Ironclad Agent takes a plain language request and returns the answer, the contract or the workflow, or hands the task to a specialized agent. Contract Review Agent redlines third party paper against playbooks and, in early access, precedent, Intake Agent pulls terms into launch forms, Renewal Agent briefs upcoming renewals, and Analytics Agent charts contracting data. The agents act on live workflow state, such as where a contract sits in approval, as well as on documents. The contract platform predates generative AI and would still work without the models.

Sirion
BB on AI CentralityThe models are the engine of a core capability, layered on a product that would still function without them as a document or workflow system.

Sirion's contract lifecycle platform came before its AI, and the company has traded since 2012. The product is organized as Store, Create and Manage, covering repository, drafting, approval, negotiation, obligation tracking and performance management. Without the agents and agentOS, a working enterprise CLM remains, and Gartner classifies it as one. The models drive the capability Sirion now sells on top of it. Agents are described as extracting and normalizing contracts, assembling first drafts from a playbook, proposing redlines on the other side's paper and monitoring obligations. Customers can also build and deploy their own agents in agentOS.

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.

Ironclad
BB on Citation Accuracy and Hallucination DisclosureGrounding is real and documented, with linked primary sources and a described retrieval method, short of published accuracy figures an outsider can test.

Extraction uses two passes to connect values to source text. The model returns each value with a description of where it sits in the contract. A second pass ties that value to the exact OCR tokens, so the interface highlights the passage with its page and position. If the model returns no match, the system tries the raw text and then the normalized value before giving up on a location. Contract Review Agent bases redlines on the customer's playbooks and templates, with precedent based redlining in early access, and redlines can show their rationale. Answers through the MCP connectors link back to the contract in Ironclad. No accuracy figure, error rate or test set is available, and the AI Addendum says output may be incorrect or inaccurate.

Sirion
BB on Citation Accuracy and Hallucination DisclosureGrounding is real and documented, with linked primary sources and a described retrieval method, short of published accuracy figures an outsider can test.

AskSirion answers questions within one agreement or across the enterprise contract corpus, combining relevant clauses with related obligations, service levels, and counterparty records. Each answer links back to its underlying source, and the interface explains how it interpreted the user's request. Follow-up questions preserve context, while summaries, financial calculations, and date calculations draw on the same contract information. Retrieval over the customer's agreements is therefore traceable. Sirion describes no externally reproducible accuracy evaluation, error breakdown, or legal citator. References to an agreement establish the source of a commercial term, rather than verifying that an external legal authority remains current.

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.

Ironclad
BB on Autonomy and Oversight ModelA written commitment that the models work alongside a supervising lawyer, with real review surfaces, short of the full control structure: commonly the threshold at which the system stops or what happens after it is wrong.

Ironclad Agent routes each request to the right agent or workflow, and the agents work inside existing contracting workflows under the user's permissions. Contract Review Agent proposes redlines, flags risk and applies positions in Ironclad or directly in Microsoft Word, with the final decision left to the reviewer. Playbooks set preferred positions and fallbacks, and answers through the MCP connectors are limited to contracts the user can already open. The AI Addendum makes the customer responsible for reviewing and validating output before using it, and says the AI products are no substitute for human oversight. Agent stop conditions, handback routes and limits on work completed without a person are not specified.

Sirion
BB on Autonomy and Oversight ModelA written commitment that the models work alongside a supervising lawyer, with real review surfaces, short of the full control structure: commonly the threshold at which the system stops or what happens after it is wrong.

AskSirion interprets a request and orchestrates agents for drafting, redlining, extraction, obligation tracking, and invoice reconciliation. Custom agent setup uses ordinary language to define the task, accessible data, connected systems, and when to escalate to the user. Agents can be tested with real scenarios and refined after launch. Recommendations include explanations and source links that allow review against the underlying contract. This gives administrators an escalation mechanism beyond a general promise of human control. Sirion does not describe default stop conditions, the approval interface for consequential actions, or recovery after an incorrect action. The launch sequence permits an agent to go live before subsequent scenario testing.

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.

Ironclad
BB on Operational and Outcome EvidenceReal deployment evidence with substance, short of full attribution or measurement: a named customer without figures, or figures without the named customer.

Named customers report figures. NEXT Insurance says Contract Review Agent gave legal operations half its time back, and AES reports first pass redlines that took 30 minutes to two hours now reach a first draft in minutes. Signifyd puts an MNDA review or custom order form clause at minutes rather than an hour to a day, and Hormel's senior counsel reports turnaround cut from 12 weeks to 3. A Forrester study drawn from five customer organizations puts the three year return at 314 percent. Apart from that study, the figures come from the customers themselves, undated and with no method stated.

Sirion
BB on Operational and Outcome EvidenceReal deployment evidence with substance, short of full attribution or measurement: a named customer without figures, or figures without the named customer.

Three customer representatives speak on the record with their roles and employers. Edzard Janssen is Chief Procurement Officer at RBI. Reinhard Plaza-Bartsch is Head of Digital Supply Chain and Operations at Vodafone. Angella Dikmic is Manager of IT Vendor Management at GTAA. All three quotes are qualitative, and all three people work in procurement or vendor management rather than legal. The five percentage claims name no customer and read as product capabilities, so named customers and published figures are never paired. About 25 enterprise logos appear, including Citi, GE, Coca-Cola, Chevron, PayPal, Bayer, Rolls-Royce, Aramco, Yamaha, DP World and Zalando. Customers are in more than 70 countries, with more than $450 billion of contract value under management. Sirion also publishes a case study library.

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.

Ironclad
BB on Privilege and Confidentiality PostureSubstantive published commitments on confidentiality and training use, short of the full picture: commonly silence on segregation between users or matters, or on what the underlying model provider may retain.

Training of Ironclad's own models on customer data, input and output starts only after a customer enables AI Training Settings in the admin console, under the AI Addendum. An opt out stops new training from that date. That data is first de identified, anonymized and aggregated, and output for other customers may not contain it. Whether or not a customer opts in, Ironclad may use input and output to evaluate the performance and accuracy of the service. External model providers may not train on customer data and run under zero data retention where available. The Enterprise Services Agreement treats customer data as confidential information, and SOC 2 covers the privacy category. The terms say nothing about attorney client privilege or work product, and access follows roles without specified matter boundaries.

Sirion
BB on Privilege and Confidentiality PostureSubstantive published commitments on confidentiality and training use, short of the full picture: commonly silence on segregation between users or matters, or on what the underlying model provider may retain.

Vendor library articles say customer data stays within the customer environment and is not used to train external language models. Clause 4.2 of the SaaS Terms, version 6, modified 26 August 2026, says otherwise. It reserves a right for Sirion to have its automated systems review and process Customer Data to generally inform machine learning capabilities in the services. None of the published agreements offers an opt out, and the agreement, not the library articles, is what binds. The rest of the confidentiality framework is published and can be read before signing. The data processing addendum stores and processes all customer data in a Sirion application instance specific to the customer. It sets Article 32 technical and organizational measures, with AES-256 at rest and TLS 1.2 in transit. It imposes need to know and least privilege access with automatic logout, requires deletion within 30 days of termination, and commits to notifying the customer of a confirmed security incident within 72 hours. Section 5 of the SaaS Terms adds mutual confidentiality, with a duty to give prior notice of any authority or court demand so the other party can object. The published agreements and trust center do not address privilege or 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.

Ironclad
CC on UPL and Professional Responsibility PostureA boilerplate disclaimer sits in the terms while the marketing describes the product in advice terms, or the intended audience is left ambiguous.

Ironclad markets its AI to legal teams and to sales, procurement and operations users, and describes the platform as built for everyone, lawyers or not. Its AI Addendum states that Ironclad is not the customer's legal advisor, that using the AI products creates no attorney client relationship, and that the customer should consult its own counsel. A separate AI Disclaimer says output is not legal advice and should be verified with a licensed professional before anyone acts on it. Neither document addresses competence or supervision duties, or which jurisdictions the product suits.

Sirion
DD on UPL and Professional Responsibility PostureNothing published on the advice line for a product that produces legal work, including where it is sold to people who are not lawyers.

The platform is sold to procurement, sales and finance teams as well as in house legal, all working on the same contracts. The three customer referees Sirion features are procurement and vendor management leaders, not lawyers. The home page, the trust center index with its AI ethics, compliance and security sections, and the terms and policies index say nothing on where tooling ends and legal advice begins. There is no statement that Sirion does not give legal advice, no professional responsibility or ethics page, no named bar or ethics guidance, including ABA Formal Opinion 512, and no jurisdiction limits.

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.

Ironclad
BB on AI Governance and Bias DisclosureA published governance framework with real substance, short of testing results or a named owner.

Every AI feature, Ironclad says, passes through its Evaluation Framework, which measures accuracy, consistency and reliability against curated benchmarks and real contract data. Subject matter experts validate model output during development and after release, with feedback loops meant to catch bias early, and training data is chosen to cover varied contract types and jurisdictions. Dimitry Dukhovny, the chief information security officer, leads security, compliance and AI governance. Customers can review, override and keep governing agent behavior across teams and contract types. Evaluation results and performance differences by contract type, jurisdiction or party are not available.

Sirion
DD on AI Governance and Bias DisclosureNo governance position published for a system whose output affects legal outcomes.

The trust center has a section titled Artificial Intelligence Ethics and Governance, last modified 16 December 2025, and its whole content is three sentences. They say Sirion has set up an AI Governance Program called S-AIGP, which monitors and ensures compliance with the EU AI Act 2024/1689 and other AI regulations as they emerge. Readers are told to contact their Sirion Account Executive for more. Sirion publishes nothing on who owns model behavior, what is tested before release, how the program works, or bias and uneven output.

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.

Ironclad
AA on AI Safety and Data StewardshipRetention, deletion, access control, subprocessors and incident practice are all published, current, and specific enough to hold the vendor to.

Storage of customer personal data is limited to what the services need under Ironclad's Data Processing Addendum, version 3.10 from 5 March 2026. It destroys all copies, archives included, within 90 days of the agreement ending, returns data within 30 days on request and issues a deletion certificate within 30 days. A security incident is reported to the customer within 48 hours of Ironclad becoming aware of it. The subprocessor list names each provider, its activity and its location for the United States platform, the EU datacenter and Clickwrap. A new subprocessor comes with 30 days' email notice and a right to object. External model providers run under zero data retention and may not train on customer data. Data is encrypted with TLS 1.2 or higher in transit and AES 256 at rest, with per tenant keys and bring or hold your own key options, and access follows administrator set roles.

Sirion
AA on AI Safety and Data StewardshipRetention, deletion, access control, subprocessors and incident practice are all published, current, and specific enough to hold the vendor to.

The data processing addendum, version 3, modified 2 July 2026, covers retention, access, subprocessors, incidents and encryption. Appendix B sets the retention period by the controller's contractual direction. Clause 8.1 requires deletion or return of all Customer Personal Data, including copies, within 30 days of termination. Any retention the law requires is limited to that purpose and stays under the agreement's protections, and the SaaS Terms add automatic deletion after 30 days as a backstop. Access runs on a need to know and least privilege basis, with automatic logout on inactivity. Subprocessors are named in a list published at its own URL. Sirion gives notice and an objection right for any addition or replacement, imposes equivalent terms on each, and is liable for their breaches. Clause 4.3 commits Sirion to notify the customer within 72 hours of establishing material impact from a confirmed Security Incident, and Appendix B says 48 to 72 hours, with updates until resolved. The definition expressly excludes unsuccessful attempts such as failed logins and denial of service attempts. Encryption is AES-256 at rest and TLS 1.2 in transit.

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.

Ironclad
AA on AI Liability and RecourseWhat the vendor stands behind when its output is wrong is published and specific: indemnity scope, caps, carve outs, and any insurance or warranty a buyer can actually invoke.

The Enterprise Services Agreement, version 2.2 effective July 2026, governs warranties and financial remedies. Ironclad defends and indemnifies customers against third party claims that the platform infringes intellectual property, and against claims from unauthorized disclosure of customer data caused by its breach of the data and security terms. It warrants that the services materially conform to the agreement and comply with applicable law; if a nonconformity is not fixed within 30 days, the customer may terminate for a pro rata refund. Liability is capped at the fees paid in the prior twelve months, rising to three times that amount for data and confidentiality breaches and the data indemnity. Gross negligence, intentional misconduct and the intellectual property indemnity sit outside the cap, and consequential loss is excluded. The service level schedule targets 99.7 percent uptime, with service credits as the remedy. The customer bears sole responsibility for results from AI output, which Ironclad does not warrant as accurate, and the agreement carries no insurance commitment.

Sirion
AA on AI Liability and RecourseWhat the vendor stands behind when its output is wrong is published and specific: indemnity scope, caps, carve outs, and any insurance or warranty a buyer can actually invoke.

Sirion publishes its SaaS terms and a separate end user agreement, so both can be read before signing. Clause 7.1 commits Sirion to indemnify and defend the customer against third party claims that use of the services infringes intellectual property. Clause 7.2 sets four exclusions, namely combination with materials Sirion did not provide, unapproved changes, unauthorized use, and use inconsistent with the documentation. Clause 7.3 gives the remedies of securing the right to continue, replacing or modifying the services, or terminating with a pro rata refund of prepaid fees, as Sirion's sole and exclusive liability. Clause 7.4 has the customer indemnify Sirion over customer data. Clause 8.1 caps each party's total liability, across the whole term, at the fees paid for the subscription in the twelve months before the first event giving rise to a claim. Clause 8.2 excludes lost profits, lost or damaged data and consequential loss, and under clause 8.3 the cap does not apply to fees owed, breach of confidentiality or the indemnities. Clause 6.2 warrants that the services perform materially in line with the documentation, with a pro rata refund if Sirion cannot correct a nonconformity reported within ten days. Separate Sirion AI Services terms extend the intellectual property indemnity to the AI features, but exclude claims that come from the customer failing to review or validate output. Section 5.1 of those terms disclaims any warranty that output is accurate or free from hallucinations. No insurance position is published.

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.

Ironclad
BB on Practice Systems Integration DepthReal integrations exist and are documented, short of depth: named connections without a description of what they actually move.

Three routes connect Ironclad to other systems: native integrations, iPaaS connections to more than 8,000 applications, and an API, with Tray, Zapier and MuleSoft in its directory. The directory names Salesforce, which is AppExchange approved, Coupa, SAP, NetSuite, Zip and Ramp, Microsoft Word and Teams, Slack, DocuSign and Adobe Acrobat Sign, and Box, Google Drive, OneDrive, Dropbox and Egnyte. MCP connectors answer questions about contracts and workflow status in Claude, ChatGPT and Slackbot, scoped to the user's permissions and linked back to Ironclad. No iManage or NetDocuments connector is identified, and the directory does not specify individual field mappings or sync directions.

Sirion
AA on Practice Systems Integration DepthDocumented, verifiable integrations into the systems legal work already lives in, with the depth described: what syncs, in which direction, and what a firm must configure.

Nine named connectors are documented, each with its direction of travel, in the Non-Native Integrations article in Sirion University, last updated 24 February 2026. Four SAP Ariba accelerators cover procurement, bids, awards and contract workspaces. An executed contract request in Sirion creates a purchase requisition in Ariba, and the resulting purchase order is written back. Ariba sourcing events and RFPs become Contract Draft Requests on set triggers, one per bidding supplier with line items mapped, and supplier redlines move into Sirion for legal review. Awarded RFx events create a draft request with awarded line items synced. Contracts finalized in Sirion copy into Ariba Contract Workspaces with metadata, documents, line items and status. Three more connectors cover supplier master data from Ariba, SAP S/4HANA Business Partners on scheduled transfers, and Oracle ERP with logging, error handling and sync status. The Microsoft Dynamics connector runs both ways in auto or manual mode. The article describes configuration through triggers, modes and scheduling rather than as a full guide, and the wider Sirion University catalog needs a login. Sirion's openly accessible web pages do not document the Word add in or the Salesforce connector to this depth. No document management connector such as iManage or NetDocuments appears on them.

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.

Ironclad
BB on Deployment Model and Data ResidencyDeployment model is stated clearly with partial residency detail, or residency is offered without the processing location being addressed, or the tenancy model is stated on its own with no residency detail published.

Hosting is on Google Cloud Platform, across multiple zones in the United States, with a separate EU datacenter. For EU hosted customers the subprocessor list places Anthropic and OpenAI, along with Elastic Cloud, Datadog and the product database, in the EU, so AI processing stays in that region too. Clickwrap runs separately on Amazon Web Services in the United States. Customers can bring or hold their own encryption keys. Ironclad does not describe a tenancy model or what changes between plans.

Sirion
BB on Deployment Model and Data ResidencyDeployment model is stated clearly with partial residency detail, or residency is offered without the processing location being addressed, or the tenancy model is stated on its own with no residency detail published.

Sirion's application is SaaS hosted by a cloud provider, according to the data processing addendum, and all customer data is stored and processed in a Sirion application instance specific to that customer. That isolation commitment sits in a contract rather than in marketing. Four underlying providers appear in the trust center, namely AWS, Azure, Oracle and IBM, which suggests customer choice without offering it as an option. Sirion's published documents make no residency commitment and give no region list or jurisdiction option. Nothing separates where processing happens from where data is stored. A Sirion library article describes the platform's multitenant scalability, which sits awkwardly beside the addendum's customer specific instance, and nothing published reconciles the two.

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.

Ironclad
BB on Security Certifications and Trust CenterCertification is real and stated, short of accessible evidence: a named standard without scope, date, or a way to obtain the report.

Ironclad holds SOC 1 and SOC 2 Type II reports from routine third party audits covering security, availability, confidentiality and privacy, along with ISO 27001, 27701, 27017 and 27018. It runs a GDPR program with standard contractual clauses, complies with HIPAA and holds Cloud Security Alliance Trusted Cloud Provider status, with a public CAIQ on the alliance's site. Penetration tests run each year and vulnerability tests each quarter, and disaster recovery is tested twice a year. Certification documents are requested through a security portal, and the website gives no auditor, audit period or report date.

Sirion
BB on Security Certifications and Trust CenterCertification is real and stated, short of accessible evidence: a named standard without scope, date, or a way to obtain the report.

Appendix B of the data processing addendum names ISO 27001 as a held certification and describes the review process around it. Under clause 7.1, unless agreed otherwise, Sirion will give a copy of its latest security attestation report on the customer's written request, no more than once a year. Clause 7.2 adds a customer audit right, with scope, timing and controls agreed in advance and a reasonable fee. Appendix B also says Sirion reviews its cloud providers' SOC 1, SOC 2 and ISO 27001 reports as part of a shared responsibility model. That is oversight of the infrastructure rather than an attestation over the application. The report route is open to existing customers, so a prospective customer cannot get the report before signing. The addendum names no auditor, coverage period or scope statement for the ISO certificate. Sirion's trust center states ISO 27001:2022 certification. Its SOC 1 Type II and SOC 2 Type II sections explain what those reports cover, and its security page attributes SOC 1 and SOC 2 to the cloud providers Sirion runs on.

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.

Ironclad
BB on Model Supply Chain DisclosureThe supply chain is partly disclosed: providers named without change notification, or architecture described without the providers.

Contract Review Agent uses models from Google Gemini, OpenAI and Anthropic, chosen for quality, latency and performance, and Ironclad says it evaluates and swaps in models as they change. Its own models, which learn from aggregated, anonymized data of customers who opt in, sit alongside them. The subprocessor list names Anthropic, OpenAI and Extend for AI and Google Cloud Platform for cloud and AI infrastructure, each in the United States or the EU. A new subprocessor brings 30 days' email notice and a right to object, and AI subprocessors run under zero data retention where available and may not train on customer data. Ironclad does not say which model serves which agent, and a change of model within an existing provider triggers no notice.

Sirion
BB on Model Supply Chain DisclosureThe supply chain is partly disclosed: providers named without change notification, or architecture described without the providers.

A combination of more than ten large language models and more than 1,200 proprietary small language models powers the contract agents. A routing framework selects a model according to the task, while company content, policies, and risk preferences can refine agent behavior. The same architecture supports extraction, drafting, redlines, obligations, and invoice reconciliation through agentOS. Provider names, model families and versions, and processing locations for individual inference tasks are not identified. There is also no model change notification commitment attached to this architecture description. The disclosure explains how different model types are combined without identifying every external model a customer inherits.

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.

Ironclad
BB on Commercial TransparencyReal pricing is published for part of the range, with enterprise tiers withheld, or the unit and structure are stated without the figure.

The base CLM, AI assistant and eSignature products use a custom quote, with deployment led by the customer, Ironclad's legal engineers or a partner. API connections, integrations, extra instances and support plans can add charges. Eligible agents consume a shared pool of AI Credits, with additional use billed at $1 per unit unless administrators enable a cap or buy prepaid packs. Not every AI feature uses those credits, and existing Contract Review Agent seat arrangements continue through the current contract term. Playbook creation and optimization require Professional Services; precedent redlining and Playbook Agent are in early access. A starting platform rate and fixed implementation fee are not specified.

Sirion
DD on Commercial TransparencyNo pricing information published at any level, including the unit of charge.

No pricing is published at any level, including the unit of charge. Sirion's site has no pricing page, no tier structure, no unit per seat, per contract or per agent, no volume banding and no statement of what implementation adds. Every call to action is a demo request. No published figure lets a prospective customer estimate cost before a sales process, even though Sirion publishes its SaaS terms, end user agreement and data processing addendum in full.

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.

Ironclad
BB on Firm and Practice CoverageSegment and practice coverage is described with substance, short of the boundaries: what is supported is clear, what is not is left open.

Enterprise and growing companies are Ironclad's buyers, with dedicated pages for general counsel, legal operations, procurement, sales and IT. It describes the platform as handling every contract type, from legal and sales to finance, HR, marketing and procurement, from intake through renewal. Named customers include Mastercard, L'Oreal, Cisco, Docker, Gusto and Rippling. The platform centers on contracting, while Contract Review Agent also supports legal questions with embedded citations. Ironclad does not say which organization sizes or contract types it does not serve.

Sirion
BB on Firm and Practice CoverageSegment and practice coverage is described with substance, short of the boundaries: what is supported is clear, what is not is left open.

Eight industries have their own pages. Financial services is split into procurement and into capital markets and lending. Insurance has a separate solution for triaging underwriting submissions. The others are automotive, IT services, healthcare, pharmaceuticals and life sciences, telecom, and oil and gas. Five departments have their own pages, covering in house legal, legal operations, procurement, sales and finance. Customers are in more than 70 countries, and the site is in English, German and French. Sirion does not say where the product stops. It excludes no contract or matter types, does not address law firms, government or public sector use, and describes coverage by industry and department rather than area of law.

The 12 legal signals, side by side

Recorded rather than graded. These are the questions a practitioner has to answer before a tool touches a client matter, and the answers are taken from public material only.

Client Data in Training

Can material a lawyer puts into this product be used to train a model?

Ironclad
Opt in

Section 1.1 of the AI Addendum, version 2.1 from 20 April 2026, lets Ironclad train its own models on customer data, input and output once the customer turns on AI Training Settings. The data is de identified, anonymized and aggregated first, an opt out stops new training but not training already under way, and external model providers may never train on it. Ironclad's product FAQ says the default setting depends on the customer's agreement and data location.

Sirion
Permitted, in the contract

Library material from Sirion states that customer data stays within the customer environment and is not used to train external language models. Its SaaS Terms, version 6, modified 26 August 2026, reserve the opposite at clause 4.2. Sirion may direct its automated systems to review and process Customer Data to generally inform machine learning capabilities in the Subscription Services. The same clause covers generating aggregated and anonymized industry analytics, with a commitment not to publicly identify the customer or disclose Customer Data to third parties.

The agreement governs over a policy page, so the reservation is what binds the customer. It operates on Customer Data itself rather than on deidentified or aggregated derivatives, which gives it a broader reach than clauses limited to aggregate data. It says generally inform rather than train, so the words leave open whether it authorizes model training in the ordinary sense. The SaaS Terms, the end user agreement and the data processing addendum offer no opt out, consent step, configuration setting or exclusion route.

Prompt and Output Retention

How long does the product keep what a lawyer typed, and can that be set to zero?

Ironclad
Disclosed without a period

During the term, the Data Processing Addendum keeps customer personal data only as long as the services need it, and the AI Addendum sets no separate period for prompts and output. All copies are destroyed within 90 days after the agreement ends, with a 28 day window to export the repository. External model providers run under zero data retention.

Sirion
Customer controlled, no zero option

The published data processing addendum says the retention period is set by contractual obligations as the controller directs. After termination, personal data is typically kept for 30 days. The window is therefore under customer instruction, with a stated default, in a contract rather than a policy page. The provision covers personal data rather than prompts and generated outputs specifically, and no zero retention setting is offered.

Ethical Walls and Matter Segregation

Does retrieval respect the firm’s ethical walls, or can the model read across them?

Ironclad
Own model, documented

Role based permissions set by administrators are Ironclad's own, rather than inherited from a document system. Agents and MCP answers respect the same permissions, so a user sees only the contracts already open to them. Nothing describes walls between matters, since the product is built for in house teams rather than firms.

Sirion
Own model, documented

Separation between customers is set out in the data processing addendum rather than in marketing. All customer data is stated to be stored and processed in a Sirion application instance specific to the customer, within the cloud service. A shared responsibility model applies, in which Sirion secures the software, the customer data and the related access, and the cloud provider secures the underlying facility. Vendor library articles describe role based access control with granular permissions.

Sirion's published material does not describe how access is enforced between teams inside a customer, where legal, procurement, sales and finance share the platform. A Sirion library article also describes the platform's multitenant scalability, and nothing published reconciles that with the addendum's customer specific instance. The buyer is an in house department, so separation between customer tenants is what applies here.

Third Party Request and Subpoena Notice

If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?

Ironclad
Notice committed

The Data Processing Addendum commits Ironclad to tell the customer promptly of any government or law enforcement request for its personal data, unless the law forbids it, and to help the customer contest it. The Enterprise Services Agreement allows disclosure of confidential information under a court or government order after reasonable notice where the law permits. No transparency report is available.

Sirion
Notice committed

Section 5.3 of the SaaS Terms, version 6, modified 26 August 2026, holds the notice commitment. A party receiving a demand from an authority or court for the other party's Confidential Information may comply only after satisfying itself the demand is lawful. It must give as much prior notice as possible, where possible, so the other party can object, and mark the material as the other party's Confidential Information.

The duty is mutual and covers customer material. Confidential Information includes information that should reasonably be understood as confidential, and the AI Module clause at 1.8(b) confirms this by bringing Customer Data back into that definition. The notice duty is limited by the words where possible, not by a legal prohibition. The data processing addendum does not address third party demands. The terms pages, the addendum and the trust center give no transparency report or count of demands.

Primary Law Corpus Provenance

Where does the law in this product come from, and does the vendor have the right to use it?

Ironclad
Sources named, basis unstated

Ironclad's AI works over the customer's own contracts, playbooks and workflow data rather than a body of law. Its own models learn from aggregated, anonymized patterns across customers who opt in, and Ironclad cites more than 2 billion contracts processed. No source, scale, license or refresh cycle is given for that training data.

Sirion
Sources named, basis unstated

The working corpus is the customer's own contract set. Answers are described as carrying citations linked to the customer's own data, and agents extract and normalize contracts from sources the customer nominates. Sirion separately states that its purpose built models are trained on millions of enterprise contracts. The statement describes a second corpus by its makeup, but Sirion names no source, states no license or rights basis, and does not say whose contracts those are.

The product does not retrieve primary law, so the usual questions of jurisdiction and coverage do not arise. No update cadence is published.

Good Law Verification

Does the product tell you when the authority it just cited has been overruled?

Ironclad
Not addressed

Contracts sit at the center, while Contract Review Agent can also answer legal questions with embedded citations. No citator, treatment signal or check of later history is described.

Sirion
Not addressed

The platform manages contracts, obligations and supplier performance rather than retrieving case law or legislation, so a citator is not part of what it sells. The home page, the trust center index with its AI ethics, compliance and security sections, and the terms and policies index do not address whether legal authority is reviewed for subsequent history. They describe no citator, treatment signal or currency check.

Refusal and Uncertainty Behavior

What does the product do when the answer is not in the corpus?

Ironclad
Not addressed

Contract Review Agent flags missing clauses and departures from a company's standards, and extraction highlights the passage each value came from. When the model cannot place a value, the grounding system retries on the raw and normalized text rather than returning nothing. No path for declining to answer, and no confidence signal for the user, is described.

Sirion
Not addressed

AskSirion gives source references and explains how it interpreted a request when answering from contracts and related records. Custom agents can also escalate according to conditions the customer specifies. Neither feature establishes a response for a question unsupported by the corpus, or an uncertainty indicator presented to the reviewer. Contract issue severity and an administrator's escalation policy concern different decisions from whether an answer has adequate grounding.

Fabricated Citation Record

Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?

Ironclad
None located

No entry for Ironclad appears in the AI Hallucination Cases database, Damien Charlotin's record of court decisions involving hallucinated AI content. Ironclad is a contracting platform, and its output is seldom filed with a court as cited authority.

Sirion
None located

Sirion and its former name SirionLabs have no matching entry in Damien Charlotin's AI Hallucination Cases database. The database records judicial decisions addressing fabricated AI content and identifies an implicated tool when the case supplies one. Sirion's enterprise contracting and supplier governance functions differ from a litigation drafting service. The absence of a named database entry says nothing about whether every extracted term, contract answer, or proposed revision is accurate.

Bar Guidance Alignment

Has the vendor engaged in public with the ethics opinions its buyers are bound by?

Ironclad
Not addressed

Ironclad's AI Addendum and AI Disclaimer say output is not legal advice and should be verified with a licensed professional. No ethics opinion or bar guidance is named, ABA Formal Opinion 512 included.

Sirion
Not addressed

Sirion's compliance material is oriented to regulation and security frameworks, covering ISO 27001, SOC 1, SOC 2 and the EU AI Act. None of it addresses the professional conduct obligations binding the lawyers who use the product. The home page, the trust center index with its AI ethics, compliance and security sections, and the terms and policies index do not engage with any bar or ethics guidance. That includes ABA Formal Opinion 512 and any state bar or Law Society material.

Billing and Fee Posture

Does the vendor address what happens to the bill when the work takes an hour instead of six?

Ironclad
Outside the fee relationship

Named corporate customers describe shorter contract reviews and less legal operations work. NEXT Insurance reports recovering half of its legal operations time, while AES and Signifyd describe first redlines and NDA reviews in minutes. The platform serves internal legal, procurement, sales and operations teams handling their organization's agreements. It does not provide a law firm billing workflow or a client fee disclosure process for the time saved.

Sirion
Savings claims only

Sirion's marketing pages are built around speed and automation gains. They cite 90 percent faster contract centralization, 85 percent faster insights, up to 90 percent faster time to contract and 70 percent faster agentic automation. A customer reports as much as a 50 percent rise in tasks automated. The home page, the trust center and the terms and policies index offer no record of AI assisted work by matter for fee purposes, and no guidance on billing, fee or disclosure treatment.

The buyer is an in house function rather than a firm billing a client, so fee disclosure here comes down to internal cost and outside counsel spend, and the published material addresses neither.

Outside Counsel Guideline Readiness

Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?

Ironclad
Subprocessors listed

Ironclad's subprocessor list names Anthropic, OpenAI and Extend for AI and Google Cloud Platform for cloud and AI infrastructure, with locations for the United States platform and the EU datacenter. The Enterprise Services Agreement, Data Processing Addendum and AI Addendum are public in its legal center. A new subprocessor brings 30 days' email notice and a right to object. No notice pack for a client's outside counsel guidelines is available.

Sirion
Subprocessors listed

Appendix D publishes a Sub-Processor List, stated to be regularly updated, at a named URL that can be reached without a sales conversation. Clause 5.4 commits Sirion to notify the customer of updates and give an opportunity to object to additions or replacements. Clause 5.6 requires equivalent data protection terms on every subprocessor and keeps Sirion liable for their breaches. Sirion publishes no disclosure pack for a firm answering a client's AI clause, and no consent or notification material for clients.

Its published material names no model provider. The trust center's AI ethics page routes AI governance detail to a Sirion Account Executive.

Court Disclosure Support

If a judge’s standing order requires an AI disclosure, can the product produce one?

Ironclad
Partial record

Routing, assignment and approvals for each contract are recorded in Ironclad's workflows, and AI review is described as auditable, with humans able to review and override it. Extracted values highlight their source passage and redlines can show their rationale. No export records which model produced an output or who verified it. Ironclad's output is contract work rather than court filings.

Sirion
Partial record

Answers are said to carry citations linked to the customer's own data. Vendor material says every AI response includes citations to exact sources, with citation and justification at clause level. Audit trails are said to record system activity, user actions and data changes. Together these cover the sources retrieved and part of what was done, as a side effect of the product's design. Sirion identifies no model, so its material does not show which system produced a passage, and it describes no export built for court disclosure or AI use certification. The product serves enterprise contracting rather than litigation, so court standing orders are not its usual setting.

What neither one publishes

The questions both sides leave open

Derived from the records above rather than written, so it cannot favor either vendor. Take these into both conversations and ask each side the same question.

Signals neither addresses in public material
  • Good Law Verification
  • Refusal and Uncertainty Behavior
  • Bar Guidance Alignment

Which one fits

Choose Ironclad if

  • You want AI that works inside existing permissions. Ironclad's agents and MCP answers see only the contracts a user can already open, under roles administrators set. Ironclad Agent hands each request to a specialized agent, and the reviewer decides what to keep.
  • Your procurement gate is a list of standards with scope attached. Ironclad names SOC 1 and SOC 2 Type II from routine third party audits and states the trust categories certified against: security, availability, confidentiality and privacy. Alongside them sit ISO 27001, 27701, 27017 and 27018, a GDPR program and Cloud Security Alliance Trusted Cloud Provider status.
  • You want the training question answered in both directions. Ironclad states strict do not train and zero data retention terms with its external model providers. Separately, customers may opt in to Ironclad training its own models on their contracting data. That data is anonymized and aggregated first, and output generated for other customers never includes the contributing customer's data.

Choose Sirion if

  • You want the indemnity to reach the AI features. Sirion's AI Services terms extend its intellectual property indemnity to the AI features, except where a claim comes from the customer failing to review or validate output. Ironclad's AI Addendum carries no indemnity.
  • Your privacy review works through a checklist. Sirion's data processing addendum sets retention by the controller's direction, with deletion of all customer personal data within 30 days of termination. It publishes a subprocessor list at its own URL, with notification and an objection right on any addition. It commits to notifying a confirmed security incident within 72 hours, and specifies AES-256 at rest and TLS 1.2 in transit.
  • Your contracts have to move through SAP or Oracle. Sirion documents nine named connectors with the direction of travel stated for each. Four SAP Ariba accelerators cover the flow where an executed contract request creates a purchase requisition and the resulting purchase order is written back, and supplier master data comes from Ariba. The others include SAP S/4HANA on scheduled transfers, Oracle ERP with logging and sync status, and a bidirectional Microsoft Dynamics connector.

In summary

Ironclad

Ironclad is an enterprise contract lifecycle management platform that runs agreements from intake and creation through no code workflows, approvals, negotiation, signature, the repository and analytics. Ironclad Agent routes requests to specialized agents, and Contract Review Agent redlines against playbooks and precedent. Administrators set role based permissions, and the agents work only within them. Reviewers keep the final call and can override what an agent proposes. Its Enterprise Services Agreement, Data Processing Addendum and AI Addendum are published, and its subprocessor list names Anthropic, OpenAI and Extend. No price is published.

Source: AI Legal Index, 2026

Sirion

Sirion is an enterprise contract lifecycle platform organized around Store for extraction, repository and conversational search, Create for drafting and negotiation, and Manage for obligations and performance. An agentOS layer builds and deploys custom agents, and the platform is sold to legal, legal operations, procurement, sales and finance. According to the AI Legal Index, Sirion's case rests on integration depth and data stewardship. It documents nine named connectors with the direction of travel for each. Its data processing addendum sets deletion within 30 days of termination, publishes a subprocessor list with an objection right and commits to notifying a confirmed security incident within 72 hours. No accuracy figure, named model provider or price is published.

Source: AI Legal Index, 2026

Questions buyers ask

Ironclad vs Sirion: which is better for enterprise contract lifecycle management?

Very little separates them. Both publish their customer terms. Ironclad publishes more about how the AI is controlled and certified, and makes training opt in by contract. Sirion publishes more integration documentation and deletes data sooner after termination. Neither publishes a price or an accuracy measurement. From the AI Legal Index, based on each vendor's own published materials as of October 8, 2026. No vendor pays for placement.

Does Sirion use customer contract data to train its AI?

Two documents speak to it. Sirion's library pages say customer data stays in the customer environment and does not train external language models. Clause 4.2 of its SaaS terms reserves a right for Sirion to direct automated systems to review and process customer data to generally inform machine learning capabilities in the subscription services. None of the terms, the end user agreement or the data processing addendum offers an opt out. Where the two differ, the agreement is what binds. From the AI Legal Index, based on each vendor's own published materials as of October 8, 2026. No vendor pays for placement.

Which one publishes its contract terms?

Both do. Sirion's SaaS terms, end user agreement and data processing addendum carry an intellectual property indemnity and a cap of a year of fees. They add mutual confidentiality with notice of authority demands, 30 day deletion and a published subprocessor list. Ironclad's Enterprise Services Agreement, Data Processing Addendum and AI Addendum sit in a public Legal Center. They set a cap of a year of fees, a threefold cap for data breaches, intellectual property and data indemnities and deletion within 90 days. From the AI Legal Index, based on each vendor's own published materials as of October 8, 2026. No vendor pays for placement.

What do Ironclad and Sirion publish about integrations?

Sirion documents its integrations in depth: nine named connectors with the direction of travel for each, covering SAP Ariba, SAP S/4HANA, Oracle ERP and a bidirectional Microsoft Dynamics connector, with triggers and sync modes described. Ironclad names Salesforce and Coupa and treats integration as a differentiator, but publishes no page describing what any individual integration moves, in which direction, or what an administrator configures. Neither names a legal document management connector. From the AI Legal Index, based on each vendor's own published materials as of October 8, 2026. No vendor pays for placement.

What do Ironclad and Sirion both leave unpublished?

Neither publishes a price. Ironclad's pricing page lays out its products and add ons, and its fair use policy sells agent use as AI Credits, while Sirion publishes neither a structure nor a unit. Neither names the model behind its AI. Ironclad names Anthropic, OpenAI and Extend as providers, while Sirion names none. Neither publishes an accuracy figure, hallucination rate or test set for contract review. From the AI Legal Index, based on each vendor's own published materials as of October 8, 2026. No vendor pays for placement.

Disclosure

Neither vendor paid for inclusion, placement or a grade, and neither reviewed this page before it published. Everything on it comes from public material on the dates shown. How the index grades.

One finding here needs both documents named. Sirion's library material states that customer data stays within the customer environment and is not used to train external language models. Clause 4.2 of its SaaS terms, version 6 modified 26 August 2026, reserves a right for Sirion to direct its automated systems to review and process customer data to generally inform machine learning capabilities in the subscription services. The terms offer no opt out, and the agreement is the document that governs. The clause says generally inform rather than train, and it operates on customer data rather than de identified derivatives. Ironclad's AI Addendum, by contrast, makes training opt in and bars its AI subprocessors from training on customer data. Neither vendor reviewed this page.

Contact

Correct a record, or ask how something was graded

Every grade and every signal on this index is drawn from public sources and dated. If a record is wrong, out of date, or missing an artifact the index did not locate, send the source and it will be reviewed and the record redated. Vendors are welcome to submit documentation. Nothing on this index is for sale, including a listing, a placement, or a grade.

AI Legal Index

The AI Legal Index is an independent index that tracks changes to AI vendors in legal. It holds 462 vendors across 9 categories, each graded on the same 15 capability axes and recorded against 12 legal signals, from public sources. No vendor pays for inclusion, placement, or rating.

Index Status
Last index update
October 16, 2026
The AI Legal Index is an editorial reference. It is not a regulatory body, not a law firm, and nothing published here is legal advice or a recommendation to retain or avoid a vendor. Records are verified against published sources, bar guidance and public court records. Where a record reads not addressed, the material was not located in public sources on the date shown. See the Methodology page for evaluation standards and limitations.
© 2026 AI Legal Index
3801 N Capital of Texas Hwy, Ste E240 · Austin, TX 78746