The dependency map
What do we use, where does it come from and how could we switch? The map includes our own gaps.
Read this map as a snapshot
As of 22 October 2026. This map covers ITARR itself. Individual assignments may involve different services and agreements.
Origin identifies who provides a service or design. A way out is an option, not a completed migration. Where no switching date has been set, we say so.
AI models
Origin: external AI services from the United States and open models, including models from China, running on our own machines in the Netherlands.
Why: we choose tools capable of the task. Local models do not yet meet the quality needed for all our work.
Way out: test another model or service for each task. A different engine requires new checks of quality and tools. Switching date: per assignment, with no fixed general date.
Chips
Origin: hardware using designs from companies including NVIDIA and Apple, both from the United States.
Why: these machines make local computing possible. Owning the device does not give us ownership of its chip design.
Way out: consider other hardware when replacing equipment. It is not a direct replacement without changes. Switching date: not set.
Computing
Origin: our own machines in Breda, the Netherlands, alongside computing provided by external AI services.
Why: run locally where it fits, using external capacity or capabilities when the task calls for them.
Way out: moving work requires enough capacity and a successful test. We have not demonstrated a route to replace all external AI. Switching date: per task.
Sign-in
This public site has no account and does not ask you to sign in. You can read its pages without a Microsoft or Google account.
The ITARR Hive is still under construction. Its final member sign-in method is not in use on this site. We therefore make no independence claim for it.
Way out and switching date: part of the design of the future member space.
Origin: Microsoft 365, provided by Microsoft in the United States.
Why: this is our existing email environment. An email to ITARR therefore does not pass only through machines we control.
Way out: another email service is possible, but no replacement has been chosen. Switching date: not set.
Code
Origin: our own code environment in the Netherlands; some code is still on GitHub, United States.
Why: existing projects and tools use both environments.
Way out: move code to our own environment. Having that environment does not prove that every project has moved. Switching date: per project, not fully set.
Domain
Origin: our domains and DNS are managed through TransIP, the Netherlands.
Why: a domain name and DNS make the site reachable and point to its web server. This remains a dependency even with our own server.
Way out: DNS and domain management can move to another provider. This takes preparation and checks. Switching date: not set.
Workplace
Origin: equipment including Apple hardware and software from the United States, operated by us in the Netherlands.
Why: these are tools we use to build and test local models.
Way out: different hardware and operating systems require changes to tools and working methods. A full switch has not been demonstrated. Switching date: not set.
Found a gap?
This map is part of the work. If a dependency changes or a way out proves inadequate, the description needs to change too. Tell us if something is wrong.