MEDcloud – Modular IoT Platform with Integrated Blazor Server Web Modules

The Challenge

Mediateknik AB had grown their product portfolio organically. MEDguard existed as a standalone .NET MAUI mobile app. It had its own login flow, camera control, and status logic handled entirely within the mobile client via REST calls. MEDrecycle was built as a separate web application.

As the product family expanded, this approach created real problems:

• Duplicated logic across products
• Isolated authentication against an external IdP
• No shared data layer
• Increasing cost of maintaining separate codebases for each solution

Each product worked in isolation. This made it difficult to build new modules quickly, share infrastructure, or give customers a unified experience across Mediateknik's growing service offering.

What was needed was a platform — a shared foundation to own the cross-cutting concerns (authentication, MQTT ingestion, device state, analytics). Individual product modules could then focus purely on their own domain logic, workflows, and UI.

At the same time, MEDGuard needed to be modernised. The move from a mobile-only experience to a web-based module was not just a technical migration — it required a clear rethinking of the application's architecture:

• From a single-camera mobile session to a multi-device, multi-tenant web module
• From isolated app logic to a module consuming shared platform services
• From legacy authentication against an external IdP to Keycloak OIDC within the platform
• From a siloed codebase to a clearly bounded module with defined integration contracts

The Result

The MEDcloud platform gave Mediateknik AB a scalable, shared foundation for their entire connected product portfolio. It replaced a fragmented collection of standalone applications with a unified architecture. New modules can be added without rebuilding core infrastructure.

MEDguard now runs as a Blazor Server web module inside MEDCloud. It delivers significantly more capability than the original mobile app: multi-device management, geospatial analytics, historical trend data, and a role-based multi-tenant access model. All features are built on shared platform services rather than duplicated logic.

Key outcomes

• A production-ready modular platform serving MEDGuard and MEDrecycle from shared infrastructure
• MEDguard modernised from a single-camera mobile app to a multi-device, multi-tenant web module
• Shared authentication, MQTT ingestion, and data services eliminate duplication across products
• Containerised, Docker-ready deployment with reverse proxy support for modern hosting environments
• A clear architectural foundation for onboarding additional product modules as Mediateknik's portfolio grows

About Mediateknik AB

Mediateknik i Varberg AB is a Swedish specialist in broadband connectivity, AI-driven camera surveillance, and connected safety systems. Through their proprietary MEDcloud platform and product family — including MEDguard and MEDrecycle — they serve clients across 12 industries. These include construction, industry, logistics, and the public sector. Smart Source has been Mediateknik's development partner across the full MEDcloud platform, MEDguard mobile app, and MEDrecycle IoT dashboard.

Frequently Asked Questions about MEDcloud

What technologies does the MEDcloud platform run on?

MEDcloud is built on .NET 10 and ASP.NET Core with Blazor Server for interactive components. The platform uses MQTTnet for IoT ingestion, InfluxDB for historical time-series data, SQL Server for operational state, and Keycloak for OIDC-based authentication. Visualisation is handled by Leaflet and Chart.js. Deployment is done via Docker with a multi-stage build.

How is security and access control handled in MEDcloud?

MEDcloud uses Keycloak as its identity provider with OpenID Connect (OIDC) and cookie sessions. A modular access model ensures each organisation and role can only access the modules and devices they are authorised for. This enables secure multi-tenant operation where multiple customer organisations share the same platform infrastructure without risk of data mixing.

What did the migration of MEDguard from a mobile app to a web module involve?

MEDguard moved from a standalone .NET MAUI mobile app with isolated logic to a Blazor Server web module inside MEDcloud. The migration required a complete rethinking of the architecture: centralised authentication via Keycloak, real-time data through the platform's MQTT stream, multi-device management, and geospatial analytics — all built on shared platform services rather than duplicated code.

How scalable is MEDcloud when Mediateknik wants to add new product modules?

MEDcloud is designed with a clear separation of concerns: the platform owns the core infrastructure (MQTT, authentication, data services) while each product module focuses solely on its domain logic. This means Mediateknik can onboard new modules without rebuilding existing infrastructure. MEDguard and MEDrecycle are already running on the same shared foundation.

How is IoT data stored and managed in MEDcloud?

MEDcloud uses a two-layer data model: SQL Server holds the latest operational state per device for instant reads, while InfluxDB stores the complete historical time-series record. Incoming MQTT data is written to InfluxDB through a dedicated bridge with clearly defined contracts. This enables both real-time monitoring and in-depth historical analytics.

Does MEDcloud meet GDPR requirements for public sector customers?

MEDcloud can be deployed on-premise or in European cloud environments under the customer's control. Keycloak authentication with OIDC ensures all access is logged and controlled, and the modular access model guarantees each organisation's data is isolated from other tenants. Smart Source can tailor the platform to meet specific GDPR and security requirements.