Docs
[PLATFORM]

PLTFRMS Architecture

PLTFRMS is built around a layered architecture that separates concerns between edge handling, authentication, and internal service execution.

At a high level, all external requests flow through a central API Gateway, which enforces security, routes traffic, and coordinates communication with internal services.


Request Flow

Every incoming request follows a strict execution path:

  1. The user sends a request to the API Gateway
  2. The API Gateway performs authentication and policy validation via the AUTH service
  3. If authentication fails, the request is immediately rejected
  4. If authentication succeeds, the gateway enriches the request (routing, headers, and signed context)
  5. The request is forwarded to the appropriate Product Service Manager with a signed JWT
  6. The Product Service Manager validates the JWT before processing
  7. The service executes the request and returns a response via the gateway

This ensures that every request is validated, traceable, and securely signed before reaching internal services.


Security Model

Security is enforced at multiple layers:

  • Edge layer (API Gateway): authentication, policy checks, routing decisions
  • Identity layer (AUTH): token validation and access control
  • Service layer (Product Service Manager): JWT verification before execution

This layered approach ensures that no service is directly exposed without verification.


Architecture Diagram


Auditz diagram



Events Flow

Each PLTFRMS product is driven by a dedicated manager service, which acts as the source of truth for that product’s state.

State changes within the manager are emitted as events into the internal event system.

Downstream services subscribe to these event topics and react accordingly. Depending on the service, events may be:

  • processed locally to update state or trigger workflows
  • transformed or enriched before further handling
  • republished to other event topics for additional consumers

This event-driven model decouples services, allowing each product to scale and evolve independently while remaining part of a cohesive system.


Events Diagram


Storage Diagram


CDN Diagram


INFRA Provisioning Diagram


Network Diagram