Guide · Developer tools

Developer tools from Syria: what each vendor's terms say.

Code hosts, package registries, deploy platforms, design tools and AI APIs all answer the Syria question differently, and many do not answer it at all. Here is each vendor's own wording with its date, so you can pick a stack you will not have to abandon halfway through a project.

Updated 18 November 2026Sources checked 16 November 2026Reviewed by Eng. Hasan Kassas

The short answer

As of 16 November 2026, GitHub is the only vendor in this guide that has formally announced it serves Syria. On 4 September 2025 it said private and paid GitHub.com features, Copilot included, would again be broadly available across the country. A smaller group goes the other way and still names Syria in its terms or help pages: GitLab, Render, Atlassian's Trello, Slack (through the Salesforce agreement) and Notion. The OpenAI API, the Anthropic API, the Gemini API and Microsoft Azure each publish a list of supported countries, and Syria is on none of them.

Most of the rest, including npm, Docker Hub, PyPI, Cloudflare, Netlify, DigitalOcean, AWS, Google Cloud, Firebase, Figma and Expo, name no country at all. Their terms either bar "embargoed" or "sanctioned" places in general, or contain no country clause. That is not a statement that they work in Syria. It means the page is silent, so you cannot lean on it in either direction.

Every row below is what the vendor's own page said when we read it on 16 November 2026. We could not test sign-up or payment from inside Syria, vendors revise their terms without notice, and nothing on this page is legal advice.

Four answers

How to read the tables

Each tool gets one of four labels, taken only from what the vendor itself publishes:

  • Says available: the vendor has stated that its service is open to people in Syria. GitHub.com is the clear example.
  • Names Syria: the vendor's terms or help pages list Syria as a place it does not serve, or where its product may not be sent.
  • Not on its list: the vendor publishes the countries it supports, and Syria is not among them.
  • Names no country: the terms bar embargoed or sanctioned places in general, or say nothing about countries. This is the most common answer, and on its own it tells you nothing about Syria.
Code hosting and registries

Where your code and dependencies live

AnswerWhat the vendor's own page saysPage date
GitHub.comSays availableAnnounced broad access for Syria on 4 Sep 2025, covering private and paid features. Its trade-controls policy names Crimea, the separatist areas of Donetsk and Luhansk, Cuba, Iran and North Korea as the places where US sanctions apply to GitHub.com. Syria is not among themPolicy revised 5 Sep 2025
GitHub CopilotSays availableIncluded in the 4 Sep 2025 announcement. The policy's Copilot paragraph says it may not go to a country in EAR Country Group E:1 without authorization, and its list of restricted destinations (Cuba, Iran, North Korea, Russia, Belarus and parts of Ukraine) does not include SyriaSame page
GitHub Enterprise Server (self-hosted)Names SyriaMay not be sold, exported or re-exported to EAR Country Group E:1, which GitHub says currently includes SyriaSame page
GitLabNames SyriaExport controls under the EAR and "other practical considerations" still prevent it from providing services to Syria. It says it will reassess, with no date20 Feb 2026
npmNames no countryNo country, export or sanctions clause, only a general duty to obey the law. npm is a GitHub company, yet GitHub's trade-controls page does not mention npmTerms 10 Mar 2022
Docker HubNames no countryThe services may not be used in, or exported to, countries the US embargoes. No country is listedEffective 26 Aug 2026
pub.dev (Dart, Flutter)Names no countryNo country clause. Published content must comply with the Google Terms of Service, which name no countries and only ask users to follow export-control and sanctions lawsGoogle terms 30 Jul 2026
Maven CentralNames no countryBars use that breaks applicable laws, US export laws included. No country is listed31 Mar 2026
PyPINames no countryBars use against export-control and sanctions laws and mentions "certain sanctioned countries or territories" without naming anyEffective 25 Feb 2025
Deploy and hosting

Platforms that run your app

AnswerWhat the vendor's own page saysPage date
VercelNames no countryCustomers must not be targets of OFAC, US State Department, UN, EU or other sanctions. No country list. Separately, a Vercel staff member wrote on its forum on 8 Jul 2025 that Vercel could now be accessed from SyriaTerms 19 Oct 2026
NetlifyNames no countryCustomers may not let anyone use the services in a "U.S.-embargoed country or region", and none is named. The revised agreement takes effect on 4 Dec 20264 Nov 2026
CloudflareNames no countryBars parties on US, EU, UK or other restricted lists, and exports to countries where export is restricted. No country list12 Sep 2025
RenderNames SyriaUsers must confirm they are not located in, or a citizen or resident of, Crimea, Donetsk, Luhansk, Cuba, Iran, North Korea or Syria10 Jul 2026
Fly.ioNames no countryA general clause on US export laws. No sanctions wording and no country list29 Apr 2026
RailwayNames no countryBars any use that breaks a law, export-control laws included. No country list20 Apr 2026
DigitalOceanNames no countryBars anyone located in a region under "comprehensive trade or economic sanctions". No region is named22 Aug 2026
Hetzner (Germany)Names no countryCustomers must follow export and import control rules, "in particular the US regulations". No country list27 Oct 2021
The big clouds

AWS, Google Cloud, Firebase and Azure

AnswerWhat the vendor's own page saysPage date
AWSNames no countryBoth parties must follow sanctions and export laws, including the EAR, ITAR and OFAC programmes. No country is named, and we found no AWS page listing the countries where an account can be opened29 Oct 2026
Google CloudNames no countryBars use that breaches "Export Control Laws" (the EAR, OFAC sanctions and ITAR). The free-trial page sets no country condition. We found no Google list of countries where billing accounts can be openedTerms 12 Oct 2026
FirebaseNames no countryNo country or sanctions wording in the Firebase terms. A project on the paid Blaze plan is linked to a Google Cloud Billing account, so paid use runs through Google CloudTerms 24 Sep 2026
Microsoft AzureNot on its listAzure says it is commercially available in 140 countries and regions and lists them. Syria is not listed, while Lebanon, Jordan and Iraq are. Microsoft gives no reasonUndated, read 16 Nov 2026
Build, design and teamwork

Mobile builds, design files and team tools

AnswerWhat the vendor's own page saysPage date
Expo / EASNames no countryThe terms covering EAS Build, Submit, Update and Hosting have no country, export or sanctions clause2 Nov 2026
Codemagic (UK)Names no countryNo country or export clause, only a duty to comply with applicable laws. The operator, Nevercode LTD, is registered in the UK28 Oct 2020
FigmaNames no countryBars use in jurisdictions the US Government embargoes or designates as supporting terrorist activities. No country is named11 Mar 2026
Trello (Atlassian)Names SyriaIts support page says US law prohibits Trello from serving organisations or users located in Crimea, Cuba, Iran, North Korea, Syria, Sudan and Venezuela25 Sep 2025
Jira, Confluence, BitbucketNames no countryThe Atlassian Customer Agreement bars export to any "U.S. embargoed jurisdiction" or to its nationals or residents. None is named1 Oct 2026
SlackNames SyriaSlack is governed by Salesforce's agreement, which bars access from US-embargoed regions, "currently" including Syria. Salesforce's compliance page also lists Syria as a prohibited territory15 Oct 2026
NotionNames SyriaBoth the business agreement and the Personal Use Terms name Syria in their definition of a "Prohibited Person": anyone located or ordinarily resident there, or a company organised under its laws17 Aug 2026 (business)
AI APIs

OpenAI, Anthropic and Gemini

AnswerWhat the vendor's own page saysPage date
OpenAI APINot on its listSyria is not on the supported countries and territories list, which does include Lebanon, Jordan, Iraq, Libya and Yemen. OpenAI warns that use outside the list may get an account blocked or suspendedUndated, read 16 Nov 2026
Anthropic API and Claude appsNot on its listThe Supported Regions Policy says any country not listed is unsupported, and Syria is not listed. It covers the API, the apps and Claude models sold through cloud platforms and resellers. It also treats companies headquartered in, or majority-owned or controlled from, an unsupported region as unsupported, wherever their staff areEffective 12 Nov 2026
Gemini API and Google AI StudioNot on its listSyria is not on the available regions list. For places outside it, the page points to the Gemini API on Google Cloud's enterprise platform, which runs on Google Cloud billing, and Google does not state that billing's status for SyriaUndated, read 16 Nov 2026
Details that matter

What else the vendor pages say

  • GitHub says it works out a user's location from sources that include IP addresses and payment history, not nationality. Its limits on sanctioned people and groups apply in every country, and nobody may use GitHub.com on behalf of such parties.
  • GitLab last changed its trade-compliance page on 20 February 2026, in an update about Syria sanctions. It says it monitors regulatory developments and will reassess "when circumstances permit".
  • Atlassian splits by product. The Trello page names Syria, while the agreement covering Jira and Confluence names no country. We found no current Atlassian page that settles Jira or Confluence for Syria.
  • Render, GitLab, the Trello page, the Salesforce agreement behind Slack and Notion's business agreement were all updated in 2025 or 2026 and still name Syria. Only GitLab gives a reason. Notion's Personal Use Terms date from April 2024 and had not been replaced when we checked.
  • These rows report what vendor pages say. We did not test sign-up forms or payments from inside Syria.
The rules behind it

Why the answers differ

Most of the terms above refer to US export rules, and some vendors are based in the EU or the UK, where different rules apply. These are each government's dated positions, given as facts and not as legal advice.

  • United States, export controls: the Syria page of the Commerce Department's Bureau of Industry and Security (BIS), still headed by its rule of 2 September 2025, says EAR99 items may go to Syria under License Exception SPP, but every item on the Commerce Control List needs a licence unless one of the exceptions applies.
  • BIS lists eight license exceptions available for Syria in whole or in part: SPP, TMP, RPL, GOV, TSU, BAG, AVS and CCD. It reviews licence applications for listed items under a "presumption of approval" for commercial uses that support economic and business development or the Syrian people, telecommunications included.
  • Vendors cite these rules by name. GitHub and GitLab classify their software as 5D992.c, GitHub points to EAR Country Group E:1 for Enterprise Server, and GitLab points to "export controls under the EAR".
  • United States, terrorism list: the US rescinded Syria's State Sponsor of Terrorism designation with effect from 24 August 2026. The wider US timeline is in our app store guide.
  • European Union: on 28 May 2025 the EU Council adopted legal acts lifting all economic restrictive measures on Syria except those based on security grounds. That is relevant to EU companies such as Hetzner, although Hetzner's own terms also point to US regulations.
  • United Kingdom: UK regulations in force from 25 April 2025 removed some sector restrictions on Syria, including on financial services and energy, while other export prohibitions stay in place. Codemagic's operator is a UK company. We did not check UK changes after April 2025.
Practical advice

Choosing a stack you can rely on

  1. Build on terms you can quote

    Prefer tools whose own terms or official announcements speak to your situation. A forum reply or a friend's experience is not a policy. Where a vendor's terms name no country, treat its position on Syria as unknown, not as a yes.

  2. Keep your core off tools that name Syria

    If a vendor's terms list Syria as excluded, do not put your source code, your build pipeline or your customer data there. Choose a provider whose terms you can meet exactly as written.

  3. Answer sign-up questions truthfully

    Location, ownership and billing details must be accurate. If you are not sure you qualify, ask the vendor's support, and a lawyer for anything contractual, before you open the account.

  4. Make your code portable

    Git keeps the full history in every clone. Keep a second copy of each repository on a machine or service you control, commit your lockfiles, and keep build and deploy steps in scripts inside the repository rather than in one platform's settings screen.

  5. Export your data on a schedule

    Back up databases, design files, boards and documents in formats other tools can open, and test a restore every so often. A backup you have never restored is a hope, not a plan.

  6. Put AI and cloud calls behind your own layer

    Call AI models and cloud services through a thin interface in your code, so switching provider means changing one module instead of rewriting features.

  7. Keep a dated terms log

    For each tool, write down the page URL, the day you read it and the exact sentence you relied on. Read it again before you sign a contract or move to a paid plan, and on a fixed date every quarter.

FAQ

Common questions

GitHub.com does, according to GitHub. It announced on 4 September 2025 that private and paid features, Copilot included, would be broadly available again across Syria, and its trade-controls policy no longer lists Syria for GitHub.com. The self-hosted GitHub Enterprise Server is different: the same page says it may not be exported to EAR Country Group E:1, which GitHub says currently includes Syria.

Sources

Where these facts come from

  1. Syria export controls: licence position and exceptionsU.S. Commerce, BIS · accessed 16 Nov 2026
  2. EU adopts legal acts to lift economic sanctions on SyriaEEAS, republishing the Council of the EU · 28 May 2025
  3. Notice to exporters 2025/12: amendments to the Syria sanctionsUK Export Control Joint Unit · 29 Apr 2025
  4. GitHub is enabling broader access for developers in SyriaGitHub Blog · 4 Sep 2025
  5. GitHub and trade controls (GitHub.com, Enterprise Server, Copilot)GitHub Docs · revised 5 Sep 2025
  6. GitLab trade compliance (Syria paragraph)GitLab Handbook · updated 20 Feb 2026
  7. npm Open Source Termsnpm · updated 10 Mar 2022
  8. Docker Terms of Use, section 11: export controls and sanctionsDocker · effective 26 Aug 2026
  9. pub.dev policypub.dev (Google, Dart team) · accessed 16 Nov 2026
  10. Google Terms of ServiceGoogle · effective 30 Jul 2026
  11. Central Repository Terms of ServiceSonatype (Maven Central) · updated 31 Mar 2026
  12. PyPI Terms of ServicePython Software Foundation · effective 25 Feb 2025
  13. Vercel Terms of ServiceVercel · updated 19 Oct 2026
  14. Request to reconsider geo-blocking of Syria (staff reply)Vercel Community · 8 Jul 2025
  15. Netlify Self-Serve Subscription Agreement, section 12.1Netlify · updated 4 Nov 2026
  16. Updates to Netlify's terms (effective date of the revised agreement)Netlify changelog · effective 4 Dec 2026
  17. Cloudflare Self-Serve Subscription Agreement, section 7.1Cloudflare · updated 12 Sep 2025
  18. The challenges of sanctioning the internet (historical)Cloudflare Blog · 12 Dec 2022
  19. Render Terms of ServiceRender · modified 10 Jul 2026
  20. Fly.io Terms of ServiceFly.io · effective 29 Apr 2026
  21. Railway Terms of ServiceRailway · effective 20 Apr 2026
  22. DigitalOcean Terms of Service, section 5.7DigitalOcean · updated 22 Aug 2026
  23. Hetzner General Terms and Conditions, section 4.5Hetzner Online GmbH · updated 27 Oct 2021
  24. AWS Customer Agreement, section 11.6Amazon Web Services · updated 29 Oct 2026
  25. Google Cloud Terms of ServiceGoogle Cloud · modified 12 Oct 2026
  26. Google Cloud free program eligibilityGoogle Cloud · updated 13 Nov 2026
  27. Terms of Service for Firebase ServicesFirebase · modified 24 Sep 2026
  28. Firebase pricing plans (Blaze is linked to Cloud Billing)Firebase · updated 12 Nov 2026
  29. Azure free account FAQ (countries where Azure is available)Microsoft Azure · accessed 16 Nov 2026
  30. Google Workspace availability by countryGoogle Workspace Admin Help · updated 10 Nov 2026
  31. Expo Terms of Service (covers EAS)Expo (650 Industries) · updated 2 Nov 2026
  32. Codemagic Terms of ServiceNevercode LTD (Codemagic) · updated 28 Oct 2020
  33. Figma Terms of Service, section 2.2Figma · effective 11 Mar 2026
  34. Trello: sanctioned countriesAtlassian Support · updated 25 Sep 2025
  35. Atlassian Customer Agreement, section 20.13Atlassian · effective 1 Oct 2026
  36. Slack Main Services Agreement page (points to Salesforce's)Slack · updated 25 Apr 2023
  37. Salesforce Main Services Agreement, section 12.1Salesforce · updated 15 Oct 2026
  38. Salesforce compliance: prohibited territoriesSalesforce · July 2025
  39. Notion terms (Master Subscription Agreement, Personal Use Terms)Notion · agreement effective 17 Aug 2026
  40. OpenAI API supported countries and territoriesOpenAI · accessed 16 Nov 2026
  41. Anthropic Supported Regions PolicyAnthropic · effective 12 Nov 2026
  42. Gemini API available regionsGoogle AI for Developers · accessed 16 Nov 2026
  43. Rescission of Syria's State Sponsor of Terrorism designationFederal Register · 31 Aug 2026

Checked 16 November 2026. Vendor terms change, often without an announcement, so read each page again before you rely on it. Nothing here is legal advice.

Choosing tools for a team in Syria?

Tell us what you are building. We will help you pick a stack whose terms you can rely on, and keep it portable.