Parent folderOpen Confluence

RWS Architecture article

Cost Transparency

Make platform costs visible, attributable, and manageable across domains.

  1. Typeprinciple
  2. Statusactive
  3. Domain60-principles
On this page
  1. Principle – Cost Transparency
  2. Summary
  3. Intent
  4. Scope and Applicability
  5. Principles
  6. Per-Domain Implementation
  7. OpenShift
  8. Networking
  9. Storage
  10. Security
  11. Platform
  12. AI

Principle – Cost Transparency

Summary

Make platform costs visible, attributable, and manageable across domains.

Intent

Enable informed trade-offs, encourage efficient use of shared resources, and reduce unexpected spend.

Scope and Applicability

Applies to shared services, infrastructure consumption, and platform capabilities that impact cost profiles.

Principles

  • Provide usage and cost signals alongside service consumption.
  • Align service tiers to cost profiles and documented budgets.
  • Prefer automation that enforces cost guardrails.

Per-Domain Implementation

OpenShift

  • Surface cluster and namespace cost metrics to platform stakeholders.

Networking

  • Track fabric scale and connectivity growth against capacity plans.

Storage

  • Provide storage tiering and retention policies aligned to cost profiles.

Security

  • Publish cost drivers of security controls (log retention, scanning cadence) and offer standard tiers so trade-offs are explicit.

Platform

  • Integrate FinOps governance into platform service delivery.

AI

  • Make AI cost drivers explicit (GPU/CPU hours, storage, and token usage where applicable) and enforce budgets/quotas.

Exceptions

Exceptions require explicit approval with documented cost impact.

Related