HomeA Practical Comparison of Docugate and CIB coSysNicht kategorisiertA Practical Comparison of Docugate and CIB coSys

A Practical Comparison of Docugate and CIB coSys

This site is also available in: Deutsch (German)

COMPARISON

Comparison: Docugate or CIB coSys?

With support for Assentis DocFamily set to end in early 2026, several providers are positioning themselves as successor solutions. Two names come up particularly often in the Swiss market: Docugate from Leuchter IT Solutions AG and CIB coSys from the CIB Group. We’ll introduce both platforms, outline the key selection criteria, and clearly state where we stand as a CIB partner.

Occasion

Support for Assentis DocFamily will end in early 2026

Docugate

Solution from Leuchter IT SolutionsAG

CIB coSys

CIB Group’s Correspondence Management Suite

Current Situation: The Market Is Undergoing a Realignment

The impending end of support for Assentis DocFamily has sparked a small-scale cutthroat competition in the DACH region: Various providers are actively courting the affected installations—ranging from international suites to Swiss solutions focused on core banking. For the institutions involved, this is good news: there is a genuine choice. At the same time, there is a growing risk of being guided by marketing promises rather than by their own requirements.

This article focuses on two options available in the Swiss banking sector. First, because transparency is important to us: ONLU is an implementation partner of the CIB Group. We therefore have a clear perspective—but this comparison deliberately relies on verifiable facts and open-ended evaluation questions rather than sweeping generalizations.

Docugate (Leuchter IT Solutions AG)

A Swiss solution for centralized template management and document creation—from individual correspondence to batch and mass document generation. The vendor explicitly positions Docugate as a migration destination for Assentis DocFamily customers, cites partnerships with Finnova, Avaloq, and IMTF, and, according to its own statements, follows an “API-first” development approach.

CIB coSys (CIB Group)

Correspondence management suite with clearly separated components: CIB webTom (central, version-controlled template repository with roles and approvals), CIB workbench (Word-based template development), CIB webDesk (interactive correspondence in the browser), CIB darkDesk and CIB documentServer (background processing and bulk generation, including PDF/UA), as well as CIB flow for BPMN process automation. According to the manufacturer, coSys generates over two billion documents annually from more than 200,000 active templates.

The selection is based on criteria, not logos

Instead of getting caught up in a feature war, we recommend evaluating both providers based on the same set of questions. These criteria have proven to be decisive in CCM evaluations within the banking sector:
CriterionWhat Matters in the Evaluation
Quantity Structure & BatchHow many documents per day/month, and what are the peak periods (e.g., year-end run)? Request workload data and references for comparable volumes—test bulk processing and background processing under real-world workload conditions.
Template Creation & GovernanceWho will maintain templates in the future—IT or the business unit? Compare Word-based creation, versioning, approval workflows, and multi-client support in detail.
Core Banking IntegrationReview existing adapters and reference installations for your own core system (Finnova, Avaloq, others)—including the effort required for customization and the ability to support core banking updates.
Process & Workflow IntegrationHow are approvals, form letters, and downstream processes orchestrated? Weigh the benefits of native BPMN integration (via CIB flow/CIB seven in coSys) against the existing workflow landscape.
Interfaces & API StrategyREST/SOAP, message-based data transfers, archive/DMS, print service providers, envelope stuffing. Review the actual API documentation, not just architecture slides.
Accessibility & FormatsPDF/UA and PDF/A creation, output streams (PDF, AFP, PostScript), e-channels. Plan for regulatory accessibility requirements early on.
Operating Model & Data ManagementOn-premises, private cloud, or SaaS? Clarify data residency in Switzerland, client isolation, IAM integration, and operational responsibility.
Migration Support & TCOCompare tools and expertise for migrating DocFamily template libraries, realistic migration efforts, and license, operating, and maintenance costs over five years.

Our Assessment as a CIB Partner

Docugate is a serious Swiss solution—in particular, its announced partnerships in the Finnova, Avaloq, and IMTF ecosystems, along with its “API-first” approach, are compelling arguments for bank implementations that should be evaluated on any shortlist.

Based on our project experience, three points speak in favor of CIB coSys: First, its clear component architecture, which neatly separates interactive correspondence (webDesk) from industrial back-office processing (darkDesk, documentServer) and scales both. Second, the end-to-end template governance with webTom and the Word-based workbench, which truly empowers business units. Third, the native integration with BPMN process automation via CIB flow and CIB seven—a structural advantage for institutions that view documents not in isolation but as part of their process landscape. Added to this is CIB’s documented experience migrating from various legacy systems.

However, which platform is best suited for a specific case depends on your own requirements profile—which is why we recommend a structured platform comparison with a proof of concept based on your own representative templates, rather than on vendor demos.
Pragmatic evaluation tip: Select three to five representative DocFamily templates—a simple standard correspondence document, a complex contract, and a bulk processing task—and have both providers implement exactly these in a proof of concept. This allows for an objective comparison of data input, rendering, batch processing behavior, and the effort required to make changes.

Conclusion

The end of Assentis support doesn’t force anyone in a particular direction—it opens a window of opportunity to make an informed platform decision. Docugate and CIB coSys are two viable Swiss options with different areas of focus. Those who conduct a criteria-based evaluation, demand a thorough proof of concept, and consider migration, operations, and process integration from the very beginning will make a decision that will last well beyond the next support cycle.

In-depth articles: “End of Support for Assentis DocFamily: How to Successfully Migrate to CIB coSys” and “DomTrac, DocuCom, and the End of Support for Assentis.”

Platform Comparison with a Proof of Concept?

ONLU organizes your plans: requirements specification, vendor comparison, proof of concept using your own templates, and a robust migration roadmap—all transparent and criteria-based.

Sources and References

  • Several service providers have consistently stated that support for the Assentis DocFamily will end “in early 2026”; individual contract terms and extended support provisions should be reviewed separately.
  • Leuchter IT Solutions AG publicly positions Docugate as a migration destination for Assentis DocFamily customers, citing partnerships with Finnova, Avaloq, and IMTF, as well as an API-first development approach. Information about Docugate is based on publicly available vendor information (as of July 2026).
  • CIB describes CIB coSys as consisting of the components CIB webTom, CIB workbench, CIB webDesk, CIB darkDesk, and CIB documentServer, as well as CIB flow; according to the manufacturer, over two billion documents are generated annually from more than 200,000 active templates.
  • Disclosure: ONLU AG is an implementation partner of the CIB Group. This article is not a substitute for an individual evaluation.


As of July 21, 2026


Leave a Reply

Your email address will not be published. Required fields are marked *

Warning: file_exists(): open_basedir restriction in effect. File(action-scheduler-en_US.mo) is not within the allowed path(s): (/home/httpd/vhosts/onlu.ch/:/tmp/) in /home/httpd/vhosts/onlu.ch/httpdocs/wp-content/plugins/wpml-string-translation/classes/MO/Hooks/LoadTranslationFile.php on line 82 Warning: file_exists(): open_basedir restriction in effect. File(action-scheduler-en_US.l10n.php) is not within the allowed path(s): (/home/httpd/vhosts/onlu.ch/:/tmp/) in /home/httpd/vhosts/onlu.ch/httpdocs/wp-content/plugins/wpml-string-translation/classes/MO/Hooks/LoadTranslationFile.php on line 85