Skip to content

Platform Overview

This document provides a high-level overview of the platform’s core technical components, including deployments, integrations, infrastructure, authentication (SSO), and MQTT-based messaging. It is intended to give engineers, partners, and stakeholders a shared understanding of how the platform is designed and how its major systems interact.

Deployments

The platform uses a GitOps-based deployment model to ensure consistency, traceability, and reliability across environments.

  • Source code is managed in Git repositories.
  • CI pipelines build, test, and package applications as container images.
  • Container images are stored in a centralized registry.
  • Kubernetes manifests define the desired application state.
  • A GitOps controller continuously reconciles the declared state with the running environment.

This approach enables: - Automated deployments - Easy rollbacks via Git history - Clear separation between build and deploy responsibilities

Integrations

The platform integrates with internal and external systems through well-defined interfaces and APIs.

Key integration patterns include: - REST and HTTP-based APIs for service-to-service communication - Event-driven integrations for asynchronous workflows - Secure authentication and authorization between services

Integrations are designed to be: - Loosely coupled - Versioned and backward compatible - Observable and traceable

Infrastructure

The platform runs on cloud-native infrastructure designed for security, scalability, and high availability.

Core Infrastructure Components

  • Managed Kubernetes for container orchestration
  • Virtual private networking with public and private subnets
  • Multi–availability zone deployments for resilience
  • Managed load balancing and routing
  • Persistent storage for stateful workloads

Infrastructure Principles

  • Infrastructure as Code (IaC)
  • Least-privilege access
  • Fault isolation and redundancy
  • Cost-aware resource provisioning

Single Sign-On (SSO)

Authentication and authorization are centralized through a Single Sign-On (SSO) mechanism.

  • Users authenticate via a trusted identity provider.
  • Standard protocols such as OIDC or OAuth 2.0 are used.
  • Access tokens are issued and validated by services.
  • Role-based access control (RBAC) governs permissions across the platform.

SSO provides: - A consistent login experience - Improved security posture - Simplified user and access management

MQTT Messaging

The platform supports MQTT-based messaging for real-time and event-driven communication, particularly for device and sensor workloads.

Messaging Characteristics

  • Lightweight publish/subscribe model
  • Topic-based message routing
  • Supports high-throughput, low-latency communication
  • Suitable for constrained or intermittently connected clients

Common Use Cases

  • Telemetry and sensor data ingestion
  • Device command and control
  • Status updates and event notifications
  • Near real-time data streaming

Messaging is designed to be reliable, scalable, and secure, with topic-level access control and monitoring.

How These Components Work Together

  • Deployments ensure applications are built and released consistently.
  • Infrastructure provides the secure and scalable foundation.
  • Integrations connect services and external systems.
  • SSO governs user and service identity across the platform.
  • MQTT messaging enables real-time, event-driven communication.

Together, these components form a cohesive platform that supports modern, distributed workloads.

  • Deployment Architecture
  • Infrastructure Overview
  • Integration Standards
  • Authentication & SSO Guide
  • MQTT Messaging Architecture