What is Cossistant?
Understand Cossistant's default widget, reusable SDK, and deployment choices.
Own your support experience. Ship the default <Support /> widget or build a
custom interface from focused hooks and primitives.
Traditional support widgets often load an opaque iframe. That can make them hard to style, integrate with application state, or adapt for custom AI and human workflows.
Cossistant keeps the widget and SDK in your application code. You can start with a polished default and take ownership of only the layers you need.
Two implementation paths
- Default widget: Use
<Support />, configure identity/copy/theme, and swap selected slots without rebuilding conversation behavior. - Custom UI: Use focused hooks, shared types, and public primitives. You own layout, accessibility, navigation, loading/error states, and interaction design.
Hosted or self-hosted
The SDK can connect to Cossistant's managed service. The repository also contains the API, dashboard, workers, and optional infrastructure integrations needed for a self-hosted deployment. Self-hosting is an operations project, not just a package flag; start with the Self-Host overview.
Principles
- Open source: The AGPL-licensed repository is inspectable and open to community contributions.
- Composable: Public hooks and reusable primitives let you replace parts of the default experience without depending on an iframe.
- Code-first: Application identity, support context, and custom behavior stay close to the rest of your codebase.
- Strong defaults:
<Support />provides the ready-made path; custom UI is optional. - AI-readable: Typed packages, raw Markdown docs,
llms.txt, and an MCP server help both humans and coding agents use the current contract.
Start with the framework quickstart, then use the Support overview for incremental customization or Advanced for a fully custom shell.
Was this page helpful?
Open a prefilled documentation issue so the team can act on your feedback.