Skip to content

Service Map

Complete map of all services in the Monozu Cloud monorepo — where they live, what they do, and how to reach them.

PropertyValue
PathBackend/
LanguageGo 1.26
FrameworkFiber v3
Port (local):8000
Production URLAzure App Service (e.g. https://api.cloud.monozu.io)
DeploymentDocker → Azure Container Registry → Azure App Service
DatabaseAzure SQL Server (multi-tenant RLS)

Responsibilities:

  • REST API for all Cloud Frontend features (/api/v1/*)
  • WebSocket hubs for real-time features (/api/ws/vpn, /api/ws/security)
  • JWT authentication and OIDC (Microsoft Entra ID)
  • Multi-tenant data isolation via Azure SQL Row-Level Security
  • Background jobs: CVE feed sync, vulnerability scanning, audit log retention
  • Edge device registration and command dispatch (/api/v1/devices/*, /api/v1/commands)
  • Internal M2M endpoint for Management (/internal/license/refresh)
  • Admin cross-tenant endpoint (/api/v1/admin/*) when ADMIN_PANEL_ENABLED=true

PropertyValue
PathFrontend/
LanguageTypeScript / React 18
Build toolVite 8
Port (local):3000
Production URLhttps://cloud.monozu.io (Cloudflare Pages)
DeploymentVite build → Cloudflare Pages

Responsibilities:

  • Primary web interface for end users (CMDB, ITSM, Security, VPN, Backup)
  • Communicates exclusively with Cloud Backend API
  • Stores access token in memory, refresh token in HttpOnly cookie
  • Feature-flagged modules loaded from GET /api/v1/me/features post-login

PropertyValue
PathManagement/management-backend/
LanguageGo 1.26
FrameworkFiber v3
Port (local):8080
Production URLAzure App Service
DeploymentDocker → ACR → Azure App Service

Responsibilities:

  • Tenant provisioning and lifecycle management
  • License activation and propagation to Cloud via HMAC webhook
  • M2M communication with Cloud Backend using X-Internal-Token
  • Entra ID OIDC for management staff authentication
  • Internal API prefix: /internal/v1/*

PropertyValue
PathManagement/management-frontend/
LanguageTypeScript / React 18
Port (local):5173
Production URLCloudflare Pages
DeploymentVite build → Cloudflare Pages

Responsibilities:

  • Admin UI for tenant provisioning and license management
  • Used by Monozu operators, not end customers

PropertyValue
Pathingestor/
LanguageGo
Production URLhttps://ingest.cloud.monozu.io (Azure App Service)
DeploymentAzure App Service

Responsibilities:

  • High-throughput ingestion of telemetry from Edge appliances
  • Single endpoint: POST /v1/ingest
  • Auth via X-Device-Key header (provisioning key)
  • Payload kinds: telemetry, log, security_alert, discovery, backup_event

PropertyValue
PathWebsite/
FrameworkAstro 6 + Tailwind CSS 3
Production URLhttps://monozu.io
DeploymentCloudflare Pages
LanguagesPolish + English

Responsibilities:

  • Public marketing site
  • Static site, no backend

PropertyValue
PathWebsiteContactApi/
RuntimeCloudflare Workers
DeploymentCloudflare Workers

Responsibilities:

  • Receives contact form submissions from marketing website
  • Verifies Cloudflare Turnstile CAPTCHA
  • Sends emails via Resend

PropertyValue
PathDocumentation/
FrameworkAstro (Cloudflare Pages)

Responsibilities:

  • Public user-facing documentation for customers
  • Separate from this internal documentation site

PropertyValue
PathInternal-Documentation/
FrameworkAstro 6 + Starlight
Production URLhttps://docs.cloud.monozu.io
DeploymentCloudflare Pages

graph LR
    monozu_io["monozu.io<br>Marketing"]
    cloud["cloud.monozu.io<br>Cloud SPA"]
    api["api.cloud.monozu.io<br>Cloud Backend API"]
    ingest["ingest.cloud.monozu.io<br>Ingestor"]
    docs["docs.cloud.monozu.io<br>Internal Docs"]
    mgmt_be["Management Backend<br>Azure App Service"]
    mgmt_fe["Management SPA<br>Cloudflare Pages"]

    cloud -->|"/api/v1/*"| api
    cloud -->|"ws /api/ws/*"| api
    mgmt_fe -->|"/api/v1/*"| mgmt_be
    mgmt_be -->|"HMAC webhook"| api
    api -->|"M2M"| mgmt_be
PackagePathUsed by
licensingpackages/licensing/Cloud Backend, Management Backend

All CI/CD pipeline definitions live alongside their respective service in azure-pipelines.yml files at the root of each service directory.