Malbek is a contract lifecycle management platform for corporate legal departments and the sales, procurement and finance teams that work on contracts with them. The core platform covers contract creation, workflow, approvals, a repository and milestone tracking. Three modules sit on top: Malbek AI, which draws insights and recommendations from contract data; BusinessIQ, which turns a contract portfolio into reporting on revenue, risk and commercial exposure; and Klix, a clickwrap tool for online agreements.
More than 50 integrations are configured through Malbek Marketplace without code, including a native Salesforce connector that syncs data in both directions, along with NetSuite, SAP, Coupa, Slack, DocuSign and Adobe Sign. A REST API covers other systems. The company states that customer inputs, outputs and embeddings are never accessible to its model vendors and never used to train models. Foundation models are reached through AWS Bedrock and Azure and work alongside Malbek's own models, which check one another's output.
Malbek is SOC 2 Type II and SOC 1 Type II certified and runs on AWS. No price is published, and quotes are built from user count, user type, modules and integrations.
Side by side on the same 15 capability axes and 12 legal signals: where the two part company, and what neither one publishes.
Vendors in the same categories as Malbek 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.
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.
All 15 axes, graded from public sources on the date shown. Hover a grade to see what the letter means on that axis.
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.
The models drive a core capability layered on a product that works without them. Malbek's own framing is a CLM charged with AI. The platform underneath covers contract creation, workflow, approvals, the repository, milestones and clickwrap. The AI arrives as separately named and separately sold modules: Malbek AI for insights and recommendations, and BusinessIQ for commercial intelligence across the whole contract portfolio.
The pricing page confirms the separation by making modules one of the four variables a quote is built from. Remove the models and a working contract lifecycle management system remains.
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 described as an architecture rather than a slogan. The security FAQ describes an Ensemble LLM architecture in which specialized AI agents check one another in a chain. It combines Malbek's own AI and machine learning models with foundation models reached through AWS Bedrock and Azure, and the vendor states this produces results that are well grounded and cited. What is missing is measurement. No accuracy figure is published, no test set is described, no evaluation is linked, and no failure mode is named anywhere, including hallucination.
Grounding to primary law does not apply to a contract lifecycle product, where the source material is the customer's own repository.
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.
Autonomy is claimed and oversight is not described. The platform is marketed on removing manual effort across contracting, streamlining negotiations, shortening review cycles and surfacing timely recommendations. A published customer testimonial states that approximately 80 percent of that customer's templates no longer require legal review. Nothing published says what the system does on its own and what a human approves.
No review screen is named, no threshold is stated at which a matter returns to a lawyer, and nothing says what happens after an output is wrong.
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.
There is real deployment evidence with substance, but no measurement a reader can assess. Named customer logos include EDF, SurveyMonkey, Aptean, Articulate, Lighthouse, TIBCO, Cetera, J.D. Power and Darden. Testimonials carry full names and roles. Ellen Kranz, Senior Contracts Specialist, states that approximately 80 percent of templates no longer require legal review and that contracts go active within minutes or hours.
Adrienne Schaal, Director of Legal Operations, describes a Salesforce integration configured in minutes and field mapping without IT. Jeff Peduto, SVP Operations, describes 90 days notice before renewal dates. Malbek was named a Leader in the 2025 Gartner Magic Quadrant for Contract Life Cycle Management. The figures sit inside quotations with no method, date or baseline. A separate panel of headline numbers, including 120 percent retention and 90 percent recommending, gives no basis, sample or date for any figure.
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.
The published commitments on confidentiality and training use are substantive but incomplete. The security and compliance FAQ states that client inputs, outputs, embeddings and training data are never shared with other customers, never accessible to the large language model vendor, never used to improve or train future models, and never used to enhance third party products. The same commitments are said to apply to partners, subcontractors and subprocessors.
Data isolation is asserted, supported by role based access controls with permissions at field level, single sign on, multifactor authentication and AES-256 encryption. What the model provider may retain is answered. Retention and deletion are not published, and privilege and work product are not addressed. The commitments also sit on a marketing FAQ rather than in an agreement a buyer can read, because the terms of service did not render.
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.
The marketing describes the product in terms that replace legal review, and no position on the advice line is published on any page reached. A featured customer quotation states that approximately 80 percent of that customer's templates no longer require legal review. The same customer says sales teams start contracts and mark them active after signature within minutes. The department pages sell contract handling directly to sales, procurement and finance.
No disclaimer, statement of what the product is and is not, competence or supervision language, or jurisdiction limit was found on the home page, the platform and module pages, the security and compliance page or the plans page. The terms of service is the page most likely to carry a disclaimer, and it could not be read and may say more.
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.
What Malbek publishes under the AI heading is security rather than governance. The AI safeguards answer is detailed. It names defenses against instruction override attacks, data exfiltration through format manipulation, output format hijacking, CSV injection, attack chains with several stages and delimiter confusion. None of it addresses governance. Nobody inside Malbek is named as accountable for AI outcomes, no evaluation of model output before release is described, and no testing results are published.
There is no responsible AI statement, no ISO 42001 and nothing on bias or uneven output across contract types or counterparties. The release process answer describes QA certification and change control for the platform in general, which is software governance rather than model governance.
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.
The published policy covers most of the ground. Access control is set out in detail: a zero trust approach, AES-256 encryption, role based access controls with permissions at field level, single sign on and multifactor authentication, continuous monitoring and threat detection, background checks on personnel, regular security awareness training and a security team monitoring systems around the clock. Incident practice is stated, with a structured response plan that puts transparency first, and third party audits and penetration testing are said to run regularly.
A business continuity and disaster recovery plan is described in outline, with the full policy available under NDA. Retention and deletion are not stated on any page reached. The subprocessor list exists but sits inside the trust center hosted on Vanta, which did not render.
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 allocation of loss could be found on any page that loaded. This reflects pages that would not load, not a finding that Malbek is silent. Malbek publishes terms of service and a privacy policy at malbek.io/terms-of-service and malbek.io/privacy-policy. Both are served through its own Klix clickwrap module, and both return the page frame with no body. Both the www and bare domain forms were tried, and the bare form redirects to the same empty page.
The site navigation and footer were checked. The security and compliance page was read in full; it covers training, isolation, access control and certification but no indemnity, cap, warranty or insurance. The trust center and subprocessor register, hosted on Vanta, returned metadata without body. On 4 September 2026 a search on distinctive clause language returned only general commentary on limitation of liability and indemnification clauses, written by Malbek's General Counsel, and nothing from Malbek's own agreement.
That commentary is about contracts in general and is not evidence of Malbek's position. The terms could not be read and may say more.
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.
Malbek documents integrations into the systems contracting runs through and describes their depth. More than 50 integrations are published, organized by type across CRM, ERP, electronic signature, storage and SSO, with a browsable directory. The Salesforce connector is described in detail: a productized native connector with complete data sync in both directions, configurable in minutes. A customer quotation separately describes mapping new fields as business needs change without IT involvement.
Named targets include NetSuite, SAP, Coupa, Slack, OneTrust, Adobe Sign, DocuSign and Azure OpenAI. Malbek Marketplace configures connections through a drag and drop interface that needs no code, which answers what a customer must set up. A REST API is published for targets without a productized connector. The plans page states which integrations are included and which cost extra.
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.
Neither data residency nor tenancy is described. Data residency options are listed as a data protection feature, but no region is named, no options are listed, and nothing says where a given customer's data would sit. Tenancy is not addressed at all. Nothing says whether customers share one platform instance or have their own, or how they are separated at the infrastructure level. The closest detail is the statement on the security page that data is isolated at enterprise grade, which is a claim rather than a tenancy model. Hosting on AWS is named, which identifies the infrastructure provider without answering either question.
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.
Malbek's security and compliance page, last modified 14 April 2026, states that Malbek is SOC 2 Type II and SOC 1 Type II certified in its own right. That is a claim about Malbek rather than its host. The other certifications on the same page, ISO 9001, ISO 27001, ISO 27017, ISO 27018, PCI DSS Level 1 and SOC 1, 2 and 3, are expressly AWS's for the cloud infrastructure and are not Malbek's own. The page also records regular third party security audits and penetration testing by independent auditors, background checks and annual security awareness training for staff, round the clock monitoring by a dedicated security team, and a structured incident response plan.
Compliance is claimed with GDPR, CCPA, CFR 21 Part 11 and GxP. No certifying body or auditor is named, no report date, observation period or scope is published, and no report is offered at any access level. The disaster recovery policy is available only under NDA. The trust center at trust.malbek.io is hosted on Vanta and returned metadata with no body. A buyer cannot check either certification against a register without contacting Malbek.
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.
The architecture is described rather than asserted. Malbek's security and compliance page, last modified 14 April 2026, describes an Ensemble LLM architecture of specialized AI agents that check one another in a chain. It combines Malbek's own AI and machine learning models with foundation models reached through AWS Bedrock and Azure. A buyer can see that both in house and third party models are used and how they are reached, and Azure OpenAI appears among the integration logos on the plans page.
The same page states that when external large language model APIs are used, Malbek follows each provider's terms and engages only vendors meeting its data protection standards. It also states that client data is never accessible to the model vendor and never used to train models. A subprocessors page is published at malbek.io/sub-processors and was not opened, and may say more. Four gaps remain: no individual model is named, the providers behind Bedrock and Azure are not identified, no location is given for inference as distinct from hosting, and no commitment to notify customers of a model or provider change was found.
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.
The pricing unit and structure are stated without a figure. The plans page lists the four variables a quote is built from: user types, number of users, modules, and Malbek connections. The pricing FAQ adds that customers pay only for what they need, against a custom quote estimated on those inputs. Some integrations are free and others cost extra, and implementation is scoped per customer from a few data points. Support, training and the help center carry no additional cost, with monthly training included.
No number, band, plan name or feature split between packages is published, so the shape of the model is visible and its scale is not.
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.
Coverage by segment is described with substance and the boundary is left open. Four buying departments each have their own solution page, Sales, Legal, Procurement and Finance, with a stated purpose for each. Four industries also have their own pages, Life Sciences, Manufacturing, Consumer Packaged Goods and Retail, with handling of regulated agreements called out for life sciences and high volume supplier and promotional contracting for CPG.
Compliance coverage names GDPR, CCPA, CFR 21 Part 11 and GxP. The buyer is a corporate enterprise rather than a law firm, and law firms are neither claimed nor excluded. No contract types are listed as supported, no organization size is stated, government use is not addressed, and nothing says where the product stops.
The public pages on file for Malbek, 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, Ethical Walls and Matter Segregation, Prompt and Output Retention
Read Sep 4, 2026
Fabricated Citation Record
Read Sep 4, 2026
No figure, band or plan name is published. The plans page publishes the structure instead, naming the four variables a quote is built from: user types, number of users, modules, and Malbek connections. The pricing FAQ states customers pay only for what they need against a custom quote estimated on those inputs. Integration cost is set out as a split, with some integrations free and others costing extra across ERP, CRM, eSignature, storage and SSO providers.
Implementation is stated to be tailored to the business and calculated from a few data points. It is delivered in phases, and the customer can maintain and expand the environment independently over time. Support is stated to carry no additional cost, covering phone, email and an online help center, with monthly training included.
Malbek made its MCP Server generally available at its Envision 2026 event, as part of what it calls Composable CLM. Any AI assistant that supports the Model Context Protocol can discover, draft and negotiate contracts in Malbek while the contract lifecycle rules stay in force, and every action an agent takes through it is recorded on the contract's timeline and audited.
A 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.
Can material a lawyer puts into this product be used to train a model?
A public policy or trust page states no training on customer content, with no matching term located in the published agreement.
The security and compliance FAQ answers the question directly and in the negative. It states that data isolation at enterprise grade guarantees customer data is never used for model training. It separately states that client inputs, outputs, embeddings and training data are never accessible to the large language model vendor, never used to improve or train future models, and never used to enhance third party products.
The same commitments are said to be required of partners, subcontractors and subprocessors. The commitment sits on a public security page rather than in an agreement. Terms of service are published at malbek.io/terms-of-service, but the body is delivered through Malbek's own Klix clickwrap module and returned no content on 4 September 2026 in either URL form. A matching contractual term could not be found or ruled out.
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.
Malbek describes what happens to inputs and outputs in detail but never states how long they are kept. The security and compliance page, last modified 14 April 2026, records that client inputs, outputs, embeddings and training data are never accessible to the LLM vendor, never used to improve LLM models or train future AI models, and never used to enhance third party products. It also describes data isolation at enterprise grade.
That covers access and permitted use rather than duration. No retention period, deletion commitment or position at the end of a subscription appears on any page reached. The terms of service and privacy policy are served through Malbek's own Klix clickwrap module and returned page frames with no clause text on two attempts on 4 September 2026, the second using URLs supplied by the operator. A search on distinctive clause language found nothing in search results, and both documents may say more. The trust center at trust.malbek.io is hosted on Vanta and returned metadata only.
Does retrieval respect the firm’s ethical walls, or can the model read across them?
Segregation is asserted in public materials with no published detail on how it is enforced.
Segregation is asserted in public material without detail on how it is enforced. The security and compliance page states that data is isolated at enterprise grade and that client inputs, outputs and embeddings are never shared with other customers. It lists role based access controls with permissions at field level among its data protection features. Nothing published describes the isolation mechanism, the tenancy model or how permissions are administered. No material addresses separation between matters or contract sets within a single customer.
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.
Customer data facing a subpoena, court order or government request has no stated handling. Nothing commits to notifying the customer or reserves discretion over notice. The security and compliance page was read in full on 4 September 2026. It covers encryption, access control, operational security, third party audits, disaster recovery and AI safeguards and never reaches compelled disclosure. The subprocessors page and privacy policy are the pages that would usually carry it.
The privacy policy and terms of service are served through Malbek's own Klix clickwrap module and returned page frames with no clause text on two attempts, the second using URLs supplied by the operator. A search on distinctive clause language found nothing in search results. The subprocessors page was not opened, and these documents may say more. The trust center is hosted on Vanta and returned metadata only.
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.
Outside legal content plays no part in the answers, and the product's design makes the question narrow. Malbek analyzes the customer's own contract repository rather than retrieving outside legal content, and BusinessIQ is described as distilling that repository into generative intelligence. No external database, publisher or content license is named on any page, and no jurisdiction coverage is claimed. Searched the home page, the platform and module pages, the security and compliance page and the plans page on 4 September 2026.
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.
Nothing on any page found addresses whether authority is checked for subsequent history. The product does not retrieve primary law. It works on the customer's own contract repository, surfacing risk at the level of individual clauses, along with obligations and commercial exposure, rather than case law or statute. The question therefore does not apply to this kind of product. Searched the home page, the platform and module pages, the security and compliance page and the plans page on 4 September 2026.
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.
Agents check one another's work, but the user sees no refusal or confidence signal. The Ensemble LLM architecture is described as a chain of specialized agents that check one another to produce results that are well grounded and cited. That is a quality control rather than a way to decline, and no confidence score, grounding score or refusal to answer is described as visible to the user. Hallucination is not named on any page reached, including in the AI safeguards answer, which addresses adversarial attack rather than model error.
Searched the home page, the platform and module pages, the security and compliance page and the plans page on 4 September 2026.
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.
The AI Hallucination Cases database maintained by Damien Charlotin was searched on 4 September 2026 on the product and company name Malbek. No court order, opinion or disciplinary record naming the product was located. This records the state of the public record on that date and is not a finding about the product.
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.
Ethics, in this vendor's telling, means corporate conduct rather than professional duty. The ethics answer on the security and compliance page describes corporate conduct policies against slavery, bribery and discrimination, and on sustainability. These are business ethics rather than professional responsibility. No bar association, regulator, ethics opinion or professional code is named on any page. The buyer is a corporate department rather than a regulated practitioner.
Searched the home page, the platform and module pages, the security and compliance page and the plans page on 4 September 2026.
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.
Public materials claim savings without addressing billing or disclosure. One featured customer states that approximately 80 percent of templates no longer require legal review, and another that the money spent on the system came back tenfold. A panel of headline numbers claims 91 percent say Malbek enables and enhances productivity. Nothing addresses what happens to a bill when work assisted by AI takes less time, and no record of AI work kept per matter is described. The buyer here is an in house department rather than a firm billing a client.
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
A current subprocessor or model provider list is published.
A model provider statement is published openly on the security and compliance page. It names AWS Bedrock and Azure as the routes to foundation models alongside Malbek's own models, and states that inputs, outputs and embeddings are never accessible to the LLM vendor. That answers which providers stand behind the AI without a sales conversation. No forwardable pack is openly published. The formal subprocessor register sits inside the trust center at trust.malbek.io, hosted on Vanta, which returned page metadata with no body on 4 September 2026. No data processing agreement was found at any access level, and the disaster recovery policy is available under NDA.
If a judge’s standing order requires an AI disclosure, can the product produce one?
No located public material addresses court disclosure or verification certification.
No located public material addresses court disclosure or verification certification. No audit trail or activity export is described on any reachable surface, the model used for a given output is not disclosed to the customer, and no record of human verification is mentioned. The platform is a contract lifecycle system for corporate contracting rather than a litigation product, so the question bites weakly, but nothing published answers it.
Searched the home page, the platform and module pages, the security and compliance page and the plans page on 4 September 2026.
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.