DiscoverCX
Get demo
</LLM>·Same content, no chrome — back to the designed page

Discover CDP

Unify scattered product content into a documentation hub your team can steer. Visual editing, ready-to-go templates, content from any source, AI-ready search, multilingual at enterprise scale, native Salesforce.

Canonical URL: https://discovercx.com/platform/cdp Last updated: 2026-06-04

Your documentation is a product. Treat it like one.

Discover CDP is the Product Knowledge Hub for technical content teams. Unify every source. Design without dev tickets. Ship the same content to your portal, to Salesforce, to your product UI, and to AI — from one platform built for documentation, not adapted to it.

Core capabilities

Product knowledge hub — Not a CMS with a doc theme

A purpose-built delivery platform for technical content — structured topics, versioned products, locale fan-out, audience-aware. Designed for documentation, not adapted to it.

Visual editing — Dream it. Build it. Ship it.

Drag-and-drop layout, inline editing on the live page, design tokens for brand fidelity. Your team ships changes. Engineering stops fielding portal tickets.

Templates → fully custom — Start fast. Scale to bespoke.

Production-ready templates for home, topic, search, hub, release notes. Theme in a week. Extend into a fully custom portal as you grow. No re-platforming.

Unify every source — One delivery layer

Discover CCMS, Confluence, SharePoint, Heretto, Paligo, MadCap, files, video, any REST API — converged into one searchable, governed product knowledge layer.

AI-ready search — Built-in or bring your own

Insight Search is federated, semantic-ranked, and analytics-instrumented. Or hand clean typed JSON to Coveo, Elastic, or Algolia — both first-class.

Headless + Salesforce-native — The portal isn't the only destination

Embed in Salesforce Experience Cloud. Surface in Service Cloud. Ground an AI assistant. Same content, served as typed JSON through the Delivery API.

Integrations

  • Salesforce Service Cloud — Native widgets. Bi-directional case sync.
  • Salesforce Experience Cloud — Embed DCX inside, or pull content as a package.
  • ServiceNow — Case widgets, knowledge sync, identity passthrough.
  • Atlassian & Zendesk — JSM, Confluence, Zendesk Guide — wired into your service stack.
  • Identity & SSO — SAML, OIDC, SCIM, MFA. Group-, plan-, product-based access.
  • Webhooks + API — Outbound on every event. REST + GraphQL inbound.

FAQ

How is this different from Fluid Topics?

Fluid Topics is a strong product knowledge platform focused on aggregation and AI delivery. Discover CDP overlaps on that surface but extends into the full experience: visual editing, ready-to-go templates, design tokens, customer experience features, and a delivery layer natively wired to Discover CCMS for authoring and SME review. If your priority is unifying sources for AI, Fluid Topics is solid. If you also need a shippable, brand-owned product knowledge hub your documentation team can steer, look at DCX.

How is this different from Zoomin?

Zoomin focuses on doc portal delivery with strong Salesforce integration. Discover CDP overlaps and extends into visual editing, native authoring on top of Discover CCMS, AI grounding via Discover AI, and a broader set of templates and personalization controls. Evaluate DCX when you need more than a portal layer on top of your existing CCMS.

Can we keep our existing CCMS?

Yes. Connectors for Heretto, Paligo, MadCap, IXIASOFT, Confluence, SharePoint, and custom sources are part of the Enterprise package. You bring your authoring source and DCX becomes the unified product knowledge layer. Many customers eventually consolidate onto Discover CCMS, but it's not required.

What's the scale ceiling?

Production hubs on Discover CDP routinely run with millions of Indexed Content Units across multiple locales, products, and versions. The platform is sized for Fortune 500 product catalogs — UKG, Dolby, and Cisco Webex run on this infrastructure.

Yes. Insight Search is included and is what most teams ship with. If you've standardized on Coveo, Elastic, Algolia, or Lucidworks, DCX exposes clean typed JSON for it to index. Both patterns are first-class — you can switch later without re-platforming.

Is it secure enough for regulated industries?

SOC 2 Type II. 24×7 critical-care support. Unlimited tech support. RBAC, SAML / OIDC / SCIM, MFA. Encryption in transit and at rest with key management. Data residency options. We support Fortune 500 financial services, healthcare, and manufacturing on this stack.

How long does a hub launch take?

Template-based launches go live in 4–8 weeks: ~1 week theming, 2–3 weeks content migration and integrations, 1–2 weeks UAT and soft launch. Fully custom builds with bespoke layouts take longer. Both paths use the same delivery infrastructure — you can start templated and customize over time.