Phase 01
Assess
Two weeks inside your systems. Architecture, delivery flow, cost and risk, scored.
Reliability report · Prioritised roadmap
DevOps engineering since 2025
Software that ships often and stays up.
We build, ship and run production systems for teams that cannot afford downtime. One senior team, from the first commit to the 3 a.m. pager.
- You own every repo
- Senior engineers only
- 15-minute response SLA
99.98%Average uptime, managed platforms
−46%Median cloud spend cut, year one
12 minMedian time to restore service
140+Environments built and operated
Services
Everything between commit and customer
Take one practice, or the whole delivery path.
-
01
Software engineering
Greenfield web, API and data platforms, legacy modernisation and architecture review, built by the engineers who will also run it in production.
-
02
Deployment & delivery
CI/CD, GitOps, preview environments, canary and blue/green rollouts. Every commit gets a safe, reversible path to production.
-
03
Infrastructure & monitoring
Reliability assessment, infrastructure as code, SLOs and tracing, 24/7 on-call and incident command.
-
04
AI infrastructure
GPU capacity and build-vs-rent strategy, inference clusters and autoscaling, cost per thousand requests tracked like any other SLI.
-
05
Cloud, cost & compliance
Migration and data centre exit, FinOps, disaster recovery, ISO 27001 and SOC 2 readiness, secrets management.
How we work
Four phases. Fixed checkpoints. No surprise invoices.
The same shape whether it runs six weeks or three years.
Phase 02
Architect
Target state designed with your team and written down. Nothing lives in someone's head.
Decision records · Migration plan
Phase 03
Automate
Code, pipelines, policies and dashboards, shipped incrementally. Nothing hand-clicked.
IaC · CI/CD · SLOs · Runbooks
Phase 04
Operate
We run it with you, or hand it over completely. Documented exit path from day one.
24/7 cover · Monthly reporting
Outcomes
What the last engagements moved
Fintech, commerce and applied AI. Names withheld on request.
Cloud spend, traffic tripled
Cost was scaling faster than revenue. Right-sized compute, batch work to spot, budget alerts in front of every team. $1.9M annual saving in 14 weeks.
Lead time, down from nine days
Deployments took four hours and a war room. GitOps, canary rollouts and preview environments took the retailer from fortnightly releases to 300 a week.
Inference throughput, same budget
The team was renting far more GPU than it used. Batching, caching and scale-to-zero cut cost per thousand requests from $1.04 to $0.31.
Insights
Notes from production
What we learned running other people's systems. Read all
21 Aug 2026
The three numbers that decide what your inference costs
Cost per thousand requests is an SLI. Batching, utilisation and the tail of your latency distribution set it, and most teams are only watching one of them.
05 Aug 2026
Cutting cloud spend, in the order that actually works
Most cost programmes start with reserved instances and stall. The savings are real but they are last, not first. Here is the sequence we use and why.
14 Jul 2026
What a reliability assessment actually looks at
Two weeks inside a production system, and the eight questions that decide the score. Most of them are not about the infrastructure.
Questions
What teams ask before the first call
The short answers. The long ones are on services.
What does p10node do?
p10node builds software, ships it and runs it. One senior team covers software engineering, CI/CD and delivery, infrastructure and monitoring, AI infrastructure, and cloud cost and compliance work - from the first commit to the 3 a.m. pager.
Who is p10node for?
Teams that cannot afford downtime: fintech, commerce and applied AI companies across South-East Asia, Europe and Australia. You can take a single practice or the whole delivery path.
Where is p10node based, and when are you available?
Hanoi and Ho Chi Minh City in Vietnam, working follow-the-sun. Incidents are answered around the clock with a 15-minute response SLA; ordinary enquiries get a reply within one business day. We work in English and Vietnamese.
How are engagements priced?
A fixed monthly figure agreed up front, with no hourly surprises. Retainers run monthly and either side can end one with 30 days' written notice.
Who owns the code and infrastructure you build?
You do, from the first commit. The work happens in your repositories and your cloud accounts, and every engagement has a written exit plan from day one.
How does an engagement start?
With a two-week reliability assessment: two weeks inside your systems scoring architecture, delivery flow, cost and risk, ending in a written report and a prioritised roadmap your own team could run without us.
Do you work on AI and GPU infrastructure?
Yes. GPU capacity planning and build-versus-rent strategy, inference clusters and autoscaling, RAG and vector store architecture, and cost per thousand requests tracked as an SLI like any other.
What results have you delivered?
Across the platforms we manage: 99.98% average uptime, a median 12 minutes to restore service, and a median 46% cut in cloud spend in the first year, over 140+ environments built and operated.
Tell us what is breaking, or what you want to build.
A short note reaches an engineer, not a sales sequence. Reply within one business day.