Dark theme
WELCOME TO QQUANTUM

Let Qubi show you around.

Choose how you’d like to explore.

Don’t agreeGo to yourOS instead ↗

Both choices allow Google Analytics, so we can see which pages help.

Sound is your choice. Essential cookies keep the site working. Continuing either way also allows Google Analytics (visits and pages viewed).

Read our Terms, Privacy and Cookies.

Change your choices anytime from the footer.

Getting Qubi ready.
Trust

The model supply chain.
Vetting what you import.

Every organisation deploying AI is deploying an artefact produced by someone else, from data they cannot inspect, by a process they cannot audit. That is uncomfortable and it is also the normal condition of every dependency you already ship.

All Trust & Security →
Pixel illustration for Model Supply Chain: a sealed component crate with provenance cards.

What can and cannot be assured

Start with the honest boundary, because a framework that promises more than it delivers is worse than none. For frontier-class models you cannot audit training data — open or closed, of any origin. A handful of fully open research models publish their data; none of the frontier models do. Anyone offering that assurance for a frontier model is describing something that does not exist. If your threat model genuinely requires provenance of training data, no current model satisfies it and the conversation is about whether to deploy at all.

What you can do is substantial and is what a defensible assessment consists of: pin a specific artefact and verify its hash; know who produced it and under what licence; test its behaviour against your own material including the cases you are worried about; control where it runs and what it can reach; and detect if any of that changes. That is a real assurance posture and it is typically achievable in a couple of weeks.

The assessment

01

Provenance

Who trained it, in which jurisdiction, under what corporate control. Which exact version and weights file, verified by hash. Where you obtained it and whether that source is authoritative — a model downloaded from an unofficial mirror is an unverified binary from the internet.
02

Licence

What the terms permit: commercial use, modification, fine-tuning, distillation, redistribution, embedding in a product you sell. Whether any thresholds or attribution obligations apply. Recorded against the deployment, not just read once.
03

Behaviour

Tested on your own material, including the topics you are concerned about. Every aligned model has behavioural characteristics reflecting its training and its origin; the question is whether they matter for your workload, and that is an empirical question you can settle.
04

Operation

Who runs the endpoint. For a hosted model this is a third-party processor assessment. For self-hosted weights it is you, which is a materially different and usually simpler review — and it is the distinction most often blurred in vendor conversations.
05

Containment

What the model can reach: network access, tool permissions, data scope. A model is not trusted code; it is an untrusted component whose outputs are constrained by the layer around it. Containment is where assurance is actually implemented.
06

Change detection

If you self-host, the artefact does not change unless you change it — which is a genuine assurance advantage. If you use a hosted model, behaviour can shift within a version, and a continuously running evaluation set is the only way you will notice.

The country-of-origin question

This usually arrives about models of Chinese origin and it deserves a structured answer rather than either dismissal or alarm. Separate it into three, because they have different answers.

Data transfer — closed completely by self-hosting. Weights are a file; they transmit nothing, and on an isolated network they could not — provided you also review any code shipped alongside them. This is the question people most often mean and the one most easily resolved.

Behaviour — testable on your own material, and workload-dependent. Every model from every jurisdiction has been aligned by someone with a view; the differences are measurable and for most business tasks immaterial. Test rather than assume, in either direction.

The artefact itself — partially assurable, as set out above, and no more or less so than for any other model. This is where the honest answer is uncomfortable and where it is identical regardless of origin.

And where an organisation has a standing policy on model origin, that policy is the answer. It is a governance decision owned by people who own the risk, and our job is to build within it rather than to argue against it.

Questions

Questions about Model Supply Chain.

Is an open-weight model riskier than a hosted one?

Different risks, and for regulated organisations often lower overall. You take on verifying and operating the artefact; you remove a third-party processor from the data path entirely and gain the ability to pin a version indefinitely. Which trade is better depends on your risk register, and both are defensible.

Should we require a model bill of materials?

Ask for it — some providers publish useful documentation of architecture, data sources and evaluations. Do not expect it to be complete or verifiable for any frontier-class model, and do not build a control that depends on it being so.

How do we document this for an auditor?

A short record per deployed model: version and hash, source, licence, behavioural tests run and their results, where it runs, what it can reach, and who approved it. Two pages, updated on change. It takes about an afternoon and it is what turns a defensible decision into an evidenced one.

Two pages,
one afternoon.

A documented model assessment is what turns a defensible decision into an evidenced one. We produce it as part of the build.

30-minute technical call · no deck

Shipped & in build

Real work. Check it yourself.

What we built, what stage it is at, and a link to the live thing wherever there is one.

The updated yourOS homepage: Roxy’s open ring surrounded by bento cards for calls, voice, translation, building, design, apps and more.
The yourOS homepage on a phone, with its compact navigation, welcome film button and bento cards.
youros.tech — the homepage bento hero
Our own · coming soon

yourOS

yourOS is an operating system with an AI at its heart. You talk to it like a person, out loud or typed. It makes your calls, plans your days and works on your projects with a crew of agents, on your own private server. Our own product, built from the first commit; the waitlist is open.

What we built
  • Operating system
  • Roxy
  • Agent crew
  • Voice calls
  • App store
  • Website
Meet yourOS →
The Sonora homepage on desktop: a full-bleed dune landscape behind the headline “Transform Your Life with Sound”, with App Store and Google Play download buttons.
The Sonora homepage on a mobile viewport, showing the same hero reflowed to a single column.
sonora.com — homepage, 1440×900
Live · iOS · Android

Sonora

Website, backend and app assets for Sonora, a free AI sound-therapy app on iOS and Android published by Cognitive AI.

What we built
  • Website
  • Backend
  • App assets
Read the case study →
The updated Podswap homepage on desktop: “Grow on Instagram and TikTok for free, with real engagement from creators your size”, beside a tilted wall of exchange, tool and guide cards on a violet gradient.
The updated Podswap homepage on a phone, with its floating navigation, Instagram and TikTok engagement headline and tilted tool cards.
podswap.app — homepage, 1440×900
Five platforms

Podswap

Brand, website, prototype, apps on five platforms, the AI backend and the algorithm-intelligence pipeline for Podswap, a social growth engine that runs without a human in the loop.

What we built
  • Brand
  • Website
  • Prototype
  • Apps on five platforms
  • AI backend
  • Algorithm pipeline
Read the case study →
The unOpen.AI homepage introducing Roxy, a private AI assistant that remembers who you are.
The unOpen.AI homepage on a mobile viewport.
unopen.ai — homepage, 1440×900
Prototype · closed beta

unOpen.AI

In closed beta: Roxy, a private AI assistant with permanent memory running on infrastructure the user owns. Brand, site, product, backend and conversational design.

What we built
  • Brand
  • Site
  • Product
  • Backend
  • Conversational design
Read the case study →
coherence.com on desktop, headed "Intelligence that moves in phase with people".
coherence.com on a mobile viewport, reflowed to a single column.
coherence.com — homepage, 1440×900
Live

Coherence

Live at coherence.com: brand identity generated with AI agents we directed, the motion system and website for the group behind Sonora, AboutAI, WakeUp and MudShadows. Agent work remains in build.

What we built
  • Brand identity
  • Motion system
  • Live website
  • Agent work — in build
Read the case study →
The new Domain Booth homepage on desktop: the headline “Premium Domains. Serious Buyers. Proven Results.” beside the animated DB monogram.
The new Domain Booth homepage on a phone, reflowed to a single column.
Our build of the Domain Booth homepage — 1440×900
Live

Domain Booth

Live at domainbooth.com for DomainBooth, a premium domain brokerage: a new animated mark, every page redesigned and rebuilt with designed mobile layouts, and a custom CMS for its sales record, featured names, press and enquiries.

What we built
  • Animated mark
  • Every page redesigned
  • Designed mobile layouts
  • Custom CMS
Read the case study →
Who we have built for

Twenty-one years. Names you know.

Apps, platforms and campaigns for these teams, long before the AI work. Every one is written up on the work page — what we did, and where our part ended.

See all of our work →
  • BBC Good Food logo
  • Charities Aid Foundation logo
  • GAME logo
  • NatWest logo
  • Next logo
  • NSPCC logo
  • Tesco logo
  • Worldpay logo
  • Samsung logo
  • Sony logo
  • Land Rover logo
  • UAP Limited logo
  • Netflix logo
  • Amazon Prime Video logo
  • Mercedes-Benz dealerships logo
  • San Miguel logo
  • Biovene Barcelona logo
  • Seventy7 logo
  • Littlewoods logo
  • Smile logo
  • The Co-operative Bank logo