Technologies we work in
We hold no vendor partnerships, resell nothing and take no commissions. These pages therefore say where each platform is a poor fit as readily as where it is a good one, because that is the only reason an independent view of technology is worth reading.
Cloud platforms
Each page covers architecture, practices, security, scalability, performance, integration, operations and governance — and where the platform is the wrong choice.
Microsoft Azure
Landing zones, identity, and the Azure services an enterprise estate actually runs on.
AWS
Multi-account landing zones, managed services and migration patterns.
Google Cloud
Data and analytics-led workloads, and GKE where container operations matter.
Microsoft Platform
Entra ID, Microsoft 365, Dynamics, Power Platform and SQL Server as an integrated estate.
How we choose between them
Four questions, in this order. Most selection processes answer them in the reverse order and arrive somewhere they later regret.
What is the problem, precisely?
A technology choice made before the problem is stated precisely is a preference. Most of the difficulty in selection comes from a requirement that was never written down clearly enough to discriminate between candidates.
What are the non-functional requirements?
Latency, throughput, availability, consistency and recovery objectives eliminate more options than feature comparison ever does — but only when they are stated as numbers rather than as adjectives.
Who will operate it?
A technically superior option your team cannot operate is not superior in any sense that matters. Hiring depth, existing knowledge and the operational burden are part of the choice, not a consideration after it.
What does it cost to keep?
Every runtime, framework and datastore carries a continuing cost in patching, monitoring, upgrading and hiring. That cost is paid for years and is almost never counted at the point of adoption.
Where sector decides the answer
The constraints that most often settle a technology choice come from the industry rather than from the technology.
Healthcare
Interoperability between clinical systems, patient data privacy, and legacy platforms that cannot be taken offline.
Banking & Financial Services
Core system modernisation, real-time payment flows, and architecture that can evidence regulatory controls.
Insurance
Claims and policy administration on ageing platforms, and data trapped in systems never designed to talk to each other.
Retail & E-commerce
Traffic that is seasonal rather than steady, omnichannel inventory accuracy, and catalogue scale.
Manufacturing
Operational technology meeting information technology, supply chain visibility, and ERP estates grown by accretion.
Logistics
Real-time tracking, partner system integration, and routing systems where latency has a direct cost.
Education
Student information systems, hybrid delivery platforms and sharply seasonal load.
Government & Public Sector
Procurement constraints, data residency, accessibility obligations and long-lived legacy estates.
Telecommunications
OSS/BSS complexity, network-scale data volumes and availability expectations measured in minutes per year.
Energy & Utilities
Grid and asset telemetry, regulatory reporting, and operational systems that cannot tolerate an outage window.
Services that apply these
Technology is how the work is delivered. These are the engagements it is delivered within.
Enterprise Architecture
Target-state design, modernisation roadmaps, integration and cloud architecture, and the governance that keeps decisions consistent after the consultants leave.
Cloud Consulting
Migration strategy, landing-zone design, cost modelling and the architecture decisions that determine whether cloud spend buys capability.
Digital Transformation
Technology roadmaps and operating-model advisory for organisations changing how they build and run software.
Software Development
Custom application, web, mobile and API development, and modernisation of systems that are constraining the business.
DevOps & Platform Engineering
Delivery pipelines, infrastructure as code, Kubernetes and the observability practices that make releases routine.
AI & Data Engineering
Data architecture, platform modernisation, integration and analytics — the foundations that have to exist before AI is a sensible conversation.
Cybersecurity
Security architecture, assessment and compliance advisory, designed in rather than reviewed afterwards.
Managed IT Services
Application support, infrastructure management and incident response under defined service levels.
QA & Test Automation
Test strategy, automation and performance testing, so quality is measured continuously rather than discovered late.
ERP & Business Applications
ERP implementation advisory, integration into the wider estate, and business process automation.
Frequently asked questions
The one that fits the problem, the constraints and the team that will operate it — in that order. We hold no vendor partnerships, resell nothing and take no commissions, so a recommendation to use less technology, or to keep what you have, costs us nothing to make.
None, with any vendor. That is a deliberate position rather than an oversight. It means we earn nothing from your platform choice and that our recommendation is worth exactly what the analysis behind it is worth.
Frequently yes. These eleven are the platforms we are asked about most often, not a restriction. Most architecture, data and delivery problems are not language-specific, and we will say plainly when a stack is one we would need to learn from your team.
For most organisations, mostly yes. Every additional runtime, framework and datastore carries an operational cost — hiring, patching, monitoring, upgrading — that is paid continuously and is rarely counted when it is adopted. The exceptions should be deliberate and few.
Against the problem, the non-functional requirements, the operating model and the team's actual capability. A technically superior option your team cannot operate is not superior in any sense that matters, and that judgement is where most selection processes go wrong.
Rarely on its own. Maturity brings documentation, hiring depth, operational knowledge and a long tail of solved problems, all of which have real value. We are biased toward boring technology for anything with a long operating horizon, and we will say when that bias should be overridden.
Usually, and usually we recommend it. Migration is expensive and rarely the actual constraint — the problems are more often architectural, and those are fixable without changing the language or the platform.
We describe practices rather than credentials and do not represent NG&NR as holding certifications it has not been awarded. What we can offer is the reasoning, which you can evaluate directly during the first consultation.
The service pages describe what we do; these describe the platforms we do it on, including where each is a poor fit. The industry pages describe the constraints that usually decide between them.
No. Pricing is transparent, published and includes GST, and it does not vary by stack. What varies is scope, because some estates require more discovery before anything can be recommended honestly.
Next step
Talk to an architect about a technology decision
A free first consultation covering the problem, the constraints that actually discriminate between options, and an honest view of whether a change is warranted at all.
No cost, no obligation. Pricing is transparent and includes GST.