Platform Engineering

Internal Developer Platform

Five planes behind one portal: orchestration, pipelines, runtime, and observability and security across all of them.

Developers see a portal; four more planes do the work. A request from a golden-path template goes through the control plane, which scaffolds the repository and pipeline, provisions infrastructure as code and deploys by GitOps. Telemetry, scans, policy, audit and cost run across every plane.

pick a templateSSO · rolessynctelemetrystatusscanevery changePeople & identity1 · Developer portal2 · Orchestration & control plane3 · Pipelines & delivery4 · Infrastructure & runtime5 · Observability & securityEnvironments · approvals from one configuration databaseDevelopersKeycloaksingle sign-onBackstage portalService catalogueowners · systemsGolden pathsapp + IaC + pipelineDocs · runbooksApp statuspipelines · costPlatform APIworkflowsApprovalsper environmentKubeVelaapp modelCrossplanecloud resourcesConfiguration DBsource of truthGitLab CIbuild · test · scanArgo CDGitOpsJenkinsVM releasesGitHub ActionsHarbor · Nexussigned imagesTerraformlanding-zone modulesAWS CDKHelmchartsEC2 · ECSVMs · containersAmazon EKSmicroservicesGrafanadashboardsLoki · Tempologs · tracesAudit logimmutablePolicy as codeguardrailsTrivyimage scan · SBOMSonarQubequality gatePrometheusmetricsCost per teambudgets · alertsDevelopmentdeploy freelyStagingmanager approvalProductionticket + admin approval

Point at a component to light its links; select it for what it does here and the practice that makes it right.

When to use it

  • Several teams keep asking for the same environments, pipelines and access
  • Developers wait on tickets; security and cost are checked late
  • Access and audit differ from team to team

How NGT delivers it

Built from code, reviewed at a gate by an NGT architect, and handed over with runbooks your team can run.

Platform Engineering