Skip to main content

Platform Overview

Summary​

The Platform service is the extracted control plane for tenant metadata, platform clients, company profiles, provisioning, commercial records, licensing, entitlements, branding, configuration, audit history, durable jobs, and service-health views.

Audience​

  • Platform and customer administrators
  • Implementation partners
  • Developers, DevOps engineers, solution architects, and security engineers

Overview​

The Platform service owns a PostgreSQL-backed platform data boundary and exposes administrative, onboarding, commercial, entitlement, runtime-resolution, configuration, analytics, and monitoring endpoint groups. It publishes and consumes selected lifecycle events through the shared messaging and outbox foundations.

Purpose​

Platform centralizes cross-tenant control-plane concerns. Identity owns authentication data; the Gateway mediates client routing; downstream services consume authenticated tenant context and may consult platform-owned state where integration exists.

Architecture​

The diagram is conceptual: source confirms the components and route boundaries, but not every dashed runtime integration or its production enablement.

Business concepts​

A tenant is the platform configuration root. A platform client represents the corresponding customer/control-plane record; a company holds organization profile metadata. Plans and subscriptions describe packaging and a tenant’s commercial association. Licenses capture validity and capacity, while features, entitlements, overrides, modules, and flags represent different access-control layers. Branding and configuration tailor tenant presentation and service behavior.

Technical implementation​

  • Implemented: Platform endpoints, persistence, metadata provisioning, entitlement evaluation, licensing evaluation, audit/timeline records, outbox messaging, durable job records, and service probing.
  • Transitional: Canonical tenant and platform-client concepts coexist, as do newer and compatibility endpoint surfaces.
  • Foundation: Optional isolated tenant-database provisioning and provider/channel configuration records are present but are not evidence of production adoption.
  • Requires confirmation: Complete downstream consumption, operational ownership, and automatic Identity synchronization.

Source References​

  • microservices/src/platform-service/Program.cs
  • microservices/src/platform-service/Data/PlatformDbContext.cs
  • microservices/src/platform-service/Api/PlatformAdminEndpoints.cs
  • microservices/src/platform-service/Api/PlatformCommercialEndpoints.cs
  • microservices/src/platform-service/Api/PlatformEntitlementEndpoints.cs
  • microservices/src/gateway-api/Program.cs

See Also​

Keywords​

  • Platform control plane
  • Tenant metadata
  • Service boundary

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-14
  • Review cycle: Quarterly