HIN Gateway migration: Stargate or an alternative
HIN is replacing the classic, SEPPmail-based Mail Gateway with the new HIN Gateway, developed in the “Stargate” project. This is more than an appliance swap: architecture, key management and transport change. I assess with you whether Stargate or another solution fits your environment, and support the cutover through to the shutdown of the old gateway.
- HIN
- Stargate
- HIN Mail Gateway
- SEPPmail
- Exchange Online
- Application Mail
What changes with Stargate
The new HIN Gateway is a mail-capable mesh node per organization: SMTP-compatible towards your own mail system, internally with decentralized key management, WireGuard transport between the instances, and deployment as a VM image or with Docker Compose. This changes firewall rules, operational responsibility, monitoring and the interaction with Exchange Online or Exchange Server. The rule set that has grown on the old gateway, application mail from scanners and business applications, and the handling of recipients without a HIN address all have to be planned anew.
Services
- AssessmentWhich functions the current gateway actually performs: rules, application mail, domains, recipients without a HIN address, dependencies on Exchange and the firewall.
- Move to StargateInstallation, network and firewall rules, mail routing to and from the mesh node, testing and cutover.
- Evaluating alternativesWhether operating without an own gateway or another encryption solution is the better fit depends on mail volume, application mail and requirements; the decision is documented in a traceable way.
- Exchange integrationAdjusting connectors and transport rules so that no mail loops and no spoofing verdicts occur.
How an engagement runs
- AssessmentRecord the functions, dependencies and submitting systems of the existing gateway.
- Target design and planningStargate or an alternative, maintenance windows aligned with HIN’s dates.
- Parallel operation and cutoverTest traffic through the new gateway, then move routes one at a time and reversibly.
- DecommissioningRemove the old gateway from routing, firewall and monitoring, document the target environment.
Real-world examples
- KB: HIN, Mail Gateway and Stargate: trust model, mail paths and the Stargate target architecture at a glance.
- HIN platform renewal 2026: Access Gateway, Client and deadlines that run in parallel with the gateway replacement.
- Encryption gateway behind Exchange Online: avoiding mail loops and spoofing verdicts in the HIN scenario.
- Backing up and restoring the HIN Mail Gateway: keeping the existing gateway operationally reliable until it is replaced.
