Foundry theme
Valencia Worked from Barcelona EU · AEPD Same hour, same coast

Valencia.
Port and agrifood AI.

Everything that moves through this city leaves a document behind it. A container arrives with a bill of lading, a packing list, a phytosanitary certificate and a customs declaration, each issued by a different party in a different format, and each read by a person under time pressure. Valencia produces the most concrete AI problems we see anywhere.

Last reviewed 5 September 2026 · Engineering guidance, not legal advice.
WHAT IS ACTUALLY DIFFERENT HERE
01

One regime, ours and yours

Valencia and Barcelona sit under the same GDPR, the same LOPDGDD and the same supervisory authority, the AEPD. Nothing crosses a border when we work together, so there is no transfer mechanism to paper and no third-country analysis to revisit later. In logistics that matters more than usual, because your counterparties frequently are outside the EU and that is where the real analysis belongs.
02

Spanish hosting, close by

AWS eu-south-2 puts a full region on Spanish soil, so keeping shipping documents, customer records and model inference inside the country is a configuration choice rather than a negotiation. For anything that must not touch a public cloud at all, open-weight models running on your own hardware are now a serious option instead of a compromise.
03

Customs rules define the data

Freight work runs on the Union Customs Code and the declaration systems that implement it, plus the AEAT on the Spanish side. The consequence for a system design is that the target format is fixed and public: you are not inventing a schema, you are populating one that already exists and that rejects malformed input. That is unusually good news — it gives an extraction pipeline a hard, checkable definition of correct.
04

Agrifood adds traceability

Food and produce businesses carry EU traceability and food-safety obligations that require knowing where a lot came from and where it went, at speed, when something goes wrong. That is a data-lineage problem wearing a compliance hat, and it usually reveals that the records exist but live in four systems that do not agree on what a lot number is.
THE WORK THAT COMES OUT OF THIS CITY

Valencia has one of the busiest container ports in the Mediterranean, an agrifood industry that feeds a good part of Europe, the ceramics cluster up the coast around Castellón, and a startup scene that has grown quickly enough to change the character of the city. Four very different clients, and three recognisable projects.

Freight and forwarding companies come with document volume. Bills of lading, arrival notices, certificates of origin, packing lists — arriving as PDFs, as scans, as photographs taken on a phone at a loading bay, and increasingly as structured messages that nonetheless disagree with the paperwork. The engineering that matters is reconciliation and escalation rather than extraction alone: what the system does when the weight on the packing list does not match the weight on the declaration. Our logistics document pipeline is exactly this problem written down.

Agrifood and produce exporters bring forecasting under conditions that make forecasting hard: a perishable product, a growing season, weather, and a customer base that reorders erratically. The honest engagement here begins by establishing whether the historical data can support a forecast at all before anyone builds one — see demand forecasting. Sometimes the answer is no, and saying so early is worth more than a model nobody trusts.

Ceramics and manufacturing send inspection work. Surface defects, tone and calibre sorting, and the specific difficulty that the human graders disagree with each other, which means the labels a model learns from are noisier than anybody admits. Quality inspection covers how we approach that, starting with measuring the disagreement.

And the startups arrive with a different question entirely: not compliance, but whether the feature can be built before the runway runs out. That is a separate engagement shape, described under startups.

HOW A VALENCIA PROJECT ACTUALLY RUNS
01

Discovery on site

Valencia is a few hours down the coast from Barcelona by rail or road, so the first workshop happens in your offices, or at the terminal, or in the packhouse. For document work, watching the documents actually arrive teaches more than any specification.
02

Remote, same clock, same country

No timezone offset, no language handover, no cross-border invoicing. A question at any point in the working day gets an answer in that working day.
03

Handover, and easy to come back

Your team takes the system over in a working session rather than a presentation. Being this close means a follow-up visit when peak season breaks something is a train ticket, not a project.
QUESTIONS
QUESTIONS — 5

No. We have one office and it is in Barcelona, and we are not going to pretend otherwise for the sake of a search result. Valencia is close enough that we come down for discovery, for site visits and for handover without it being an expedition.

Often yes, and it is worth testing before committing to anything. Modern models handle poor scans far better than the previous generation of document tooling did, but the honest answer depends on your actual worst documents rather than your representative ones. We would ask for a sample of the bad ones early, because that is what sets the escalation rate and therefore the real economics.

Yes. There is a full AWS region in Spain, and self-hosted open-weight models are an option where nothing may leave your own network. For any hosted model we document its retention and training position at the time of writing and recommend confirming it against the provider's current terms — those change without anyone telling us.

Sí. Trabajamos habitualmente en castellano, català i anglès, y el català y el valencià se entienden sin ningún problema en una reunión. La documentación técnica suele entregarse en inglés por convención del sector, pero la documentación funcional puede ir en castellano si os resulta más útil.

The ranges are published on our pricing page, in euros and exclusive of VAT, and they are the same everywhere — we do not price by postcode. Being three hours away does not lower the fee; it lowers the amount of time lost to coordination, which is where the saving actually shows up.

Keep reading
30-minute technical call · no deck

Paperwork moving
through the port?

Thirty minutes on what arrives, in what state, and what happens to it now. That usually settles whether this is a project or not.

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 →