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
## Description
Scrub for W&B branding consistency
- Bias toward terminology in public pricing page and other authoritative
pages, recent blog posts, FullyConnected, social posts
- Squash 'SaaS', 'single-tenant', and other conflations that tend to
creep back in
Fixes WBDOCS-1919
## Testing
- [x] Local build succeeds without errors (`mint dev`)
- [x] Local link check succeeds without errors (`mint broken-links`)
- [x] PR tests succeed
W&B support embedded TensorBoard for W&B Multi-tenant SaaS.
10
+
W&B supports embedded TensorBoard for W&B Multi-tenant Cloud.
11
11
</Note>
12
12
13
13
Upload your TensorBoard logs to the cloud, quickly share your results among colleagues and classmates and keep your analysis in one centralized location.
The following sections apply to W&B SaaS Cloud. If you use a different W&B deployment type, check with your administrator for deployment-specific guidance or limits.
105
+
The following sections apply to W&B Multi-tenant Cloud. If you use a different W&B deployment type, check with your administrator for deployment-specific guidance or limits.
106
106
</Warning>
107
107
108
108
## Recommendations at scale
@@ -345,7 +345,7 @@ W&B does not enforce hard product limits for these recommendations beyond API ra
345
345
346
346
## Rate limits
347
347
348
-
W&B SaaS Cloud APIs use rate limits to maintain service reliability and availability.
348
+
W&B Multi-tenant Cloud APIs use rate limits to maintain service reliability and availability.
349
349
350
350
<Note>
351
351
Rate limits are subject to change.
@@ -395,7 +395,7 @@ For manual syncing, use `wandb sync <run-file-path>`. See [`wandb sync`](/models
395
395
396
396
The W&B app and the [public API](/models/ref/python/public-api/api) use GraphQL requests to query and modify data.
397
397
398
-
For SaaS Cloud:
398
+
For Multi-tenant Cloud:
399
399
400
400
* unauthorized requests are rate-limited per IP address
A single-tenant, fully managed service deployed in W&B's cloud infrastructure. It is the best place to onboard W&B if your organization requires conformance to strict governance controls including data residency, have need of advanced security capabilities, and are looking to optimize their AI operating costs by not having to build & manage the required infrastructure with security, scale & performance characteristics.
23
+
A fully managed service with dedicated, isolated infrastructure in W&B's cloud. It is the best place to onboard W&B if your organization requires conformance to strict governance controls including data residency, have need of advanced security capabilities, and are looking to optimize their AI operating costs by not having to build & manage the required infrastructure with security, scale & performance characteristics.
24
24
25
25
See **[W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud)** for more information.
Copy file name to clipboardExpand all lines: platform/hosting/enterprise-licenses.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ This page provides a comprehensive overview of Enterprise licenses, including wh
14
14
## Deployment options
15
15
Enterprise licenses are available for W&B Dedicated Cloud and Self-Managed deployments.
16
16
17
-
-[W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) provides single-tenant infrastructure managed by W&B, deployed in Google Cloud. Dedicated Cloud deployments automatically include an Enterprise license. No additional configuration is required, and all Enterprise features are available immediately upon provisioning.
17
+
-[W&B Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) provides dedicated, isolated infrastructure managed by W&B, deployed in Google Cloud. Dedicated Cloud deployments automatically include an Enterprise license. No additional configuration is required, and all Enterprise features are available immediately upon provisioning.
18
18
-[W&B Self-Managed](/platform/hosting/hosting-options/self-managed) is deployed on your own infrastructure, providing full control over your deployment and data. Air-gapped deployments are supported. Without an Enterprise license, [Enterprise features](#enterprise-features) are unavailable.
Copy file name to clipboardExpand all lines: platform/hosting/hosting-options.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ This section describes the different ways can you can deploy W&B.
10
10
See [W&B Multi-tenant Cloud](/platform/hosting/#wb-multi-tenant-cloud) or [get started for free](https://app.wandb.ai/login?signup=true).
11
11
12
12
## W&B Dedicated Cloud
13
-
[W&B Dedicated Cloud](/platform/hosting/#wb-dedicated-cloud) is a single-tenant, fully managed platform designed with enterprise organizations in mind. W&B Dedicated Cloud is deployed in W&B's AWS, Google Cloud or Azure account. Dedicated Cloud provides more flexibility than Multi-tenant Cloud, but less complexity than W&B Self-Managed. Upgrades, maintenance, platform security, and capacity planning are managed by W&B. Each Dedicated Cloud instance has its own isolated network, compute and storage from other W&B Dedicated Cloud instances.
13
+
[W&B Dedicated Cloud](/platform/hosting/#wb-dedicated-cloud) is a fully managed platform with dedicated, isolated infrastructure, designed with enterprise organizations in mind. W&B Dedicated Cloud is deployed in W&B's AWS, Google Cloud or Azure account. Dedicated Cloud provides more flexibility than Multi-tenant Cloud, but less complexity than W&B Self-Managed. Upgrades, maintenance, platform security, and capacity planning are managed by W&B. Each Dedicated Cloud instance has its own isolated network, compute and storage from other W&B Dedicated Cloud instances.
14
14
15
15
Your W&B specific metadata and data is stored in an isolated cloud storage and is processed using isolated cloud compute services. [Bring your own bucket (BYOB)](/platform/hosting/data-security/secure-storage-connector) optionally allows you to store artifacts and other related sensitive data in your own cloud or on-premises infrastructure.
Copy file name to clipboardExpand all lines: platform/hosting/hosting-options/dedicated-cloud.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ description: "Learn about W&B Dedicated Cloud deployment features including comp
3
3
title: Dedicated Cloud
4
4
---
5
5
6
-
W&B Dedicated Cloud is a single-tenant, fully managed platform deployed in W&B's AWS, Google Cloud, or Azure cloud accounts. Each Dedicated Cloud instance has its own isolated network, compute and storage from other W&B Dedicated Cloud instances. Your W&B specific metadata and data is stored in an isolated cloud storage and is processed using isolated cloud compute services.
6
+
W&B Dedicated Cloud is a fully managed platform with dedicated, isolated infrastructure, deployed in W&B's AWS, Google Cloud, or Azure cloud accounts. Each Dedicated Cloud instance has its own isolated network, compute and storage from other W&B Dedicated Cloud instances. Your W&B specific metadata and data is stored in an isolated cloud storage and is processed using isolated cloud compute services.
7
7
8
8
W&B Dedicated Cloud is available in [multiple global regions for each cloud provider](./dedicated-cloud/regions)
Copy file name to clipboardExpand all lines: platform/hosting/iam/access-management/restricted-projects.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ Set a project's visibility scope when you create a project or when editing it la
41
41
42
42
#### Set visibility scope when you create a new project
43
43
44
-
1. Navigate to your W&B organization on SaaS Cloud, Dedicated Cloud, or Self-Managed instance.
44
+
1. Navigate to your W&B organization on a W&B Multi-tenant Cloud, Dedicated Cloud, or Self-Managed instance.
45
45
2. Click the **Create a new project** button in the left hand sidebar's **My projects** section. Alternatively, navigate to the **Projects** tab of your team and click the **Create new project** button in the upper right hand corner.
46
46
3. After selecting the parent team and entering the name of the project, select the desired scope from the **Project Visibility** dropdown.
47
47
<Frame>
@@ -91,7 +91,7 @@ Set a project's visibility scope when you create a project or when editing it la
91
91
For the _Team_ or _Restricted_ scoped projects in your team, you can assign a specific role to a user, which could be different from that user's team level role. For example, if a user has _Member_ role at the team level, you can assign the _View-Only_, or _Admin_, or any available custom role to that user within a _Team_ or _Restricted_ scope project in that team.
92
92
93
93
<Note>
94
-
Project level roles are in preview on SaaS Cloud, Dedicated Cloud, and Self-Managed instances.
94
+
Project level roles are in preview on W&B Multi-tenant Cloud, Dedicated Cloud, and Self-Managed instances.
95
95
</Note>
96
96
97
97
### Assign project level role to a user
@@ -112,4 +112,4 @@ When you change the project level role for a user to be different from their tea
112
112
* You **can not** change the project level role of a user who has _View-only_ role at the team level.
113
113
* If the project level role for a user within a particular project **is same as** the team level role, and at some point if a team admin changes the team level role, the relevant project role is automatically changed to track the team level role.
114
114
* If you change the project level role for a user within a particular project such that **it is different from** the team level role, and at some point if a team admin changes the team level role, the relevant project level role remains as is.
115
-
* If you remove a user from a _restricted_ project when their project level role was different from the team level role, and if you then add the user back to the project after some time, they would inherit the team level role due to the default behavior. If needed, you would need to change the project level role again to be different from the team level role.
115
+
* If you remove a user from a _restricted_ project when their project level role was different from the team level role, and if you then add the user back to the project after some time, they would inherit the team level role due to the default behavior. If needed, you would need to change the project level role again to be different from the team level role.
Copy file name to clipboardExpand all lines: platform/hosting/iam/scim.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ For practical Python examples demonstrating how to interact with the SCIM API, v
22
22
-**Service Account Authentication**: Organization service accounts can access the API
23
23
24
24
<Note>
25
-
If you are an admin of multiple Enterprise [Multi-tenant SaaS](/platform/hosting/hosting-options/multi_tenant_cloud) organizations, you must configure the organization where SCIM API requests are sent to ensure SCIM API requests sent using your API Key affect the correct organization. Click your profile image, then click **User Settings**, then check the setting **Default API organization**.
25
+
If you are an admin of multiple Enterprise [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud) organizations, you must configure the organization where SCIM API requests are sent to ensure SCIM API requests sent using your API Key affect the correct organization. Click your profile image, then click **User Settings**, then check the setting **Default API organization**.
26
26
27
27
The chosen hosting option determines the value for the `<host-url>` placeholder used in the examples in this page.
28
28
@@ -697,7 +697,7 @@ Reactivates a previously deactivated user in your organization.
697
697
<Note>
698
698
- User reactivation works for users only, not service accounts. Reactivation is not supported for service accounts. Manage service accounts in the settings for the W&B Team.
699
699
700
-
- User reactivation is not supported in [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud). To restore the user's access, re-add them to your organization. See [Create user](#create-user-request-multi-tenant). In Multi-tenant Cloud, a user's account is not managed by the organization. An attempt to reactivate a user results in a HTTP `400` error:
700
+
- User reactivation is not supported in [Multi-tenant Cloud](/platform/hosting/hosting-options/multi_tenant_cloud). To restore the user's access, re-add them to your organization. See [Create user](#create-user-request-multi-tenant). In Multi-tenant Cloud, a user's account is not managed by the organization. An attempt to reactivate a user results in a HTTP `400` error. The `detail` field in the response body is returned verbatim from the API and may still use legacy product wording:
701
701
```json
702
702
{
703
703
"schemas": [
@@ -2298,7 +2298,7 @@ W&B maintains two separate SCIM API implementations, and the features differ bet
2298
2298
## Limitations
2299
2299
2300
2300
-**Maximum results**: 9999 items per request.
2301
-
-**Single-tenant environments**: Only support one email per user.
2301
+
-**Dedicated Cloud and Self-Managed**: Only support one email per user.
2302
2302
-**Team deletion**: Not supported via SCIM (use the W&B web interface).
2303
2303
-**User reactivation**: Not supported in Multi-tenant Cloud environments.
2304
2304
-**Seat limits**: Operations may fail if organization seat limits are reached.
Copy file name to clipboardExpand all lines: platform/hosting/iam/sso.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ In the context of W&B, access tokens authorize requests to APIs on behalf of the
19
19
20
20
You can use environment variables to [configure IAM options](/platform/hosting/iam/advanced_env_vars) for your [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) or [Self-Managed](/platform/hosting/hosting-options/self-managed) instance.
21
21
22
-
To assist with configuring Identity Providers for [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) or [Self-Managed](/platform/hosting/hosting-options/self-managed)W&B installations, follow these guidelines to follow for various IdPs. If you’re using the SaaS version of W&B, reach out to [support@wandb.com](mailto:support@wandb.com) for assistance in configuring an Auth0 tenant for your organization.
22
+
To assist with configuring Identity Providers for [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud) or [Self-Managed](/platform/hosting/hosting-options/self-managed)deployments, follow these guidelines. If you’re using W&B Multi-tenant Cloud, reach out to [support@wandb.com](mailto:support@wandb.com) for assistance.
23
23
24
24
## Configure your IdP
25
25
This section shows how to configure your identity provider (IdP) for OIDC. Select the tab for your IdP for details.
0 commit comments