As part of our Enterprise Hub Plan, we recently released support for our storage region.
Regions can determine where organizational models and datasets are stored. This has two main advantages: I’ll explain this briefly in this blog post.
Regulatory and legal compliance, and more generally, better digital sovereignty performance (improve download and upload speeds and latency)
Currently we support the following regions:
We eu eu🇪🇺 coming soon: Asia Pacific🌏
However, first let’s take a look at how to set up this feature in your organization’s settings.
ORG settings
If your organization is not an Enterprise Hub organization already, you will see the following screen:
You can view the Area Settings page immediately after subscribing.
On that page you can see:
Audit where Orgs repository is currently located
Repository Tags
Repositories (models or datasets) stored in non-default locations will display the area directly as tags. This will allow organization members to see where the report is.
Regulatory and Legal Compliance
Many regulatory industries may require data to be stored in a specific area.
For EU companies, this means that they can build ML in a GDPR-compliant way using hubs. Store all datasets, models, and inference endpoints in an EU data center.
If you are an Enterprise Hub customer and have any further questions about this, please contact us!
performance
Bringing your model or dataset closer to your team and storing your infrastructure means significantly improving performance for both uploads and downloads.
This makes a big difference considering the weights of the model and the dataset files are usually very large.
As an example, if you are in Europe and have your repository stored in the EU region, and if you are stored in the US, you can expect ~4-5 times the speed, download speed and download speed.
