Skip to main content
ContentCloudContentCloud

Documentation

Implementation guidance for ContentCloud's secure and compliant enterprise AI solutions. The website embed below is publicly available today. Ingestion, administration and platform APIs are currently provisioned with our team during onboarding, pilots or solution design rather than through a public self-serve API.

Quick start: embed CCBot on your site

These are the steps we use for the widget on this website. You need an API key from your ContentCloud tenant to complete step 3.

1

Request access and an API key

API keys are issued during onboarding or a pilot. There is no public self-serve API yet — talk to us and we will provision your tenant and key.

2

Install the widget package

The React widget is published publicly on npm. It mounts inside a Shadow DOM and ships its own styles, so it will not collide with your CSS.

npm install @eworx-org/ccbot-react
3

Exchange your API key server-side

Keep the API key on the server. Your endpoint exchanges it for a short-lived Chat Session Token, so the key never reaches the browser.

// POST /api/ccbot/token  (server-side only)
const res = await fetch(
  'https://www.contentcloud.com/services/chat-token-service/exchange',
  { method: 'POST', headers: { 'X-Api-Key': process.env.CONTENT_CLOUD_API_KEY } },
);
const { token } = await res.json();
4

Mount the widget

Point the widget at your token endpoint. This is exactly how the widget on this website is configured.

import { CCbotWidget } from '@eworx-org/ccbot-react';

<CCbotWidget auth={{ tokenEndpoint: '/api/ccbot/token' }} />

Drupal sites: use the ContentCloud Drupal module instead of the React package — it handles widget placement and configuration inside Drupal 9, 10 and 11. Ask us for the module and setup notes.

Guidance we provide with your team

The topics below are covered during onboarding, pilots and solution design. Written material for each is shared directly with your team rather than published here.

Onboarding and content ingestion

Typically 1–2 sessions

Getting your project created and your first sources ingested, with our team.

  • Project and tenant setup
  • Source selection and ingestion planning
  • Scoping, allow/deny lists and response policies
  • Validating answers against your sources
Request access or guidance →

Drupal module

Typically half a day

Install the ContentCloud module on Drupal 9/10/11 and place the widget.

  • Module installation via Composer
  • API key configuration
  • Widget placement and theming
  • Content synchronisation
Request access or guidance →

React / JavaScript embed

Typically 1–2 hours

Embed the widget with the public npm package (used by this website).

  • Install @eworx-org/ccbot-react
  • Add a server-side token endpoint
  • Mount the widget component
  • Theming inside Shadow DOM
Request access or guidance →

Enterprise deployment

Scoped per deployment

Dedicated EU cloud or on-premises deployment, designed with our engineers.

  • SSO integration (SAML/OIDC, EU Login)
  • On-premises or private cloud installation
  • Scaling and private GPU options
  • Monitoring and operations
Request access or guidance →

Security and compliance review

Provided on request

Material for DPIAs, security reviews and procurement.

  • Data residency, encryption and retention
  • Access controls and audit logging
  • DPA and sub-processor information
  • EU AI Act and GDPR documentation
Request access or guidance →

Memory pilot setup

Pilot onboarding

Desktop, mobile and portal setup for Memory pilot participants.

  • Installing Memory Sidekick and Memory Mobile
  • Choosing capture sources per device
  • Workspace policies and retention
  • Self-hosting via Docker Compose
Request access or guidance →

Platform APIs

Ingestion, administration and query APIs exist behind the platform and are used for customer integrations, but they are not yet published as a public, self-serve API with open documentation and SDKs. Endpoints, authentication details and usage limits are shared under your tenant during onboarding or a pilot, so we can keep them aligned with your deployment model.

A public API with published reference documentation is on our roadmap. If your evaluation depends on it, tell us — it helps us prioritise.

Ask about API access

Need help?

Technical support

Help with integration, troubleshooting and deployment questions, by email during EU business hours.

Contact support →

Frequently asked questions

Answers on deployment, data handling, pricing, pilots, CCBot Mobile and Memory.

View FAQ →