Platform Components & Technology Stack

Who this is for: Developers and operators who want to know what each part of the TrustBridge platform is built on and how it's deployed.

What you'll learn: The four deployable components of the TrustBridge stack, the technologies behind each, and the ports they use.

Beyond the C SDK layers, the TrustBridge platform is made of the following components, each shipped as a container in the integrated Docker stack.

TrustBridge Backend (tb-be)

A NestJS 10 (TypeScript) REST API served under the /api global prefix on port 3000, with interactive Swagger / OpenAPI documentation at /docs. It persists to MySQL 8 via TypeORM, authenticates users with JWT (Passport) and enforces role- and permission-based guards, and talks to devices through an MQTT client.

TrustBridge Frontend (tb-fe)

A React 19 + TypeScript single-page application built with Vite 7, using Chakra UI for components, TanStack React Query for server state, React Router 7 for navigation, and Axios for HTTP. It's served on port 5173 and resolves the backend URL at runtime via GET /api/discover, falling back to the VITE_APP_ENDPOINT environment variable.

Cloud SDK agent (sandgrain-cloud-app)

A Python 3 asyncio service (application_PoC_MQTT) built on the sandgrain_cloud_sdk library (aiohttp). It bridges MQTT to the SandGrain / CyberRock device and tenant REST APIs over HTTPS, and fetches per-device credentials on demand from the backend (GET /api/devices/credentials-by-tid).

Infrastructure

• MySQL 8 (tb-mysql) for persistent storage.
• Eclipse Mosquitto MQTT broker (tb-mosquitto, image eclipse-mosquitto:2) on port 1883 for all device messaging.

Ports at a glance

When you run docker ps on a healthy stack you should see five containers: tb-be, sandgrain-cloud-app, tb-fe, tb-mosquitto, and tb-mysql.

Related articles: System Architecture Overview · MQTT Topic Reference · Deployment Guide · Infrastructure, Monitoring & Security · Verify Your Installation