Mighty QuinnConsultingMighty Quinn Consulting — home

crimSun

Files, messages, mail, calendar, meetings — air-gapped if you need it

Category
Custom Built, complexity tier 3 of 3
Status
Live
modules in one product
6
Stack
  • Go
  • PostgreSQL
  • Keycloak
  • Collabora
  • Stalwart
  • LiveKit
  • ClamAV
  • Traefik

The problem

Anyone working on classified or otherwise protected material gets offered two things. Either a cloud suite that does everything, but carries the data outside the boundary you control. Or an accredited single-purpose tool that is allowed to do exactly one thing — exchange files, say — while chat, mail and meetings carry on somewhere else entirely.

The usual way out is to assemble the suite yourself: a file service, a messenger, a mail server, a video tool. That produces four things to operate, four update paths, four identity models and four security reviews — and, at the end of it, no single record of who did what and when, because every tool keeps its own log.

What it does

crimSun is a product rather than a kit: one web login, one interface for desktop and mobile, in German and English, with six modules behind it.

  • Files and documents — role-based encrypted containers, nested folders, full version history, Office editing and in-browser viewing.
  • Messages — one-to-one and group chat with presence and real-time delivery. Matrix is supported as an option where the messenger itself has to be certified.
  • Mail — a full webmail client with folders, drafts, contacts and attachments, every message scanned for malware before it is sent.
  • Calendar and meetings — a shared calendar, invitations and free/busy, plus video meetings with embedded group chat and optional media E2EE.
  • Dashboard — recent documents, unread mail, active chats and the next meeting with one-click join.
  • Audit — a tamper-evident, append-only record of every security-relevant action, with a separate auditor role and SIEM export.

One application, one trust boundary

Behind the interface sits a purpose-built Go core, and it is the only place policy is enforced. It authenticates, authorises, performs all cryptography and orchestrates a small number of proven open-source services. The reverse proxy is the only TLS edge.

Encryption is envelope-based: a separate key per object under a key-encryption key, AES-256-GCM per BSI TR-02102, with KEK rotation and custody in a PKCS#11 HSM. Destroying the key destroys the data — crypto-erase rather than overwriting.

It runs on-premise or hosted, on a single node or as a multi-node cluster, down to modest hardware for field use. Air-gapped operation is not a special case but the normal one: nothing in the suite phones home.

Where the limits are

For classified work, a limit stated honestly is worth more than one oversold. Three of them therefore belong on the same page as everything else:

  • Not yet formally accredited. crimSun is built to VS-NfD requirements and designed for the buyer-led self-accreditation route that has been the normal path since September 2025. We supply the cryptography, audit and hardening documentation for the assessment — the approval itself is a joint programme with the authority, not a tick in a datasheet.
  • Encrypted at rest, not zero-knowledge. Office editing and mail need short-lived server access to content. Files, chat, calendar and mail attachments are encrypted per object; mail bodies live in the mail server and are encrypted at rest at the volume level. We say precisely where data is in the clear — and log every access to it.
  • Some things are options, not defaults. HSM custody, S3 object storage, federation with the customer's directory and external S/MIME mail are supported hardening and connectivity options. Which of them are switched on is decided by the protection requirement, not by us.

Why custom built and not a tier down

The other two categories fail here for the same reason. A smart little helper or a low-code app lives on a platform somebody else operates, whose cryptography, logging and update path you do not control. For a trust boundary that is the entire point: it has to be small, completely describable and auditable, and it has to work with no connection to the internet.

So the core is written and compiled in-house — light enough for a hardened field device, strict enough for a data centre. The pieces around it are deliberately not in-house: identity, Office rendering, mail, media and malware scanning are proven, open-source, sovereignly operable services. Each of those choices reduces attack surface and accreditation effort.

More Custom Built

Custom Built, complexity tier 3 of 3

Signed, or it doesn't run

A self-service portal that checks every Office macro automatically and only lets signed, reviewed code run.

1central inventory of every macro in the company

  • Power Automate
  • Power BI
  • SharePoint Online
  • Outlook