RadixiaRadixia

How delivery works

Four stages, and what you receive at each one.

01

Assess

Use-case map and architecture assessment

Whether the use case suits AI at all, and which model and architecture fit it.

02

Decide

Decision memo, with the recommended next step

Build, buy, or open source, judged on measured cost, latency and risk rather than on a feature list.

Stop. Do not build this.

This stage can end the engagement. If the answer is that the use case should not exist, you get that in writing, with the reason and what to do instead.

03

Validate

Evaluation plan and a measured prototype

Whether it is safe to put in production, against criteria agreed before the prototype was built.

04

Deliver

Integration and oversight plan, including a local or air-gapped option

Who owns what. Delivery is direct, with named specialist partners, or alongside your own team.

Not provided24/7 operations · managed services · generic staffing

Who delivers, and where

We stay responsible for architecture, validation and technical direction through to production. The building happens in one of three ways: directly by us, together with named specialist partners, or alongside your own engineering team. Which one applies is agreed and written down before work starts.

Depending on requirements, we work across open-source platforms, on-premises and air-gapped environments, and selected cloud services. We are a Huawei Cloud reseller, which is the only reason that one is named here: it is an option we can deliver directly, not a preference we bring to a decision.