English
Deutsch
Español
العربيةCities we work from
A city page exists where the city changes something a country page cannot say: the hours our day overlaps with yours, what gets built there, and which entity or regime applies locally.
North America
New York
One hour of shared day, written decisions, and tax that is a per-address calculation rather than a rate.
Washington DC
Buyers whose data can be demanded by a process rather than a user, where completeness of a record set matters more than any single screen.
Boston
Research and clinical data where the risk is re-identification rather than disclosure, and a consent that can be withdrawn after analysis has begun.
Chicago
Calculation engines whose answers have to be reproducible years later, batch windows with a hard end, and a calendar the code cannot infer.
Los Angeles
Availability as a function of place and date, long-running work that cannot live in a web request, and money that is owed to several parties at once.
San Francisco
The widest time gap we work across, which rules out supervising anything live and makes the plan the deliverable.
Austin
Usage billed after the fact, an invoice that has to reconcile to the event log, and two systems that both think they know whether a customer is active.
Miami
Payments that cross a border, two currencies on one transaction, and an exchange rate that is part of the record rather than a display detail.
Toronto
Tax that varies by province, French that is law rather than courtesy, and both decided in the schema rather than the interface.
Montreal
Portability as a real feature rather than a promise, defaults that have to be restrictive before anybody chooses, and automated decisions that need a record of their reasons.
Vancouver
One database, customers from Asia to Atlantic Canada, and scheduled work whose correct time depends on who it is for.
Ottawa
Bilingual obligations that reach the database rather than the template, a publish gate nobody can bypass, and translation as a tracked state.
Calgary
Measurement data that is provisional for longer than anybody expects, accounting periods that cannot simply be rewritten, and figures that have to explain their own revision.
Europe
Berlin
Teams that already have engineers, an hour of difference, and privacy duties that land in the data model.
Munich
Enterprise buyers, procurement ahead of engineering, and systems that run inside the building rather than on a platform.
Frankfurt
Supervised buyers, a log that has to say who looked at what, and a legal duty to keep records that collides with a duty to erase them.
Hamburg
Messages whose only idempotency key is a reference number, batch jobs that have to survive dying halfway, and rates that were true last month.
London
Five hours of shared day, inherited codebases with real money moving through them, and UK rules that have drifted.
Manchester
Operations software with a physical business behind it, and integrations that decide the project before the interface does.
Birmingham
Industrial data with real structure, conversions that must be explicit, and a migration off the file that the business actually runs on.
Edinburgh
A regulated buyer, a bank connection that stops working after ninety days by design, and money that has to be explainable rather than approximately right.
Leeds
Buyers handling special category data, and an application whose real exposure is in its logs rather than its database.
Glasgow
Public service systems whose hardest problem is deciding that two records are one person, and workflows measured in years rather than sessions.
Bristol
High-write workloads in a relational database, data that has to be summarised before it is useful, and a retention policy that is an engineering decision.
Madrid
Corporate buyers, invoicing with certification requirements, and regional rules that make one national configuration insufficient.
Barcelona
Product teams rather than corporates, and a third language that is record data rather than interface strings.
Valencia
Negotiated terms per customer, availability that depends on what is reserved, and an invoice that has to be explainable a year later.
Malaga
Reservation systems where the hard part is concurrency, seasonal rates that belong to a period, and dates that break the moment they become timestamps.
Amsterdam
Six shared hours, English without it being a concession, and a payment that cannot be authorised and captured later.
Rotterdam
An identity model where the subject is a company, a membership that carries its own role, and an invitation flow that cannot be abused.
Eindhoven
Option sets with real constraints between them, a quote that has to still be buildable, and a serial number that carries its own configuration for a decade.
Gulf
Dubai
Nearly a full shared day, an invoice that is not valid until a third party accepts it, and Arabic that has to be stored and searched, not only displayed.
Abu Dhabi
Work delivered through an integrator, a schema where the Arabic name is authoritative, and integrations where delivery has to be provable.
Riyadh
Effectively the same working hours, programme buyers with integrators attached, and where data rests decided before the model.
Jeddah
Private-sector commerce, payment that happens after delivery or not at all, and business dates that no library can calculate.
Asia-Pacific
Sydney
Push payments that have to be matched rather than confirmed, and a notification deadline that makes your data model the answer.
Melbourne
Product teams with their own engineers, and data whose retention and consent rules reach the schema rather than the privacy page.
Brisbane
One database serving forty businesses, a scope that must be impossible to forget, and head-office reporting that deliberately breaks the isolation.
Perth
Five hours of shared working day, data captured offline with identifiers the client generated, and conflicts the server has to resolve rather than reject.
Adelaide
Traceability as a recursive data problem, a recall that has to be answerable in hours, and provenance claims that have to be evidenced.
Canberra
Data whose sensitivity is a property of the row rather than of the system, and every export, log and backup having to respect it.
Auckland
A daily written handover instead of calls, a simple tax model, and a hosting choice you have to be able to defend.
Wellington
Te reo Māori reaching the data layer, search that has to find a name typed either way, and a duplicate created by a missing macron.
Christchurch
Cases whose substance is attachments, uploads from third parties that cannot be trusted, and a file that has to still be retrievable in seven years.
Why a page per city
Because three things change inside a country and a country page cannot carry them. How many hours of our working day overlap with yours, which decides whether a question is answered today or tomorrow. What is actually built there, which is not the same in a capital and in an industrial centre two hours away. And which entity or regime applies - a free zone, a canton, a province - which is a city-level fact in several of the places we work.
Where none of those three differ, there is no city page. A page that repeats the country with a name swapped is a doorway, and it is measured here rather than assumed.
Tell us what you are building.
A repository, a slow query log, or three sentences about what keeps breaking. What comes back is an engineer's opinion, not a brochure.