About NinetyX
The platforms your applications and data depend on
NinetyX is an engineering consultancy in Hanoi, Vietnam, working in three practices: Multi-Cloud Consulting, DevSecOps and Data & AI. We set up the layer your applications and data run on, as code your team owns.
Hanoi, Vietnamservice@ninetyxtech.comWhat the published work shows
What the published work shows
What we do
Multi-Cloud Consulting sets up landing zones: the management hierarchy, policy, network topology, identity and cost model that every later workload is deployed into. DevSecOps puts security and quality checks inside the delivery pipeline as gates, with each result routed to the team that owns it.
Data & AI sets up data platforms, tested pipelines, a semantic model with agreed metric definitions, and AI applications evaluated before each release. Our published write-ups do not yet cover Data & AI, so we describe it by method rather than by result.
The handover is the same in every practice. You keep the code in your repositories, the pipeline definitions, the runbooks and decision records, and engineers on your side who can run them.
Where we work
Banking and financial services come first. Two of our three published engagements are in banking: a governed Azure landing zone, and an omnichannel banking platform running on Microsoft Azure.
That platform runs its workloads on Azure Kubernetes Service, with every data service reached only through a private endpoint. Our DevSecOps work spans banking, financial services, manufacturing and retail.
Regulated environments shape how we build. Naming and tagging conventions, policy as code, disaster recovery and continuity design, and an auditable change trail are specified from the start, not added once audit asks.
How an engagement runs
Four steps, whichever practice you start with: assess and scope, design and sign-off, build in your repositories, then hand over and tune. Each step ends with something your team reviews.
We work through your change control and access rules, not around them. Where a simpler design meets the need, we recommend it and say plainly what it gives up.
How we work
Four steps, each ending in something you review
01
Assess and scope
We review your current estate, delivery process and constraints with your engineers, then agree the scope, the owners and the decisions that have to come first.
02
Design and sign-off
We write down the architecture, the controls and who owns each part. Your team reviews and signs it off before any infrastructure or pipeline code is written.
03
Build in your repositories
We build as code in your repositories and through your change process, so your engineers review each increment as it lands rather than at the end.
04
Hand over and tune
We hand over runbooks and decision records and work alongside your engineers until they run it themselves. Then we tune cost, performance and controls with you.
Start from the platform you have today
Tell us what you run, what is holding back the next release or workload, and who owns it. An engineer replies with questions and a proposed first step.