A security stack today often holds two to three dozen SaaS tools. Each one has its own login, its own bill, its own GDPR review, and its own API. SecTepe.Comm takes a different path. It is one fully self-hosted platform. It brings email security, threat intelligence, sandbox analysis, identity, SIEM, and backup under one roof. It runs in the EU and does not depend on a hyperscaler.
What Is SecTepe.Comm?
SecTepe.Comm is the communication and security platform of the SecTepe suite. It covers the classic ways people talk to each other: mail, messaging, video, and telephony. On top, it adds layers of defense:
- a mail security gateway with DLP
- sandbox detonation for attachments
- a built-in threat intelligence stack
- single sign-on via Keycloak
- SIEM via Wazuh
- a forensic archive with retention that meets legal rules
The Core Idea in One Sentence
One platform, one identity provider, one audit trail, and one party in charge of hosting, not fifteen contract partners with fifteen sub-processors. That cuts license and integration costs. It also makes compliance work far easier, such as NIS-2, GDPR, and ISO 27001 audits.
The Building Blocks at a Glance
- Mail Security Gateway: filters for inbound and outbound mail with milter support. It uses ClamAV, YARA rules, and an LLM that flags phishing and BEC. It adds outbound DLP (data leak prevention) and a four-eyes check before a high-risk mail is released.
- CAPE Sandbox: suspect attachments are detonated on their own in isolated Linux and Windows guests. Anti-evasion profiles catch modern Office maldocs.
- CTI Stack: MISP, OpenCTI, YARA, and our own Ransomware Intel service, with 30+ OpenCTI connectors set up out of the box.
- Identity & Access: Keycloak is the central identity provider. It supports OIDC, SAML, and MFA. An optional AD connector serves hybrid setups.
- Security & SIEM: Wazuh collects endpoint data and logs. OpenBao manages secrets. You also get the Coraza WAF and a Linkerd service mesh with automatic mTLS.
- Observability: Prometheus, Grafana, Loki, SigNoz. Ready-made dashboards show the mail pipeline, sandbox delay, and whether CTI syncs succeed.
Who Is the Platform For?
It is built for mid-market firms and public bodies that want three things at once:
- Real data sovereignty: no access from third countries and no hyperscaler sub-processors.
- Built-in security: one system, not ten best-of-breed islands.
- A total cost of ownership you can plan: no SaaS bill that keeps growing with per-mailbox or per-event pricing.
It is a strong fit for groups that fall under KRITIS or NIS-2, and for processors with strict GDPR needs. It also suits firms whose cyber insurance now asks them to put technical measures in place that they can prove.
Three Reasons Self-Hosting Is Back Right Now
- Geopolitics & the Cloud Act: the US Cloud Act still lets US authorities reach data held by US providers, even when it is hosted in the EU. Self-hosting takes that question off the table.
- SaaS costs out of control: per-seat and usage-based pricing does not grow in line with the value you get. A platform run on-prem or with an EU hoster most often pays for itself in 12–24 months.
- Audit duties: NIS-2, DORA, and ISO 27001:2022 call for clear proof of data flows, third-party risk, and incident response readiness. A platform you run yourself is far easier to audit.
What Comes Next?
Over the next few weeks we will post deep dives on each building block here. Topics range from outbound DLP and CAPE sandbox integration to NIS-2 readiness tools such as the audit log and alert rules. Want to see it in a live system? We can set up a demo at short notice.
Conclusion
SecTepe.Comm is not one more product in a crowded security market. It tries to bring the key tools of a modern security and communication stack together. The result is sovereign, built as one piece, and easy to audit. If you take data sovereignty seriously in 2026, you can hardly avoid a self-hosted strategy. And if you already follow one, a single platform gives you one thing above all: clarity.