What we do
01  Advanced Infrastructure 02  Applied AI & Data 03  AI Cybersecurity 04  AI Assurance
Engagements
AI estate inventory Assurance review
Industries
Financial Services Government & Public Sector Energy & Utilities Telecommunications Healthcare & Life Sciences Transport & Logistics Industrial & Manufacturing Retail, Hospitality & Real Estate
Research
The Trust Maturity Model The GCC Assurance Index Readiness self-assessment Case studies Perspectives Sector briefings Technology evaluations
Company
About us Partners Events Careers Contact العربية Talk to our team
What we do  ·  Advanced Infrastructure

Four contracts. One gap nobody owns.

Residency, recovery, reachability and exit are written as clauses in four separate contracts and broken in the gaps between them. We assess the estate as one architecture — and we sell you none of the parts.

4–6 WEEKSWRITTEN REQUIREMENTS, NOT A SHORTLISTWE ASSESS · PARTNERS DELIVER
Why this pillar exists

Infrastructure is bought in layers and fails across them.

Every organisation of scale has a competent network team, a competent storage team and a competent identity team. What it usually does not have is one person who can answer a requirement that touches all three.

01

The requirement is nobody’s

A residency obligation is written by legal, implemented by storage, and quietly undone by a network re-route. Each team did its job correctly.

02

The supplier assesses to what it supplies

A carrier scopes the requirement against its transport. An integrator against its implementation. Both are competent; neither is neutral.

03

The test is run on the wrong day

Resilience is tested against hardware failure, which almost everything survives, and never against exit, which almost nothing does.

What we assess

Four requirements. Six layers. None of them stays put.

Infrastructure is bought one layer at a time and examined one requirement at a time, and the two never line up. Choose a requirement and watch how far it reaches.

CONTROL PLANE
LAYER 01

Identity

Who is allowed to be here at all
LAYER 02

Network

How anything reaches anything else
EXECUTION
LAYER 03

Compute

Where processing physically happens
LAYER 04

Storage

Where the copies come to rest
OUTCOME
LAYER 05

Data

What is in scope, and on what basis
LAYER 06

Exit

What it would cost to leave
REQUIREMENT— OF 6 LAYERS TOUCHED
Select a requirement

Six layers of an estate, grouped by what they actually control. A requirement is written against one of them and lives in several.

TOUCHEDNOT IN SCOPE

This is why a layer-by-layer purchase produces a requirement nobody owns. Each of these was somebody’s clause in somebody’s contract, and the gap between them is where the estate actually fails.

Advanced Infrastructure

Three ways in.

Three engagements, sold independently and architected as one. Start with the question you can name.

The boundary

We design it. We do not run it.

Three moves. Two of them are ours, and the one in the middle deliberately is not.

MOVE 01 — OURS

Assess and specify

We walk the estate, write the requirements the infrastructure has to meet, and sequence the path to get there. The requirement is written before any product is considered.

MOVE 02 — NOT OURS

You contract directly

You hold the contract with the provider or carrier. No margin passes through us, and no lock-in passes through us either. This is the move that makes the other two believable.

MOVE 03 — OURS

Re-test on a cycle

We return and check the estate against the same questions — including whether the thing you bought did what it was specified to do.

Because we carry nothing and resell nothing in this pillar, no recommendation we make depends on which platform you choose.
How we engage

Defined engagements with a deliverable at the end.

Every engagement in this pillar is scoped, fixed-fee and finishes with something you can put in front of somebody else.

TYPICAL DURATION
4–6 weeks per service
DELIVERABLE
Written requirements and a sequenced path
DELIVERED
Remotely, workshops where required
INDICATIVE FEE
[FEE BAND — pending sign-off]
Questions we are asked

Before you ask us.

Does Orvix supply infrastructure?
No. In this pillar Orvix assesses and specifies; delivery, capacity and operation are contracted directly between you and a provider under their own licensing. We carry no traffic, hold no data and take no margin on what you buy.
Which of the three should we start with?
If you can name the layer that worries you, start there — Network as a Service or Storage & Resilience. If the concern is a requirement rather than a layer, or if the last two answers you got contradicted each other, start with Infrastructure Design.
Can this run alongside an incumbent integrator?
Yes, and it usually does. We are assessing a requirement, not competing for the implementation. Where an incumbent has done good work, the report says so, and that is a more useful outcome for you than a finding we had to manufacture.

Start with the requirement, not the layer.

Thirty minutes. Bring the obligation you are least able to evidence and we will tell you which layers it actually reaches.

Book a 30-minute scoping call

ORVIX · INDEPENDENT AI & TECHNOLOGY ASSURANCE · WE DISCLOSE EVERY COMMERCIAL RELATIONSHIP ON THE PAGE FOR THE SERVICE IT BELONGS TO. WHERE LICENSING IS REQUIRED, DELIVERY IS PERFORMED BY NAMED PARTNERS UNDER THEIR OWN LICENCE.