Platform Engineering
Golden paths, not ticket queues: your best practice turned into self-service.
At a glance
NGT builds internal developer platforms that turn your best practice into self-service: pick a golden-path template, fill in a short form, get a running service with pipeline, guardrails and cost tracking, in minutes, not weeks.
Self-service from vetted templates: an environment in minutes, not a queue of tickets.
Portal, orchestration, GitOps, infrastructure and policy as code on AWS, Azure or Google Cloud, chosen per client.
A thin platform first, measured on delivery, adoption and cost, then grown team by team.
One platform, five planes
What stands behind the portal. Select a component for what it does and the practice behind it.
- A portal developers chooseCatalogue, golden-path templates, docs and each application's status in one place.
- A control plane behind itRequests become workflows and approvals; repositories, pipelines and infrastructure come from code.
- Guardrails on every planeScans, policy as code, an immutable audit log and approvals per environment.
- Cost seen before it is spentEstimated before provisioning, tracked per team and component, with budget alerts.
Point at a component to light its links; select it for what it does here and the practice that makes it right.
Problems we solve
Five problems that send customers to a platform, each with the architecture we use. Select one.
Weeks of tickets for one environment
Every environment goes through a ticket, a review and manual provisioning. Security comes back after the build, and developers wait weeks.
- Golden-path templates and a short form in the portal
- Repository, infrastructure and pipeline created from code
- Guardrails pass before deploy; cost tagged from day one
An environment in minutes from a short form, with the guardrails already passed.
Point at a component to light its links; select it for what it does here and the practice that makes it right.
What NGT delivers
Each service line can start on its own; together they make an internal developer platform.
Explore Platform Engineering
6 pages, each a few minutes to read.
Frequently asked questions
What customers ask first.
No. Backstage is a common choice and NGT has delivered Backstage-based portals, but the portal is one of five planes.
We can build on a portal you have, or start with templates and pipelines and add the portal later.
The first deliverable is an MVP with two or three pilot applications: a portal, the first golden-path templates and the pipelines behind them. We grow from there, team by team.
No. Microservices on EKS and monoliths on EC2 can share one golden path: GitOps for one, Jenkins and Ansible with blue-green releases for the other, with the same checks and dashboards.
The rules live in the platform: scans and policy as code in every pipeline, approvals per environment, time-boxed production access and an immutable audit log. Security reviews the path once instead of every project.
Cost is part of the path: estimated before provisioning, tracked per team and component, with budget alerts. Teams see their own spend in the portal.
Your choice. NGT can run it as a product with you, or hand it over. Large programmes include an insourcing stream so your engineers can operate and extend it.
