SecTepe.Comm– Communication, collaboration & security from one source

SecTepe.Comm is more than a set of tools. About 40 open-source components and SecTepe's own services share one base. It includes one entry point for all web traffic, one central sign-in and a shared bus for events. On Kubernetes, mutual TLS (mTLS) also encrypts traffic between all services.

One identity for every service

One login covers the whole suite. It speaks OIDC and supports MFA with an app code (TOTP) or a security key (WebAuthn). Apps without their own OIDC support are checked at the central entry point first. So your staff sign in once and then reach chat, mail and files.

SecTepe adds its own login extensions. One syncs groups into the chat. Another checks new passwords against known leaks. An AD connector brings in users from your on-prem Active Directory. A bridge based on the SCIM standard does the same for cloud directories such as Azure AD or Okta.

Events instead of point-to-point links

Services report what happens as events on a shared bus. Every event uses the same format. The web UI shows new events live. Each person only sees what is meant for them, their group or their role.

Rules and workflows turn events into actions. A severe SIEM alert can, for example, land in a chat room or start a workflow.

Ways to run it

• Containers on one server. You switch extra modules on with profiles. A lite setup runs only the base stack.
• Kubernetes with GitOps. The cluster follows the state in your Git repository.
• Networks without internet, with a local copy of all container images in fixed versions.
• Your choice of provider. Ready-made templates cover IONOS, Hetzner and private OpenStack clouds.
• Branch offices, with a small package in containers or on a lightweight Kubernetes.

Data sovereignty and trust

You run every component yourself, on your own servers or with an EU provider such as IONOS. Passwords and keys live in a central vault. Services can use it to encrypt stored data.

The SecTepe code is licensed under Apache 2.0. The open-source parts run unchanged at their core. Container images are digitally signed. They ship with a software bill of materials (SBOM) in CycloneDX and SPDX format.

Technical foundation

SecTepe.Comm builds on proven open-source parts: Matrix for chat, Jitsi for video, Nextcloud for files and Keycloak for sign-in. Others include Mailcow, Wazuh, Traefik, n8n, NATS, OpenBao and Linkerd.

Common questions

Can each customer get its own environment? Yes, in the dedicated model. The customer gets its own virtual Kubernetes cluster, its own login area (realm) and its own database. Even the smaller dedicated-lite model has its own realm.

How do I back up my data? On Kubernetes, a backup service saves the state of all services. Restore drills check that a restore really works.

Do I have to run every module? No. A minimal core with chat, mail, sign-in and the central entry point runs on its own. You add other modules when you need them.