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

Copenhagen.
Documents and sensors.

We are based in Barcelona and work on your hours exactly. Copenhagen is unusual among European cities in that the two hardest kinds of industrial data are equally present here: paper that moves goods across borders, and telemetry from assets standing in the North Sea. They are not the same problem and they should not be the same system.

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

What is actually different here

01

Two data shapes, one city

A Copenhagen group will often own both a document estate — bills of lading, customs declarations, certificates, regulatory dossiers — and a time-series estate coming off vessels, turbines and production lines. Language models are good at the first and largely irrelevant to the second, where the useful work is anomaly detection and forecasting with a language layer only at the point a human reads the result. Selling one platform for both is the most common way this goes wrong, and we will argue against it even when it costs us scope.
02

No Danish region, and it barely matters

At the time of writing the major providers have no Danish cloud region: the nearest are in Sweden and Germany. Both are EU, so jurisdictionally nothing changes, and the latency across the Øresund is not a problem for anything we would build. It is worth checking whether your own contracts say Denmark or say the EU, because those are different requirements and only one of them is expensive. If it genuinely says Denmark, the route is self-hosting on Danish infrastructure and we will price that honestly.
03

Shipping data is cross-border by definition

Datatilsynet supervises data protection under the standard GDPR, which is the simple part. The complication in this city is structural: a single shipment involves shippers, forwarders, customs authorities, ports and consignees across several jurisdictions, some well outside the EEA, and the documents carry named individuals. The transfer question here is not theoretical and it is not solved by a region setting. It is solved by deciding what leaves your perimeter, which is a design decision made early or a problem discovered late.
04

Life-science documentation has its own gravity

Danish pharmaceutical and biotech work answers to documentation standards that were strict long before anyone here had an AI question. What that means practically is that a summary without a traceable citation is not a lesser deliverable, it is an unusable one. The requirement is retrieval you can follow back to the source paragraph, and that is a design constraint we would rather accept at the start than negotiate at validation.

The work that comes out of this city

  • Shipping and logistics

    is the sector that defines Copenhagen commercially, and it produces the most reliably valuable document work in Europe. A freight operation handles enormous volumes of semi-structured paper that arrives in every possible condition — emailed, scanned crookedly, photographed, in several languages, occasionally handwritten. Extracting it correctly is worth real money per document, and the engineering that decides success is the exception path rather than the happy path. Our logistics document pipeline is that pattern written down, and the wider sector view sits under logistics.
  • Pharmaceuticals and biotech

    arrive with the opposite tolerance for error. The valuable systems here read across regulatory submissions, study reports and internal literature and answer a specific question with the paragraph it came from, so a scientist can verify it in seconds. Fluency is not the requirement; verifiability is. That is what we build under life sciences research.
  • Renewables and wind

    bring the sensor half of the city. Turbines generate continuous condition data, and the commercial question — should this asset be serviced now or in six weeks — is a forecasting problem with a maintenance-history document problem attached to it. The two halves are usually owned by different teams and stored in different systems, which is most of why this work is hard. The approach is described under predictive maintenance.
  • Design and consumer brands

    bring a smaller but cleaner problem: large product catalogues sold across many markets, where search, translation quality and merchandising decide conversion. It is the least regulated work we do in the city and often the fastest to show a result.

How a copenhagen project actually runs

01

We come up for discovery, often twice over

Barcelona to Copenhagen is a direct flight of about two and a half hours. Where both halves of the estate are in scope, the document people and the asset people are usually in different buildings and sometimes different towns, and the first workshop has to reach both — so we plan discovery around two sites rather than one meeting room. On a normal engagement we do not bill the travel as a line item.
02

Then remote, same hours all year

Denmark and Spain keep the same clock, including the daylight-saving switch, so a question asked in a morning standup is answered the same morning. Nothing about the schedule needs converting.
03

And back for handover to the people on the line

The ownership session goes to your engineers, and for a document pipeline we also run it with the operations team who will see the exceptions, because they are the ones who decide whether the system is trusted. After that it is yours, in your repositories and your cloud accounts.
Questions

Questions about Copenhagen AI Engineering.

Do you have a Copenhagen office?

No. We have one office and it is in Barcelona. We travel to Copenhagen for discovery, for handover and for anything where being in the room changes the outcome. There is no Danish entity and no Nordic partner behind us.

Can our data stay in Denmark?

In the EU, straightforwardly. In Denmark specifically, not with a major provider region at the time of writing — the nearest are in Sweden and Germany, both EU, which satisfies most requirements that are actually written down. Where a policy genuinely names Denmark, the route is a self-hosted open-weight model on Danish infrastructure, and that is a larger build we would price rather than approximate. Where a hosted model is used we document its retention and training terms at the time of writing, and you should confirm them against the provider's current terms.

Do you do the sensor side as well as the documents?

Yes, but not with the same tools, and this is the answer we most often have to defend. Condition monitoring and forecasting on time-series data is classical machine learning and signal work; a language model belongs at the end of it, turning a result into something a planner can read, and sometimes not at all. If you have been quoted a single AI platform covering both, ask what model is reading the vibration data and what it was trained on.

Our shipping documents involve parties outside the EU. Is that a problem?

It is a question rather than a problem, and it needs answering in the architecture rather than in the contract alone. In practice we design so the extraction runs inside your perimeter and only the structured result — often with the personal data already dropped, because a customs line item does not need a name — moves onward. That removes most of the transfer surface without changing what the business gets. Your DPO owns the legal analysis; our job is to make it a short one.

What does a Copenhagen engagement cost?

The same as anywhere else — the ranges are on the pricing page, in euros and exclusive of VAT. We do not price by postcode. A project covering both the document estate and the asset estate is two systems and is estimated as two.

In Copenhagen and
building something?

Thirty minutes on the problem, and an honest read on whether we are the right team for it.

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