IoT infrastructure

Lt’s deep dive into Kamea IoT infrastructure.

This is a fundamental point to understand: our device management platform is designed so that you remain the owner and fully autonomous. Unlike solutions hosted by the vendor, Kamea is deployed on your infrastructure, whether in the cloud (Azure or AWS) or on-premise.

This approach serves a clear purpose: no dependency on us and complete freedom to evolve your solution.

The advantages of this IoT infrastructure

Independence and control: You deploy Kamea in your own environment, without vendor lock-in. You keep full control over your architecture and its evolution.
Multi-cloud flexibility: Native support for Azure and AWS, with an architecture designed to avoid lock-in.
Simplified maintenance: We prioritize managed services and containers to reduce operational overhead (patching, updates, security).
Built-in performance and security: Component and protocol choices (TLS, network segmentation) ensure scalability and robustness without compromise.
Extensibility: Thanks to Kubernetes, you can migrate or adapt your deployment without major redesign.

Two possible IoT architectures

Kamea relies on two architectural models to meet different needs: one based on Azure managed services and another orchestrated by Kubernetes for greater flexibility.

1. Azure version (PaaS approach)

In this model, Kamea leverages Azure managed services such as Azure Functions, App Services, and Service Bus. This approach simplifies maintenance by delegating OS management and updates to the cloud provider.

Deployment is automated using Terraform files, which create all the necessary resources in Azure. These files are configurable to adapt to your specific requirements (resource sizing, performance, etc.).

The goal is clear: reduce operational workload and allow teams to focus on functionality rather than infrastructure.

2. Kubernetes version (AKS, AWS EKS, or on-prem)

The second option is based on Kubernetes, a standard container orchestrator that offers maximum portability across cloud environments. This architecture addresses two key challenges:

Reducing vendor dependency: Kubernetes enabl without a complete redesign.
Ensuring scalability: Kubernetes makes resource adaptation easier as needs evolve.

Deployment follows an automated workflow:

Terraform to create the cloud infrastructure and Kubernetes cluster.
Kubernetes manifests to deploy application components within the cluster.
CI/CD pipelines (GitHub by default, portable to GitLab or others) to orchestrate updates and ensure reproducibility.

You can also set up a Kubernetes cluster on premise, but this requires additional configuration.

Kamea’s infrastructure is robust, proven, and designed for your autonomy.

It combines:

Ease of deployment without sacrificing security or performance.
Native scalability through Kubernetes or PaaS resources.
Strategic freedom: You own your solution and can adapt or evolve it as you wish.

By choosing Kamea, you eliminate the critical risk of vendor lock-in. You maintain control, secure your operations, and benefit from a modern architecture built to last.