EnglishWhere we work
The markets we take engagements in, and what each one changes about the build. These pages are written country by country rather than generated from one.
North America
Europe
Germany
GDPR obligations that reach the schema, e-invoicing with a format, and hosting decided before the first migration.
Netherlands
iDEAL, which has no card semantics, Peppol as a network rather than a format, and a regulator that actually enforces consent.
Spain
Invoicing software with certification requirements, regional rules inside the country, and immediate reporting for larger filers.
United Kingdom
HMRC as a real integration, Companies House as a source of truth, and a tax year that starts in April.
Gulf
Bahrain
Mandatory open banking APIs to build against, and a data protection law with named responsibilities behind it.
Kuwait
Data classification decided before hosting, which makes residency a per-table question rather than a per-application one.
Qatar
A data protection law that predates the region's others, and an invoicing model that should assume a tax which does not exist yet.
Saudi Arabia
ZATCA integration, residency decided before hosting, and Arabic that reaches the database rather than the theme.
United Arab Emirates
E-invoicing through an accredited provider, a working week that is not Monday to Friday, and Arabic that reaches the database.
Why a page per country at all
Because the constraints reach the schema. Handling personal data in Germany means a deletion path and a processing record that have to exist in the tables, not in a policy document. Selling into Saudi Arabia means a signed e-invoicing integration and a residency decision, both settled before the first migration runs. A UK financial product inherits Open Banking rules that shape the architecture rather than sit beside it.
These are not lines of marketing copy with a country name substituted in. Each one moves something structural - the schema, the queue topology, or the question of where the database is permitted to live.
All of it is delivered remotely from Ankara, which is how this work is best done in any case: read the system, measure it, hand back something written down. The value is having met the constraint before, and being able to say which parts of it will eat your timeline.
Every engagement is carried out in English.
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.