Cloud & DevOps / Infrastructure blueprint
NEZEN Developer Platform
An internal developer platform blueprint connecting Backstage templates, identity, delivery pipelines, and Kubernetes policy guardrails.
- Focus
- Infrastructure & platform engineering
- Project type
- Infrastructure blueprint
- Core technologies
- Backstage · Keycloak · Tekton · Terraform

Context
The engineering problem
Creating a service often means repeating repository setup, infrastructure wiring, delivery configuration, and security decisions across teams.
Architecture at a glance
A simplified map of the intended relationships in this blueprint. Integration gaps are described in the implementation scope; arrows do not establish a running deployment.
- clientDeveloperPortal accessgatewayBackstage / identity
- gatewayBackstage / identityService scaffoldingserviceService templates
- serviceService templatesDelivery workflowinfraTekton delivery
- infraTekton deliveryProvision / deployinfraTerraform / EKS
- infraTerraform / EKSPlatform controlsgatewayIstio / OPA
All system components (6)
- Developerclient
- Backstage / identitygateway
- Service templatesservice
- Tekton deliveryinfra
- Terraform / EKSinfra
- Istio / OPAgateway
Approach
Implementation decisions
Standardize the starting point
A golden-path microservice template captures a repeatable starting workflow for service creation.
Make delivery composable
Tekton tasks separate cloning, image builds, analysis, policy scanning, and Terraform operations.
Bake in platform boundaries
Identity, mesh, and policy modules describe shared controls that individual teams should not need to reinvent.
Explore the implementation
Start with the source.
These entry points connect the architecture to the implementation.
- Microservice template ↗backstage/templates/golden-path-microservice/template.yaml
- Infrastructure composition ↗terraform/main.tf
- Build task ↗kubernetes/tekton/tasks/kaniko-build.yaml
- Non-root policy ↗policies/opa/k8s/no_root_user.rego
Implementation scope
Platform engineering blueprint with service templates and infrastructure modules. The custom Backstage action, placeholder build-image digest and policy integration need implementation and validation before the workflow can run end to end.