Fluid Topics

What is Fluid Topics?

Fluid Topics is a product knowledge platform that gathers technical documentation from many authoring tools and delivers it through portals, chatbots, in-product help and support desks. It also prepares that content for AI applications.

The idea is to stop product knowledge from living in separate silos. Content written in DITA, Paligo, Adobe Experience Manager, MadCap Flare, Confluence, Word, Markdown or OpenAPI files is ingested into one hub. From there, the platform adds semantic search, enrichment and access control, then publishes the same content to every channel that customers, support agents and AI assistants use.

The business began in 1999 as Antidot, founded by Fabrice Lacroix, Stéphane Loesel and Jérôme Mainka, and rebranded as Fluid Topics in 2014 when it launched its content delivery platform. The about page names Kennet Partners, Ventech and Crédit Mutuel Innovation as investors and says the team works across six countries. Recent additions include a RAG chatbot service and a production-ready MCP server for agentic AI.

Key Features

Unified ingestion plus AI-ready delivery is what Fluid Topics sells, letting one documentation source feed portals, chatbots and agents without replacing existing authoring systems.

• Multi-source ingestion: The platform imports content from DITA, Heretto, Paligo, MadCap IXIA CCMS, Flare, RWS, Schema ST4, Confluence, SharePoint, Word, PDF and HTML5. Writers keep their current tools while readers get one consistent experience.
• Semantic search: Search is tuned for domain-specific technical language rather than general web queries. It aims to return contextual results across every touchpoint, so users find the right procedure without knowing the exact wording.
• RAG chatbot service: Teams can launch a chatbot grounded in their own documentation using prebuilt orchestration, embeddings and vector search. Answers respect existing access controls, which matters when some content is restricted to partners or paying customers.
• MCP server and AI services: A production-ready MCP server lets external applications and agents query the knowledge hub. Core services such as embeddings, semantic search and prompt management are exposed for teams building their own AI features.
• Multichannel delivery: The same content is published to documentation portals, in-product help and helpdesk tools such as Zendesk, Zoho Desk and Salesforce. Support agents and customers therefore see identical, current answers.
• Content analytics: An analytics suite tracks document performance, engagement and satisfaction through star ratings. Documentation teams can see which topics people read, which they rate poorly and where content needs work.

Pros

Keeping existing authoring tools is the strongest argument for Fluid Topics, because organisations can add search and AI delivery without migrating years of structured content.

• No authoring migration: Connectors cover most major component content management systems and common formats. Technical writing teams avoid a risky platform change while still modernising how readers access content.
• Grounded AI answers: Chatbot answers draw on approved product documentation rather than general model knowledge. This lowers the risk of invented instructions, which is important for regulated or safety-critical equipment.
• Reported support deflection: The site cites Darwinbox at 65 per cent support deflection and Teradata at 5 million portal visits. These case figures suggest real gains for large documentation estates.
• Enterprise security: Fluid Topics states ISO 27001 certification and GDPR readiness. Access control carries through to search and chatbot answers, which suits companies with partner-only or customer-only material.
• Established vendor: The company has operated since 1999 and lists customers such as Siemens, KONE, Liebherr and Johnson Controls. Buyers get a long track record rather than a recent start-up.

Cons

Hidden pricing is the first hurdle with Fluid Topics, since the official site publishes no plans and directories quote conflicting monthly figures.

• No public pricing: Costs only emerge through a sales conversation. Capterra lists a starting price of $900 a month and Futurepedia $500, but neither figure comes from Fluid Topics.
• Enterprise scope: The platform targets organisations with large, structured documentation sets. A small software team with a few dozen help articles may find a simpler help centre tool more proportionate.
• Setup effort: Connecting several authoring sources, metadata and access rules takes planning. Expect a project with technical writers, IT and support involved rather than a same-day launch.
• Trial unclear: Capterra reports no free trial, while Futurepedia mentions 30 days. Ask sales directly whether a pilot or proof of concept is available before committing budget.
• Few public reviews: The Capterra listing showed no user reviews when we read it. Independent evidence of day-to-day use is thin, so reference calls with existing customers become more important.

Who is Using Fluid Topics?

Manufacturers and enterprise software vendors dominate the customer list, with names such as Teradata, JFrog, Hitachi Vantara, Siemens, KONE and AVEVA shown on the site.

• Technical documentation teams: Writers publish structured content from several authoring tools to one portal. They use analytics to find and improve topics that readers rate poorly.
• Customer support teams: Agents see documentation inside Zendesk, Salesforce or Zoho Desk. They answer tickets faster and deflect repeat questions to self-service.
• Industrial manufacturers: Firms such as Liebherr and KONE deliver manuals for complex equipment. Field engineers and customers search procedures across many product variants.
• AI and product teams: Developers connect assistants through the MCP server. They ground in-product copilots in approved documentation instead of raw model output.

Pricing

Fluid Topics does not publish a price list, so every deployment is quoted after a demo (official site, checked October 2026).

Directories conflict: Capterra reports a $900 monthly starting price with no trial, while Futurepedia lists $500 a month and a 30-day trial.

Disclaimer: enterprise quotes depend on content volume, channels and AI usage, so use directory figures only as rough context for budgeting.

What Makes Fluid Topics Unique?

Treating documentation as a shared source for both people and AI is the core idea. Rather than building a chatbot beside a portal, Fluid Topics feeds the portal, helpdesk widgets, in-product help and AI agents from the same enriched content, with the same permissions.

The breadth of authoring connectors is the second difference. Many help centre tools expect you to write inside their editor, while Fluid Topics accepts output from specialist systems such as DITA tools, Schema ST4 and RWS. That makes it a delivery layer for companies with heavy technical content rather than a replacement for their authoring stack.

Compatibilities and Integrations

Connectors to more than a dozen authoring systems and three major helpdesks give Fluid Topics its reach, with an MCP server covering AI agents.

• Authoring sources: DITA, Heretto, Adobe Experience Manager, Paligo, MadCap IXIA CCMS, Flare, RWS, Schema ST4 and Docufy Cosima are listed. Confluence, SharePoint, Word, Markdown, PDF, HTML5, OpenAPI and Swagger are supported too.
• Helpdesks and CRM: Zendesk, Zoho Desk and Salesforce are named delivery channels. Agents can reach documentation without leaving their ticket view.
• AI agents: The MCP server and RAG services let external applications query the knowledge hub. Access controls still apply to the answers.
• Platforms: Portals are web-based. Capterra also lists Android and iOS access, which we could not confirm on the official site.
• Security: Fluid Topics states ISO 27001 certification and GDPR readiness. Ask for hosting regions and data processing terms during procurement.

Fluid Topics Tutorials

Rollout starts with a sales demo, then moves through a structured implementation with your documentation and support teams.

1. Request a demo and list the authoring systems and formats you use.
2. Agree a pilot scope, such as one product line and one delivery channel.
3. Connect your content sources and map metadata for filtering and access rights.
4. Configure the portal design, search behaviour and user groups.
5. Add the helpdesk integration or chatbot once search results look reliable.
6. Review content analytics monthly and fix topics with low ratings.

How We Rated It

Connector breadth and grounded AI delivery carry Fluid Topics to 4.0 out of 5, while opaque pricing and scarce public reviews keep cost and support scores lower.

Summary

Fluid Topics suits enterprises with large technical documentation estates that want one source to feed portals, helpdesks, in-product help and AI assistants. Its authoring connectors, access-controlled RAG chatbot and MCP server are strong reasons to shortlist it. The main limitation is transparency: there are no public prices, directory figures conflict and independent user reviews are scarce. Smaller teams may find it more than they need. Our tip is to pilot one product line, measure search success and ticket deflection, and ask for customer references before signing.