Centerbase vs Clio: how they compare in 2026

Centerbase has sold practice management, billing and accounting software to midsize firms for more than a decade, and Centerbase IQ arrived in April 2026 as an intelligence layer on top. The vendor's own account of its history describes building the system of record first and IQ as the layer that reads it. Take IQ away and matter management, timekeeping, billing, collections, trust and general accounting, document management, intake, the client portal, workflows and reporting all remain. By August 2026 the vendor called itself an AI powered performance platform and stated a plan to expand proactive insights and deepen agentic AI. That plan is in the future tense and does not describe a shipped capability.

Clio is an eighteen year old practice platform with an AI workspace built on top, and Clio frames it that way: its marketing says the 18 year foundation now powers its legal AI. Clio Manage, Grow, Draft and Accounting are conventional software, and the entry tier is sold on practice management, not models. Clio Work is built around AI and sold as a separate product with its own trial, and Grow AI and Manage AI sit inside the older modules. Remove the models and the system 400,000 professionals use to run their firms still works.

The vendor commits that every Centerbase IQ answer includes the source records behind it, so users see where an answer came from and an administrator can trace a figure back to the underlying data. The chief product officer frames it as showing both the answer and the source rather than asking firm leaders to trust a black box. The vendor describes the insights as isolated to the firm's own data, leaving no outside material for an answer to drift into. The cited sources are the firm's own billing entries and matter records, which the reader can open directly. No accuracy figure, error rate, evaluation or test is published, and nothing describes how a natural language question becomes a query over the firm's data. The product answers questions about a firm's finances rather than about law, so it cites no legal authority.

Two sources ground the AI, and no accuracy figure is published. Clio's pricing page says the AI is grounded in the firm's matters and cites its sources. Its home page says the AI works from matters, clients, filings, messages and financial data, combined with over a billion legal documents across 100+ countries, the vLex library Clio bought in June 2025. That is a described retrieval method over identifiable sources, and the subprocessor list backs it up by naming a vector database provider. No accuracy measure is published, and the Terms cut against any implied one. Clause 14.2 says Themis does not review Output for accuracy or completeness and that Output may be incomplete or inaccurate. Clause 17.2 says the same of the legal Materials, disclaiming accuracy, completeness and currency. Clio publishes an accuracy resource at /resources/ai-for-lawyers/ai-accuracy-legal/.

Centerbase IQ answers the questions put to it and returns visual, sourced answers. It does not act, file, draft or decide, and nothing published claims it does. Source records on every answer give a user something to check against. Nothing states whether an answer should be verified before it is relied on in a partner meeting, what the system does when a question cannot be answered from the data, or whether any confidence indicator, threshold or escalation route exists. The vendor has also published a plan to deepen agentic AI to power workflows, and nothing published addresses oversight of a layer that would act on billing, collections or matter data.

Human review is a marketing commitment that Clio's contract makes binding, but there is no finer structure. Clio's pricing page says the firm reviews and approves everything before it reaches a client or court. Terms clause 14.2 turns that into a duty on the subscriber. It must use AI Services and Output only with human oversight, and review Output for accuracy, completeness, fitness and compliance with legal, regulatory and professional requirements before using it. Clause 14.4 leaves the subscriber in full control of how AI Services are set up and presented. Missing: no modes or thresholds are described, and nothing says what the product does on its own versus what it waits to be asked.

No named customer firm, case study, named reference or attributed testimonial is published. The vendor publishes trade press coverage of the Centerbase IQ launch, its debut at the 2026 Association of Legal Administrators Annual Conference, a listing in the ALA supplier directory, and partnership announcements with NetDocuments, Billables AI and Scan Logic. Partners are not customers. Outcome claims are made in the abstract, such as greater delivery capacity without added headcount and stronger realization, with no firm, figure, period or method attached. A Centerbase IQ product page is published at centerbase.com/IQ.

One named firm comes with a figure and period, alongside platform numbers with no method. King Law is named on the home page with a 275% increase in revenue over four years, credited to visibility and tools across the firm. Named people appear with their firms: Angela Lennon at Koenig | Dunne and Danielle Harvey-Jacob at Harvey-Jacob Law. Platform figures are 400,000+ legal professionals, 130+ countries and 300+ integrations. Nothing is dated, and no method is given for the King Law figure. A rating of 4.7 from 12,000+ reviews comes from directories, and Clio's own comparison page is marketing.

On security, the vendor states SHA256 4096 bit RSA encryption in transit, 256 bit AES encryption on backups, enterprise class firewalls and a SOC 2 Type II claim. On the AI, it states that Centerbase IQ's insights are isolated to the firm's own data. Nothing states whether customer content is used to train models. No model provider is named, so nothing states what any third party may retain. Privilege and work product are not addressed, on a platform holding matter records, documents and the firm's billing narrative, where time entries routinely describe privileged work. No customer agreement is published; the legal path publishes a privacy and security policy for the website and payments.

Confidentiality commitments are real at Clio, but privilege is never addressed. Terms clause 4.2 binds Themis and its vendors and hosting partners to keep Content strictly confidential and not use or disclose it outside the agreement. Clause 21.3 says only Themis, for strict business reasons, may access and transfer Content, only to provide the Service, with reasonable efforts to notify the subscriber first. Clause 14.6 says using AI Services grants no right to use confidential information to train general large language models. The security page says AI data is encrypted and processed in the customer's region, AI tools process in real time without storing or reusing data, and outputs are generated only for the user who asks. Missing: any express treatment of privilege or work product, on a platform holding the whole matter file, and any documented separation between matters within a firm.

Nothing is published on professional responsibility. Centerbase IQ answers questions about the firm's own billing, collections, realization, productivity and deadlines. It does not produce legal work product, advise on a client matter or generate anything that goes to a client or a court, so output being mistaken for legal advice is not the usual risk here. The product is sold to law firms and the AI is addressed to managing partners and firm administrators. No statement connects the tool to the professional obligations of the people using it. Nothing addresses the judgment a managing partner exercises when acting on a machine generated read of realization or attorney productivity, nothing addresses supervision, and no disclaimer is published. No customer agreement is published.

Clio covers every part of the advice question, all in its contract. The top of the Terms says in bold that Themis is not a law firm and gives no legal advice, through the Service or otherwise. Clause 12.1 adds that the Services, Output or Materials create no attorney client relationship. The Service is only for legal professionals and those they supervise, with a named exception for academic access. Clause 14.2 addresses competence and supervision, requiring human oversight and making the subscriber review Output against professional body requirements and fiduciary rules. Jurisdiction limits are stated three ways. The Service is for North America with separate EMEA terms, Materials are limited to the account's country, and clause 2.16 warns that one code base serves all jurisdictions, so subscribers must set and check their own. Clause 14.4 covers clients: firms must tell their own users about the use of AI, the nature and limits of AI responses, and any human oversight.

The chief product officer's stated principle is that AI in legal software has to earn trust before it earns adoption, and that the company shows both the answer and the source rather than asking firm leaders to trust a black box. Two design commitments sit behind it, source records on every answer and analysis isolated to the firm's own data. No governance framework is named, nobody is identified as accountable for AI decisions, nothing describes what is evaluated before a feature ships, and no testing is published. Bias is not addressed. Centerbase IQ reports attorney productivity, realization and origination, numbers that feed compensation and staffing decisions, and nothing published asks whether those readings are even across practice groups, seniority or working patterns.

AI principles are public, but not the process behind them. An AI Principles page, attributed to Chief Technology Officer Jonathan Watson, sets out five commitments: AI as collaborator, transparency of AI actions, high quality data, relentless refinement and uncompromising security. Bias appears once, as a claim that diverse, top quality data minimizes it, not as anything measured. Nothing names a person or committee accountable for the AI, describes testing before a feature ships, or discloses any evaluation result. The one trace of testing is indirect: the subprocessor list names Braintrust Data as an AI analytics, evaluation and testing provider across five products. That shows a testing pipeline exists, not a published regime a buyer could examine.

Infrastructure is the company's own rather than a hyperscaler's, with the Centerbase Cloud described as built on enterprise class Dell server hardware and firewalls with 24/7 high availability VMware clusters. Encryption is stated in detail: SHA256 4096 bit RSA from the browser to the data center and 256 bit AES on all backups of customer data. A SOC 2 Type II position is also claimed. No retention period is stated for firm data, prompts or generated answers, no commitment to delete or export data on termination is published, no subprocessor list exists and no processor is named, and no breach notification commitment is published.

Incident practice is contractual: clause 5.5 requires Themis to report any event it reasonably believes is unauthorized access to, disclosure of, use of or damage to Content within 72 hours, and clause 5.6 sets cooperation, investigation and mitigation duties. Deletion has a period: 90 days to retrieve Content after termination, after which all Content is permanently deleted. Escrowed data is held six months under a separate escrow agreement the customer controls. Subprocessors are published in full and dated. Clause 21.3 limits Themis access to strict business reasons, with advance notice. Encryption, geographic redundancy and at least annual third party penetration testing are stated. No retention period is published for AI inputs and outputs during the term, and clause 14.6 lets deidentified, aggregated Content and Output be kept for quality improvement without limit.

Nothing is published on who bears the loss when the system is wrong. No warranty, indemnity, liability cap, exclusion, service credit or insurance position appears, and no customer or master subscription agreement is published. The legal path publishes a privacy and security policy for website and payments use rather than a contract for the platform. Nothing addresses what happens if Centerbase IQ misreports a collection rate, misstates work in progress aging or misses a deadline it was asked about. The vendor positions these answers as giving managing partners confidence in the boardroom. It commits that every answer carries its source records, which lets a user catch an error, and makes no commitment about the consequences if the user does not.

Liability terms run both ways at Clio, but stop short of AI output. Clause 11.1 excludes liability generally but carves out breaches of confidentiality, security and managed backup, so those duties stay live. Clause 11.2 caps liability at the total paid in the six months before the claim, and does not apply that cap to the indemnity. Clause 13.2 gives the subscriber a real indemnity on two grounds: third party intellectual property claims against the Service, and claims arising from Themis breaching its own confidentiality or security duties. Exceptions are listed in 13.3. None of it reaches AI output. Clause 13.2(a) excludes Output from the intellectual property indemnity, clause 14.2 provides Output as is, and clause 12.2 disclaims any warranty on results. No insurance position is published.

Three integrations were announced within six months of each other. NetDocuments, March 2026, is described as the first native connection between a practice management platform's matter data and ndMAX document intelligence. AI is applied from the moment a matter opens, automating matter workflows and removing manual reentry. Billables AI, April 2026, provides automated time capture feeding practice intelligence. Scan Logic BillSync, August 2026, brings electronic billing and compliance into the platform. Alongside those sit Outlook, Microsoft Calendar and Microsoft Word synchronization and online banking reconciliation for trust accounts. No API or developer surface is published, nothing describes which objects synchronize or in which direction, and no configuration or authentication detail is published. A third party review notes no direct Google Workspace integration.

Integrations at Clio are documented in breadth, not depth. It lists 300+ integrations in an app directory, runs a developer hub and partner program, and treats API access as a governed feature in clause 3.9. API use is bound by the agreement, heavy use may lead to suspension after a reasonable attempt to warn, and access may be changed or ended. Clause 18 says third party services are not Services under the agreement, carry no warranties, indemnities or service commitments from Themis, and may be replaced, disabled or limited at any time without notice. That is honest about where the boundary sits. But nothing published says what any integration moves, in which direction, or what a firm must set up.

The company hosts its own infrastructure rather than using a hyperscaler, and the Centerbase Cloud is described as running on enterprise class Dell server hardware and firewalls, with 24/7 high availability VMware clusters and backups encrypted with 256 bit AES. No data center location, country or region is named, no residency option is offered or refused, and no tenancy model is described. Beyond the statement that IQ's analysis is isolated to the firm's own data, nothing says whether one firm's data is logically or physically separated from another's. Nothing distinguishes where firm data is stored from where Centerbase IQ processes it, and the AI layer's own hosting is unstated.

Residency is set out in detail, with no tenancy model. Hosting options cover the European Union, Australia, the United States and Canada, with five regional site versions, a separate EMEA instance at eu.app.clio.com with its own terms, and separate North American and EMEA agreements. Processing is distinguished from storage. The security page says all data used by the AI is encrypted and processed in the customer's own region, naming US, Canada, EMEA and APAC. The subprocessor list gives a data location for every provider, including each AI processor, and names infrastructure by provider and product. Missing: the tenancy model is not stated anywhere, and nothing says whether residency options vary by plan.

The current security page states that the Centerbase platform is fully SOC 2 Type II and that the controls protecting firm data are independently tested every year. An older security page, still published, states that the platform is SOC 2 Type 2 compliant for the Security trust services criterion only, with availability, processing integrity, confidentiality and privacy to be completed in 2025. Those are materially different claims about the same attestation, and neither page says which is current. No auditor is named, no report period or observation window is given, no certificate or report is published, and no trust center exists.

Clio states the coverage period of its SOC 2 report and gives customers a contract right to it. The trust center at trust.clio.com says the 2025 SOC 2 Type II report was issued for 1 June 2024 to 31 May 2025. The security page says Clio completes annual SOC 2 Type II and SOC 1 Type II examinations, with both reports in the trust center. Clause 5.4(d) obliges Themis to provide a SOC 2 or SOC 3 report, or a comparable description of security measures, within thirty days of a subscriber's request. At least annual third party penetration testing is stated, and Clio's help center names Deloitte as the independent auditor, though for the earlier Type I engagement. Three details are missing: the trust services criteria are not listed, the auditor for the current Type II is not named, and the penetration testing firm is described only as a leading cybersecurity firm. Clause 5.4(d) also requires signing an agreement with the report's third party provider.

Centerbase IQ is described as an AI powered natural language decision support capability and an AI intelligence layer. None of that names a model, a version or a provider, and nothing states where inference happens or commits to notifying a customer when any of it changes. No subprocessor list is published. What is disclosed is the data side: the analysis is isolated to the firm's own data, every answer carries its source records, and firms may add an internal knowledge base of their own standards. Those describe what the model reads, not what the model is. The native NetDocuments integration brings ndMAX document intelligence into Centerbase workflows, but that is the partner's product rather than a component of Centerbase IQ.

The AI providers behind each product, and where they run, are named, but not the models. The subprocessor list, last modified 20 August 2026, has an AI Service Providers table naming five AI processors, the products each serves and each one's data location: AWS Bedrock, Anthropic, OpenAI, Google Vertex AI and Microsoft Azure Foundry. They span Clio Manage, Grow, Draft, Work, Vincent AI and Clio Operate. The list also names Turbopuffer as the vector database, Braintrust Data for AI analytics, evaluation and testing, and Vapi for the Grow voice agent. So it is clear whose model handles a customer's content, per product, and where. Two gaps. The specific models are never named, only the providers. And the list page carries no commitment to notify customers of changes; the Themis Data Protection Addendum, under which the list is published, may hold one.

Pricing is based on the number of users, with no figure, plan or tier published. Every subscription includes onboarding, covering system setup and training, and implementation packages run from quick start to full service, scoped to the firm's size and needs. Professional service hours, Legalfit marketing services and advanced training and consulting are optional extras without published prices. Centerbase Payments, powered by Stripe, carries no platform fee and charges a standard fee on each payment processed.

The entry tier has a public price and the rest are quoted. Clio's pricing page shows a starting figure of $49 USD per user per month and names four tiers, Starter, Core, Signature and Elite, with features described tier by tier and a bundle saving of over 15%. Above the entry tier, buyers get a custom quote, and large firms a separate process. The Terms show the published figure is not the whole cost. Clause 9.5 lists setup fees, implementation charges and Metered Features fees as separate, nonrefundable items. Clause 9.6 gives buyers of setup or professional services sixty days to start them or lose them. None of those amounts is published. The tier names have changed again, and third party trackers still show the previous set.

The vendor's whole positioning is midsize law firms, repeated across every announcement and product page as purpose built rather than adapted. It explains why the segment is distinct: midsize firms are expected to operate with the strategic visibility of larger firms while running leaner administrative teams, and the AI is built around that gap. Roles are named: managing partners and firm administrators for Centerbase IQ, with attorneys, timekeepers, accounting teams and operations leaders as platform users. Functional coverage runs across matter management, timekeeping, billing, collections, trust and general accounting, document management, intake, CRM, workflows and reporting. No practice area is named as supported or unsupported, no firm size is given in numbers, no jurisdictional statement appears even though trust accounting rules vary by state, and nothing states what the product is not for.

Coverage is wide, with limits drawn by geography rather than function. Sixteen practice areas have their own pages, from bankruptcy and criminal law to intellectual property and real estate. Pages also cover four firm sizes, from solo to enterprise and large firms, and seven roles. In house counsel and government law each have a page. The Terms state real limits, about where rather than what. The Service is scoped to North America, with separate EMEA terms, and Materials are limited to the country tied to the account. Clause 2.16 warns that one code base serves all jurisdictions, so the subscriber must set and check its own settings. Nothing says which practice types the product handles poorly.