You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/hub/advanced-compute-options.md
+33-20Lines changed: 33 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,19 @@ Enterprise Hub organizations gain access to advanced compute options to accelera
6
6
This feature is part of the <ahref="https://huggingface.co/enterprise"target="_blank">Enterprise Hub</a>.
7
7
</Tip>
8
8
9
+
## Host ZeroGPU Spaces in your organization
10
+
11
+
ZeroGPU is a dynamic GPU allocation system that optimizes AI deployment on Hugging Face Spaces. By automatically allocating and releasing NVIDIA A100 GPUs (40GB VRAM) as needed, organizations can efficiently serve their AI applications without dedicated GPU instances.
12
+
13
+
**Key benefits for organizations**
14
+
15
+
-**Free GPU Access**: Access powerful NVIDIA A100 GPUs at no additional cost through dynamic allocation
16
+
-**Enhanced Resource Management**: Host up to 50 ZeroGPU Spaces for efficient team-wide AI deployment
17
+
-**Simplified Deployment**: Easy integration with PyTorch-based models, Gradio apps, and other Hugging Face libraries
18
+
-**Enterprise-Grade Infrastructure**: Access to high-performance NVIDIA A100 GPUs with 40GB VRAM per workload
19
+
20
+
[Learn more about ZeroGPU →](https://huggingface.co/docs/hub/spaces-zerogpu)
21
+
9
22
## Train on NVIDIA DGX Cloud
10
23
11
24
Train on NVIDIA DGX Cloud offers a simple no-code training job creation experience powered by Hugging Face AutoTrain and Hugging Face Spaces. Instantly access NVIDIA GPUs and avoid the time-consuming work of writing, testing, and debugging training scripts for AI models.
@@ -18,30 +31,30 @@ Read the [blogpost for Train on NVIDIA DGX Cloud](https://huggingface.co/blog/tr
18
31
19
32
#### Transformers
20
33
21
-
| Architecture |
22
-
|---------------------------|
23
-
| Llama |
24
-
| Falcon |
25
-
| Mistral |
26
-
| Mixtral |
27
-
| T5 |
28
-
| gemma |
34
+
| Architecture |
35
+
|------------|
36
+
| Llama |
37
+
| Falcon |
38
+
| Mistral |
39
+
| Mixtral |
40
+
| T5 |
41
+
| gemma |
29
42
30
43
#### Diffusers
31
44
32
-
| Architecture |
33
-
|---------------------------|
34
-
| Stable Diffusion |
35
-
| Stable Diffusion XL |
45
+
| Architecture |
46
+
|-------------------|
47
+
| Stable Diffusion |
48
+
| Stable Diffusion XL |
36
49
37
50
### Pricing
38
51
39
52
Usage of Train on NVIDIA DGX Cloud is billed by the minute of the GPU instances used during your training jobs. Usage fees accrue to your Enterprise Hub Organizations’ current monthly billing cycle, once a job is completed. You can check your current and past usage at any time within the billing settings of your Enterprise Hub Organization.
@@ -59,8 +72,8 @@ You can find all supported models in [this NVIDIA Collection](https://huggingfac
59
72
60
73
Usage of NVIDIA NIM API (serverless) is billed based on the compute time spent per request. Usage fees accrue to your Enterprise Hub Organizations’ current monthly billing cycle, once a job is completed. You can check your current and past usage at any time within the billing settings of your Enterprise Hub Organization.
The total cost for a request will depend on the model size, the number of GPUs required, and the time taken to process the request. For each model, you can find which hardware configuration is used in the notes of [this NVIDIA Collection](https://huggingface.co/collections/nvidia/nim-66a3c6fcdcb5bbc6e975b508).
79
+
The total cost for a request will depend on the model size, the number of GPUs required, and the time taken to process the request. For each model, you can find which hardware configuration is used in the notes of [this NVIDIA Collection](https://huggingface.co/collections/nvidia/nim-66a3c6fcdcb5bbc6e975b508).
Copy file name to clipboardExpand all lines: docs/hub/audit-logs.md
+72-2Lines changed: 72 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,76 @@ This feature is part of the <a href="https://huggingface.co/enterprise" target="
6
6
7
7
Audit Logs enable organization admins to easily review actions taken by members, including organization membership, repository settings and billing changes.
8
8
9
-
Audit Logs are accessible through your organization admin settings.
This feature is part of the <ahref="https://huggingface.co/enterprise"target="_blank">Enterprise Hub</a>.
5
+
</Tip>
6
+
7
+
Enterprise Hub organizations can improve their security with advanced security controls for both members and repositories.
8
+
9
+
<divclass="flex justify-center">
10
+
<img class="block dark:hidden !m-0" src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/enterprise/advanced-security.png" alt="screenshot of the Dataset Viewer on a private dataset owned by an Enterprise Hub organization."/>
11
+
<img class="hidden dark:block !m-0" src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/enterprise/advanced-security-dark.png" alt="screenshot of the Dataset Viewer on a private dataset owned by an Enterprise Hub organization."/>
12
+
</div>
13
+
14
+
## Members Security
15
+
16
+
Configure additional security settings to protect your organization:
17
+
18
+
-**Two-Factor Authentication (2FA)**: Require all organization members to enable 2FA for enhanced account security.
19
+
-**User Approval**: For organizations with a verified domain name, require admin approval for new users with matching email addresses. This adds a verified badge to your organization page.
20
+
21
+
## Repository Visibility Controls
22
+
23
+
Manage the default visibility of repositories in your organization:
24
+
25
+
-**Public by default**: New repositories are created with public visibility
26
+
-**Private by default**: New repositories are created with private visibility. Note that changing this setting will not affect existing repositories.
27
+
-**Private only**: Enforce private visibility for all new repositories, with only organization admins able to change visibility settings
28
+
29
+
These settings help organizations maintain control of their ownership while enabling collaboration when needed.
Copy file name to clipboardExpand all lines: docs/hub/enterprise-hub.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
Enterprise Hub adds advanced capabilities to organizations, enabling safe, compliant and managed collaboration for companies and teams on Hugging Face.
-an audit of where your organization repos are currently located
29
-
-dropdowns to select where your repos will be created
28
+
-An audit of your organization's repository locations
29
+
-Options to select where new repositories will be stored
30
30
31
31
## Repository Tag
32
32
33
-
Any repo (model or dataset) stored in a non-default location will display its Region directly as a tag. That way your organization's members can see at a glance where repos are located.
33
+
Any repository (model or dataset) stored in a non-default location displays its Region as a tag, allowing organization members to quickly identify repository locations.
In regulated industries, companies may be required to store data in a specific region.
41
+
Regulated industries often require data storage in specific regions.
42
42
43
-
For companies in the EU, that means you can use the Hub to build ML in a GDPRcompliant way: with datasets, models and inference endpoints all stored within EU data centers.
43
+
For EU companies, you can use the Hub for ML development in a GDPR-compliant manner, with datasets, models and inference endpoints stored in EU data centers.
44
44
45
45
## Performance
46
46
47
-
Storing your models or your datasets closer to your team and infrastructure also means significantly improved performance, for both uploads and downloads.
47
+
Storing models and datasets closer to your team and infrastructure significantly improves performance for both uploads and downloads.
48
48
49
-
This makes a big difference considering model weights and dataset files are usually very large.
49
+
This impact is substantial given the typically large size of model weights and dataset files.
As an example, if you are located in Europe and store your repositories in the EU region, you can expect to see ~4-5x faster upload and download speeds vs. if they were stored in the US.
53
+
For example, European users storing repositories in the EU regioncan expect approximately 4-5x faster upload and download speeds compared to US storage.
0 commit comments