Noble Platforms
Products Noble owns, not projects Noble delivered.
Alongside the client work, Noble develops and owns technology platforms. They are built by the same engineering, data and AI teams that deliver for clients, and they carry Noble’s name rather than a client’s.
A platform listed here is a Noble product. It is not a physical product from the catalogue, not a service, and not work delivered for a client — client digital work is kept separate, under Digital Experiences.
The platforms
Three, each with its own page. Each is being prepared for public release, and each page says exactly that until there is more to say.
Why a services company builds products
Because a product is the honest test of an engineering organisation. Client work is delivered, accepted and handed over; a product Noble owns has to keep running, keep being maintained, and keep being worth using after the enthusiasm of the first release has gone. The decisions that survive that are the ones worth taking on a client’s system.
It also means the platform work and the delivery work share the same standards. Bilingual composition, accessibility, an evaluation set before deployment, a defined path when a model is wrong — those apply to Noble’s own products first, where the cost of getting them wrong lands on Noble.
The services behind them
The same four that would build the equivalent system for a client.
- Software & Web EngineeringThe application itself — architecture, interface, APIs, delivery pipeline and the operations that follow the release.
- AI & Machine LearningRetrieval, evaluation, model selection, and the governance around what a model may read and how its answers are checked.
- Data & AnalyticsThe layer a product’s intelligence stands on. A platform that cannot reconcile its own numbers cannot report on them.
- CloudWhere a product runs, what it costs per tenant, and which region its customers’ data is allowed to sit in.