Vienna Worked from Barcelona Austria and the CEE markets Same hour as us

Vienna.
CEE-ready AI systems.

We are based in Barcelona and work with Austrian companies remotely, in the same hour. The thing that makes a Vienna project different is almost never Austria itself: it is that a Viennese group of any size usually has operations in eight or ten other countries, and the system has to be lawful in all of them.

Last reviewed 5 September 2026 · Engineering guidance, not legal advice.

WHAT IS ACTUALLY DIFFERENT HERE

One national authority, which helps

Austria supervises data protection through a single national body, the Datenschutzbehörde, rather than splitting it by region the way Germany does. For an Austrian-only system that is genuinely simpler: one regulator, one set of published positions, one place to look when a question about automated decision-making comes up. It is the rest of the map that complicates things.

The CEE footprint is the architecture

Vienna is the head office for a great deal of Central and Eastern European business, and that is a technical fact before it is a commercial one. A customer-service model trained or evaluated on data from subsidiaries in the Czech Republic, Slovakia, Hungary, Romania and Croatia touches five supervisory authorities inside the EU. Extend the same group into Serbia, Bosnia or Ukraine and you have left the EEA entirely and need a transfer mechanism for those legs. We design the data boundaries around that map on day one, because retrofitting them country by country is the expensive version.

Compute close by, but not everywhere

Austrian cloud regions exist, and Frankfurt remains the workhorse for anything that needs the full service catalogue. That covers the Austrian entity comfortably. Several of the CEE markets a Vienna group operates in have no local region at all, so if a subsidiary is under a national requirement to keep something in-country, the honest answer is usually a self-hosted open-weight model on infrastructure there, not a hosted endpoint. That is a real build, and we would rather price it than discover it.

Supervision arrives on top of the GDPR

The largest Austrian banking groups sit under direct European Central Bank supervision, with the FMA and the Oesterreichische Nationalbank alongside; energy has its own regulator; life sciences answers to documentation standards that predate all of this. None of it prohibits AI. What each one does is fix where a human decides and what evidence you must be able to produce afterwards, which is a design input rather than a legal obstacle.

THE WORK THAT COMES OUT OF THIS CITY

Almost every Vienna enquiry we take has the same underlying shape, whatever industry it comes from: a process that already works in Austria, and a question about whether it can be made to work the same way in nine other countries without becoming nine separate systems.

Banking and insurance groups bring this most sharply. The document a Slovak branch produces is not the document the Austrian branch produces, the retention rules differ, and the language changes. The engineering that matters is the boundary — one model serving many entities, with per-entity control over what data reaches it and per-entity records of what it did. Our secure data pipeline work is largely about that boundary, and regulatory reporting is where it usually earns its keep first.

Energy and utilities arrive with a different problem: grid, plant and metering data that was captured for operations and is now wanted for planning. That is an integration project wearing an AI hat, and we say so early.

Industrial groups in and around the city hold decades of maintenance history in systems nobody wants to touch. Making that history answerable is unglamorous and reliably valuable.

Life sciences teams bring regulatory and research documents, where the requirement is not fluency but traceability back to the source paragraph. That is the pattern behind our life sciences research work, and where a system stores that trace decides most of the residency conversation.

HOW A VIENNA PROJECT ACTUALLY RUNS

We fly out for discovery

Barcelona to Vienna is a short flight with several a day, and the first workshop is worth doing in a room. On a normal engagement we do not bill it separately. Where the group has CEE entities in scope, we would rather get the right people from two or three of them into that same room once than interview them sequentially over six weeks.

Then remote, on your clock exactly

Austria and Spain share an hour, so there is no overlap arithmetic to do. A question at 09:00 gets an answer that morning, and the working day ends at the same time for both of us.

And back for handover

The session where your engineers take ownership goes better in person. For a multi-entity system we run it against the hardest subsidiary rather than the easiest, because that is the one that will break first. After that the system is yours, in your repositories and your cloud accounts.

QUESTIONS

QUESTIONS — 5

No. We have one office and it is in Barcelona. We travel to Vienna for discovery, for handover and for anything where being in the room changes the outcome. A team our size claiming an Austrian office would be describing a mailbox.

For the Austrian entity, usually yes — there are Austrian cloud regions, and open-weight models can be self-hosted inside your own perimeter, so a system where no personal data leaves the country is a configuration decision rather than a special build. Frankfurt is the more common answer where the full service catalogue is needed, and it is still the EU. For subsidiaries in markets with no local region, in-country means self-hosting, and we will say so rather than quietly routing the traffic somewhere else.

One system with per-entity boundaries, in almost every case we have looked at. Several systems means several evaluation regimes, several sets of prompts drifting apart, and no way to answer a group-level question. The work is in making a single system honest about which entity it is acting for at any moment, and in keeping the records separable afterwards. For the entities outside the EEA, that boundary is also where the transfer question is answered.

The Datenschutzbehörde for data protection in Austria, plus whichever sectoral supervisor already covers you — for a large bank that means the ECB and the FMA rather than instead of them. For subsidiaries, each country has its own data-protection authority, and the group-level answer has to survive the strictest of them. Your DPO and counsel own that analysis; we build so it is not made harder.

The same as anywhere else — the ranges are on the pricing page, in euros and exclusive of VAT. We do not price by postcode. Multi-country scope changes the estimate because it is genuinely more work, not because the invoice has Vienna on it.

Keep reading

Industry

AI for Financial Services

→

Architecture

Secure Data Pipelines

30-minute technical call · no deck