TrustAbout TrustKern
Built in Berlin by engineers who believe industrial IoT deserves real security architecture — not just TLS and hope.
Our vision
Industrial sensors generate some of the most sensitive operational data in existence — production metrics, environmental readings, equipment health. Yet most IoT platforms treat the gateway as a trusted component, giving it full access to plaintext telemetry.
We started TrustKern with a simple conviction: the gateway should never see plaintext. If you can design the system so that data is signed and encrypted at the sensor — in dedicated security hardware — and only decrypted inside a boundary the operator controls, you eliminate an entire class of risk. No compromised edge device, no rogue operator, no supply chain attack on the gateway can expose sensor data.
That's the architecture we've built: hardware-rooted identity, gateway-blind forwarding, and a decryption boundary that stays under your control.
The founders
Murat Akdeniz
Software engineer and systems architect. Designed the full-stack platform — from Zephyr firmware and secure element integration to the Go backend, Kubernetes infrastructure, and iOS companion app.
Zane Atlas Muslu
Business and operations lead. Responsible for go-to-market strategy, customer development, and building partnerships in regulated industrial verticals across the EU.
The company
TrustKern is a product of Eitan & Meir GmbH, a company registered in Berlin, Germany. We design, build, and operate every layer of the stack — sensor firmware, gateway software, cloud backend, and management applications.
What we believe
Security is architecture, not a feature. You can't bolt on trust after the fact. The cryptographic boundaries, key management, and trust model need to be designed in from the start — at the hardware level.
Data sovereignty is a deployment decision. Operators should choose where decryption happens — EU-hosted, customer-controlled, or fully self-hosted — without changing a single line of sensor firmware.
Industrial IoT should be operable. Secure device commissioning, safe firmware updates with rollback, fleet health monitoring, and clear lifecycle management. Not SSH scripts and spreadsheets.