Backstage application architecture

Backstage application architecture An architecture diagram generated by Archify. Developer · Self-service user · Users Developer Self-service user Platform engineer · Portal operations · Users Platform engineer Portal operations Backstage UI · React application · Frontend Backstage UI React application Plugin UI · Catalog / TechDocs / Scaffolder / Kubernetes · Frontend Plugin UI Catalog / TechDocs / Scaffolder / Kubernetes Backstage Backend API · Node.js · Backend Backstage Backend API Node.js Plugin backends · Catalog / TechDocs / Scaffolder / Auth · Backend Plugin backends Catalog / TechDocs / Scaffolder / Auth PostgreSQL · RDS / plugin data · Data stores PostgreSQL RDS / plugin data S3 · TechDocs artifacts · Data stores S3 TechDocs artifacts GitHub / GitLab · Catalog / Scaffolder integration · External integrations GitHub / GitLab Catalog / Scaffolder integration EKS cluster · Kubernetes plugin · External integrations EKS cluster Kubernetes plugin ArgoCD · ArgoCD plugin / GitOps · External integrations ArgoCD ArgoCD plugin / GitOps Cognito / Okta · Auth / OIDC · External integrations Cognito / Okta Auth / OIDC Users Frontend Backend Data stores External integrations Legend Frontend Backend Database Cloud Security External

Plugin architecture

  • • Frontend and backend modules compose the portal
  • • Plugins need explicit registration and configuration

Storage

  • • PostgreSQL stores plugin data; S3 stores TechDocs output
  • • Backends call configured integrations

Authorization

  • • OIDC sign-in and permission policy are separate
  • • Shared Kubernetes credentials are not per-user RBAC
  • • Review external permissions and file-based credentials