Download websites that use Chatbase

About Chatbase

Almost every technology described on this site has a longer history than the job it does. Chatbase does not. Chatbase, Inc. shipped it in 2023, which means the entire installed base was assembled after generative language models became cheap enough to sit behind a support widget on an ordinary business website.

A Live chat widget of this kind is a different signal from a traditional chat box. A team that installs it has already gathered its documentation, help articles or product pages into something a model can be trained on, has decided that a meaningful share of inbound questions are repetitive, and is willing to pay a Proprietary vendor instead of assembling a retrieval stack in house. The widget describes a decision about support economics far more than a decision about front-end design.

As of October 2026 the embed appears on 3,807 sites, and with a young product the interesting question is not who uses it but how fast the base is changing and where it is coming from. Answering that needs the full list rather than a lookup. With every domain in hand you can measure how often Chatbase sits on the same site as an older live chat vendor, which sectors move to conversational support first, and which segments carry it next to an ecommerce platform rather than next to a documentation site. Anyone selling to companies that are actively buying AI tooling is looking at a self-selected list of buyers who have already crossed that line once, which is a far better starting point than a list of companies that merely could.

A young vendor also carries a risk the data can describe. Support widgets churn, funding rounds end, and a category built in the last couple of years has not yet been through a consolidation. Holding the domain list at intervals is how you watch that happen rather than guess at it, whether you are a competitor tracking displacement or a buyer checking that the vendor you are about to sign with is still adding customers.

Detection has real edges. The widget is recognised from the embed that loads it, so deployments routed through a tag manager, a server-side proxy or a custom subdomain can pass unseen, and the same bot delivered through messaging channels instead of a website leaves nothing for a crawler to find at all. Sites that load the widget only after a consent click, or only inside a logged-in area, are missed as well. The published figure is a floor, and in this category it moves faster than in most others.