Bureau theme
Model families

Qwen for
multilingual systems.

Qwen's distinguishing feature is range. It ships across one of the widest ranges of sizes of any open family, which means the same architecture and tokeniser can serve a phone, a single GPU and a multi-node cluster — and that consistency is worth more in a real system than it sounds.

SPECIFICATION
Provider
Alibaba Cloud, China
Weights
Published across the range
Licence
Predominantly Apache-2.0 across recent releases, with some exceptions — check the specific model card
Sizes
One of the widest ladders of any open family, from sub-1B up to large mixture-of-experts models
Strengths
Multilingual coverage including CJK, coding variants, and strong small models
Where we use it
Self-hosted multilingual work, and wherever a single family has to cover both an edge and a server deployment

Provider-published specifications as of 1 September 2026, not figures we measured. Model families move quickly — check the provider's own documentation before committing to a number.

WHY A SIZE LADDER MATTERS

Most production AI systems end up wanting more than one model. A small one for classification and routing, a mid-size one for the bulk of the work, a large one for the hard minority of requests. Assembling that from three different families means three tokenisers, three prompt idioms, three evaluation baselines and three sets of quirks to learn.

Qwen's range lets you build that ladder inside one family. Prompts transfer with far less rework, an evaluation harness written for one size largely holds for another, and when you move a request class from the mid-size model to the small one — which is where a great deal of cost saving actually comes from — you are changing a parameter rather than rewriting an integration.

The multilingual coverage is the second reason we reach for it. If your corpus contains Chinese, Japanese or Korean alongside European languages, this family has, in our evaluations, handled the mix better than Western-trained alternatives of comparable size, and the difference shows up immediately on a fair evaluation set rather than needing a subtle one.

THE PROVENANCE QUESTION, AGAIN

Qwen is developed by Alibaba, and the assessment is structurally the same one we set out on the DeepSeek page: separate the transfer question from the behaviour question from the artefact question. Self-hosting closes the first completely — the weights are a file and they transmit nothing. The second is testable on your own material and is workload-dependent. The third is only partially answerable, for every model from every jurisdiction.

Where an organisation has a standing policy against models of Chinese origin, that policy is the answer and we build with Mistral or Llama, which occupy adjacent ground. It is a governance decision owned by people who own the risk, and it is not our place to argue anyone out of it.

WHERE WE WOULD CHOOSE SOMETHING ELSE

Where the deployment is a single size on a single class of hardware, the size ladder stops being an advantage and the decision comes down to capability and tooling on that one rung — which is frequently where Llama's deeper serving ecosystem wins.

Where the workload is at the hardest end of agentic or reasoning work, the leading proprietary models still lead, and a hybrid arrangement that routes that minority out is usually better than choosing one family for everything. See hybrid model routing.

QUESTIONS
QUESTIONS — 3

At most sizes, yes — and its small models in particular are strong relative to their footprint, which is exactly where a lot of production value sits. As always the comparison that matters is on your task, and we run it rather than argue about it.

The lower rungs of the ladder run comfortably on a single accelerator, and the smallest run on a CPU at usable speeds for batch work. That makes them a realistic option for edge deployments and for on-premise setups where a full GPU node is not justified.

Write it down before you build. Record which model and version you deployed, where it runs, what the licence permits, what evaluation you ran on sensitive-topic behaviour, and who signed it off. That record is what turns a defensible decision into an evidenced one, and it takes an afternoon.

Keep reading
30-minute technical call · no deck

One family,
every size.

We will build the routing ladder and show you what moves down a rung without losing quality.

CASE STUDIES

Shipped work.
Go and check it.

The work we can name, with the live site, our scope and the boundary made explicit. Select a project to see the evidence; each is a full case study, not a logo or a claim.

sonora.com
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.
sonora.com — homepage, 1440×900 sonora.com →
Live Consumer wellness · Mobile + web

Sonora

Cognitive AI Ltd · 2026

A free sound-wellness app, described by its publisher as AI sound therapy that reads a short vocal sample at the start of a session and generates a soundscape for that moment. We designed and built the website and its backend, produced assets for the iOS and Android apps, and supported the application prototype.

Read the case study →

See every published project →

WHO WE HAVE BUILT FOR

Twenty-one years of applications, platforms and campaigns for names you know.

See all of our work →