For European clients, Mistral frequently resolves a conversation that has nothing to do with benchmarks: the provider is EU-domiciled, several releases carry a standard permissive licence, and the weights can run inside your own building.
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.
On the hardest reasoning and coding tasks, the largest frontier models still lead. Where a workload genuinely sits at that ceiling — complex multi-step agentic work, difficult code generation — you will feel the difference, and choosing Mistral there for jurisdictional reasons is a trade you should make consciously rather than discover in production.
The licence position is not uniform across the family. Assuming everything is Apache-2.0 because one well-known release is has caught out teams before. Read the model card for the specific model you intend to deploy, and record which one you chose, because that record is what a future audit will ask for.
And EU domicile is not the same as compliance. It removes the transfer question; it does not remove your obligations around lawful basis, purpose limitation, retention or subject rights. Those still need designing into the system. See GDPR and EU data residency.
No. It removes the international transfer question, which is often the hardest single obstacle, but lawful basis, purpose limitation, retention, subject access and the record of processing all remain yours to design. A model provider cannot be compliant on your behalf, and any vendor implying otherwise is describing a product that does not exist.
It varies by release and it changes, so we check the model card at selection time rather than working from memory — and we write the answer into the architecture decision record, because “which licence did we deploy under” is a question that gets asked eighteen months later by someone who was not in the room.
If the licence or the EU-provider question is live, Mistral. If tooling depth and the widest possible body of operational experience matter more, Llama. On raw capability at comparable sizes they trade places release by release, which is a good reason to build the system so the model is swappable.
EU-domiciled models, EU hosting, or your own hardware. We will tell you which one your constraints actually require.
30-minute technical call · no deck
What we built, what stage it is at, and a link to the live thing wherever there is one.
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.
Website, backend and app assets for Sonora, a free AI sound-therapy app on iOS and Android published by Cognitive AI.
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.
In closed beta: Roxy, a private AI assistant with permanent memory running on infrastructure the user owns. Brand, site, product, backend and conversational design.
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.
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.
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.
