Secure communication. Simple. Under your control.

Rocket.Chat is a customisable communication and collaboration platform. It stands for topic-based collaboration, service and coordinated communication paths. Which features, licence and operating form are used is defined per project.

Rocket.Chat documents private, read-only and broadcast rooms, role- and attribute-based access control, MFA, TLS support and settings for uploads and retention, among other things. Whether this results in an appropriate level of security depends on the architecture, configuration, operations and reviews of the organisation concerned.

The matrix below classifies different solutions by their documented focus. It is not a ranking, not a security assessment and not a complete procurement comparison: depth of functionality, licence, support, operating model, interoperability and approvals must be reviewed for the specific deployment.

CCNet is the official German-language Rocket.Chat partner and serves customers in the DACH region and beyond. The focus is on clarifying needs and architecture, licence assessment and procurement, implementation and migration, integrating identity concepts and support in operations. The specific service, responsibility and acceptance are agreed per project.

CCNet can structure your communication requirements, plan a suitable architecture, take existing directory and identity concepts into account, accompany rollout and migration and shape an agreed operating path. Alongside compliance questions, this includes operational topics such as roles, access, monitoring, updates and responsibilities. Specific security or compliance commitments do, however, require an individual assessment. CCNet also acts as a procurement partner – in both the public and the private sector.

For data protection officers, the selectable architecture, the control of roles and access, configurable data and retention options and plan-dependent audit functions can be relevant review points. Rocket.Chat does not create automatic GDPR compliance, but it offers the functions needed: legal basis, technical and organisational measures, contracts, storage locations, permissions and operating model must be assessed and documented for the organisation.

Administrators can assign permissions to roles and, where needed, define their own roles with more than 150 granular rights. The documentation also names user, room and workspace administration, API access, identity providers such as LDAP, SAML and OAuth, and options for monitoring and logs. The scope and availability of individual functions depend on the configuration and, where applicable, the licence model.

The Rocket.Chat Marketplace bundles public apps; private apps can be developed and managed for a single workspace. Examples include BigBlueButton, GitHub, Jira Cloud, Google Calendar, Google Drive, Pexip, ClamAV and the DLP app. Not every app is available in every plan or operating model; licence, permissions, data flows and support should be reviewed before rollout.

Rocket.Chat can be extended via Marketplace apps, APIs and private apps, among other routes. The official BigBlueButton app makes it possible to start conferences from Rocket.Chat; this requires your own BigBlueButton server. The Rocket.Chat AI app requires a provided LLM and enables AI summaries in chats. A CDR solution for file sanitisation is not promised as a standard Rocket.Chat function: its interplay with uploads, DLP and DLP rules must be designed and tested separately, both technically and organisationally.

CCNet describes zero trust collaboration as the interplay of Rocket.Chat for communication, Pexip for video and Forcepoint for controlled data and file flows. In this approach, architecture, roles, policies, interfaces and operations are planned together. The components are not a blanket pre-configured standard package; the specific technical design is defined for each project.

The official Pexip app for Rocket.Chat makes it possible to start video calls directly from a Rocket.Chat room. The integration connects Rocket.Chat with Pexip Infinity. Setting it up requires, among other things, a Pexip Infinity server, valid certificates, suitable network routes and a Rocket.Chat premium licence. CCNet supports planning, integration and operations as a project-specific video component. Other services such as BigBlueButton or Jitsi can of course be integrated instead of Pexip.

Omnichannel is a paid Rocket.Chat add-on. The specific scope of services, the connected channels, identity verification and data protection and operating requirements must be clarified before implementation.

Rocket.Chat can be run in self-managed environments, in CCNet cloud hosting or as an isolated air-gap workspace. The decision is guided by requirements for data flows, scaling, administration, resilience, interfaces, licence and operations. CCNet supports the clarification of architecture and operating model.

Yes. On request, CCNet carries out deployments and monthly maintenance inside the customer's infrastructure.