CKA generalizes our AI Chat Prompt into an embeddable website assistant. The widget answers questions based on your website context, your configuration, and clear safety boundaries. CKA is currently in pilot phase; there is no general self-service purchase yet.
Origin From the Cephei AI Chat Prompt to a website widget Our chat prompt demo shows the technical foundation: local AI backend, streaming, website context, and clear limits. CKA turns that into a reusable widget for other websites. View AI Chat PromptCKA is functional and already running in real integrations. At the same time, the pilot phase still evaluates onboarding, context maintenance, operations, privacy wording, and suitable industry scenarios. If you want to participate, contact us; we will assess together whether the website and use case fit.
Many websites already contain the relevant information, but visitors do not always find it quickly or ask questions that menus and search boxes handle poorly.
Services, process information, blog posts, or FAQs live across multiple pages. CKA can turn them into a structured answer base for visitor questions.
People ask in everyday language. A website assistant can receive these questions and answer them from curated content.
Medical practices, advisory services, and company sites need clear notices, limits, prompt-injection protection, and controlled answer logic.
The decisive pieces are tenant configuration, context maintenance, allowed origins, privacy link, limits, monitoring, and a realistic operating model.
The widget is only the visible surface. The product logic lives in the multi-tenant backend and in the controlled configuration for each website.
Curated website contexts, article indexes, or practice information form the answer base for each tenant.
The model integration runs server-side through Cephei infrastructure. API keys and model access stay out of the browser.
CSRF, origin allowlisting, rate limits, prompt limits, prompt-injection detection, and an optional AI safeguard reduce typical risks.
Depending on the tenant, web search can be enabled. Answers can include source references when the configuration provides for it.
Small tenant-specific WordPress plugins are currently in use. A generic plugin and self-service onboarding are later product phases.
CKA runs, for example, on our own blog and on an ENT practice website. These examples show different contexts: editorial content on cephei.blog and curated practice information on hno-augsburg.com.
A CKA pilot is not just a script installation. We first review the goal, content, boundaries, and operations.
Which questions should be answered, which content is suitable, and which topics must deliberately be excluded?
We create the initial answer base and define theme, limits, allowed domains, privacy link, and behaviour.
The website loads the central widget. We then test common questions, failure states, and rendering on desktop and mobile.
We assess value, answer quality, maintenance effort, and operating risks before turning this into a lasting offer.
CKA does not replace professional advice or legal, medical, or security-critical decisions. The assistant provides orientation based on the supplied context and points to appropriate contact paths when needed.
If you want to test a website assistant for your blog, practice, company website, or another suitable scenario, write to us. We will get back to you for an initial assessment.
Before a pilot, it is important to understand what CKA can do, where the boundaries are, and how integration works.
No. CKA is currently in pilot and evaluation phase. The pilot programme is open, but every participation is assessed and set up individually.
Suitable websites have clear, curatable content: blogs, practices, company sites, product or service information. The important part is that intended answers can be grounded in reliable sources.
At the core, the website loads a central JavaScript widget with a tenant ID. Security-relevant configuration, context, and model integration live server-side in CKA.
The current CKA widget is designed to be cookieless. Session and CSRF data are held in widget storage. Independently of that, the website must describe AI processing properly in its privacy policy.
CKA is designed for privacy-conscious operation. Processing runs on Cephei-owned hardware in our own rooms at a German location, not on third-party cloud infrastructure. For each pilot, we also clarify the appropriate privacy notice wording and organizational agreements.
No. Inputs and answers are not used for AI training and are not disclosed to third parties for their use. Conversation content is not stored permanently; technical processing is limited to answering the request and limiting misuse.