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.
Lyon

Lyon AI engineering.
Pharma and biotech.

Lyon is a working city rather than a headquarters city, and the AI problems reflect that. They arrive from people who make things — vaccines, molecules, components, deliveries — and who have a document trail behind every one of them that somebody has to read, check and keep for a very long time.

  • Worked from Barcelona
  • EU · CNIL
  • Same hour as us
Last reviewed 5 September 2026 · Engineering guidance, not legal advice.
All Where We Work →
Pixel illustration for Lyon AI Engineering: a destination postcard for Lyon, with an illustrative city silhouette and a travel route.

What is actually different here

01

One authority for the whole country

France has a single national supervisory authority, the CNIL, so a company in Lyon answers to exactly the same body, the same guidance and the same published AI recommendations as one in Paris. There is no regional variation to design around — unlike Germany, where the answer depends on which Land you are established in. It makes the governance conversation shorter and more predictable.
02

The nearest region is in Paris

There is no Lyon cloud region, and there does not need to be. AWS eu-west-3 sits in Paris, which is French soil and a few milliseconds away over decent transit — irrelevant for a document pipeline and irrelevant for batch analysis. If the requirement is stricter than French soil, the answer is your own hardware, and for a plant that is often what people wanted anyway.
03

Regulated production changes the standard

Pharmaceutical and biotech manufacturing runs under good manufacturing practice, with the ANSM nationally and the EMA above it. In that setting an extraction that is usually right is a defect, not a feature: every value a system produces has to be traceable to the page it came from, and any change to the system is itself a documented event. That is a higher bar than most AI projects are built to, and it has to be in the design from the start.
04

Chemicals bring their own paperwork

The chemical corridor south of the city lives under REACH registrations, safety data sheets and classification rules, in several languages and several revisions. This is unusually good material for retrieval — it is structured, versioned and consequential — and unusually unforgiving, because citing a superseded revision of a safety data sheet is worse than returning nothing.

The work that comes out of this city

Lyon holds one of Europe's most concentrated life-sciences clusters, a chemical industry running down the Rhône, a broad manufacturing base, and the logistics that follows from sitting on the crossroads between northern Europe, Italy and the Mediterranean. Four industries, and in practice two kinds of project.

The first is document extraction where being wrong is expensive. Study reports, regulatory submissions, batch records, deviations, safety data sheets, supplier declarations. The naive version of this project — put the documents in a vector database and ask questions — produces a demonstration that impresses a steering committee and fails the first audit, because it cannot show where an answer came from and cannot say when it does not know. The version we build cites the page, refuses more often, and routes the uncertain cases to a named reviewer. That pattern is set out in clinical document intelligence, and the research-facing variant under life sciences research.

The second is operational: sensor histories, maintenance logs and quality records from plants that have been instrumented for longer than most software companies have existed. The data is there, the labelling usually is not, and the honest first step is often a month of establishing whether a signal exists at all before anyone commits to a model. Predictive maintenance and supply chain planning describe how those run.

Both kinds share a trait worth naming: the person who understands the data is a chemist, a QA lead or a scheduler rather than a data engineer, and the project succeeds or fails on how much of their time we get. We would rather have six hours with them than six weeks of documentation.

How a lyon project actually runs

01

We come to the site first

Lyon is a short hop from Barcelona by air and a straightforward run up the coast overland. For plant work the discovery visit is where the real requirements surface, usually from someone who was not invited to the meeting.
02

Remote, with no time difference

France and Spain sit on the same clock, so there is no offset to work around — no waiting for a window, no question parked until tomorrow. It removes an entire category of project friction.
03

Handover to your team

We finish with your engineers and your QA people operating the system themselves, including the parts that fail. Then it is yours, in your repositories and your infrastructure.
Questions

Questions about Lyon AI Engineering.

Do you have a Lyon office?

No. We have one office and it is in Barcelona. We travel to Lyon for discovery, for site visits and for handover. There is no local branch, no local partner and no local associate — if we say we will be at your plant, it is us.

Do we get a lesser team than a Paris client would?

No, and it is a fair thing to ask given how much French AI activity is concentrated in Paris. We are a small senior team and the people at the discovery workshop are the people who build the system. There is no bench to hand you off to, which is a limitation as much as a promise: if we are full, we will tell you.

Our documents are in French, English and sometimes German. Does that break retrieval?

It complicates it, and it is worth designing for explicitly rather than hoping. Mixed-language corpora need either a multilingual embedding model or per-language indexes, and the two behave differently when a French query should surface an English source. We test that case specifically, because it is the one that quietly fails and nobody notices for months.

Can the whole system run inside our plant?

Often, yes. Open-weight models have become good enough that extraction and analysis workloads can run on hardware in your own data centre with nothing leaving it, which is frequently what a validated environment wants anyway. The trade-off is that you own the GPUs, the capacity planning and the update cycle, and we will size those honestly rather than optimistically.

How do you price?

Published ranges on the pricing page, in euros and exclusive of VAT. The same for Lyon as for anywhere else — we do not price by postcode.

Documents piling up
somewhere in Lyon?

Thirty minutes on where they come from, who reads them now, and what would have to be true for a system to help.

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