Deploy W&B Platform On-premises

Hosting W&B Server on on-premises infrastructure

W&B recommends fully managed deployment options such as W&B Multi-tenant Cloud or W&B Dedicated Cloud deployment types. W&B fully managed services are simple and secure to use, with minimum to no configuration required.

Reach out to the W&B Sales Team for related question: [e-mail].

Infrastructure guidelines

Before you start deploying W&B, refer to the reference architecture for complete infrastructure requirements, including hardware sizing recommendations.

Version Requirements

Software	Minimum version
Kubernetes	v1.32 or newer (Supported Kubernetes versions)
Helm	v3.x
MySQL	v8.0.x is required, v8.0.32 or newer; v8.0.44 or newer is recommended. Aurora MySQL 3.x releases, must be v3.05.2 or newer
Redis	v7.x

Hardware Requirements

CPU Architecture: W&B runs on Intel (x86) CPU architecture only. ARM is not supported.

Sizing: For CPU, memory, and disk sizing recommendations for Kubernetes nodes and MySQL, see the Sizing section in the reference architecture. Requirements vary based on whether you’re running Models, Weave, or both.

MySQL database

W&B requires an external MySQL database.

For production, W&B strongly recommends using managed database services:

• AWS RDS Aurora MySQL
• Google Cloud SQL for MySQL
• Azure Database for MySQL

Managed database services provide automated backups, monitoring, high availability, patching, and reduce operational overhead.

See the reference architecture for complete MySQL requirements, including sizing recommendations and configuration parameters. For database creation SQL, see the bare-metal guide. For questions about your deployment’s database configuration, contact support or your AISE.

For MySQL version requirements, see the Version Requirements section above.

For MySQL configuration parameters for self-managed instances, see the reference architecture MySQL configuration section.

Database creation

Create a database and a user with the following SQL commands. Replace SOME_PASSWORD with a secure password of your choice:

CREATE USER 'wandb_local'@'%' IDENTIFIED BY 'SOME_PASSWORD';
CREATE DATABASE wandb_local CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;
GRANT ALL ON wandb_local.* TO 'wandb_local'@'%' WITH GRANT OPTION;

For SSL/TLS certificate requirements, see the SSL/TLS section below.

Redis

W&B depends on a single-node Redis 7.x deployment used by W&B’s components for job queuing and data caching. For convenience during testing and development of proofs of concept, W&B Self-Managed includes a local Redis deployment that is not appropriate for production deployments.

For production deployments, W&B can connect to a Redis instance in the following environments:

• AWS Elasticache
• Google Cloud Memory Store
• Azure Cache for Redis
• Redis deployment hosted in your cloud or on-premise infrastructure

Object storage

W&B requires object storage with pre-signed URL and CORS support.

For production deployments, W&B recommends using managed object storage services:

• Amazon S3: Object storage service offering industry-leading scalability, data availability, security, and performance.
• Google Cloud Storage: Managed service for storing unstructured data at scale.
• Azure Blob Storage: Cloud-based object storage solution for storing massive amounts of unstructured data.
• CoreWeave AI Object Storage: High-performance, S3-compatible object storage service optimized for AI workloads.

For self-hosted object storage options, see the bare-metal guide object storage section for detailed setup instructions including CORS configuration and enterprise alternatives.

MinIO Open Source is in maintenance mode with no active development or pre-compiled binaries. For production deployments, W&B recommends using managed object storage services or enterprise-grade S3-compatible solutions.

See the reference architecture object storage section for complete requirements.

Self-hosted object storage setup

The object store can be externally hosted on any Amazon S3 compatible object store that has support for signed URLs. Run the following script to check if your object store supports signed URLs. See the MinIO setup section below for important information about MinIO Open Source status.

Additionally, the following CORS policy needs to be applied to the object store.

<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
    <AllowedOrigin>http://YOUR-W&B-SERVER-IP</AllowedOrigin>
    <AllowedMethod>GET</AllowedMethod>
    <AllowedMethod>PUT</AllowedMethod>
    <AllowedMethod>HEAD</AllowedMethod>
    <AllowedHeader>*</AllowedHeader>
</CORSRule>
</CORSConfiguration>

Configure object storage through the System Console or directly in the W&B Custom Resource (CR) specification.

AWS S3 configuration

For AWS S3 buckets, configure the following in your W&B CR:

bucket:
  kmsKey: <kms key arn>  # Optional KMS key for encryption
  name: <bucket name>    # Example: wandb
  path: ""               # Keep as empty string
  provider: s3
  region: <region>       # Example: us-east-1

TLS is enabled by default for AWS S3 connections.

S3-compatible storage configuration

For S3-compatible storage (such as MinIO), use the following configuration:

bucket:
  kmsKey: null
  name: <s3 endpoint>    # Example: s3.example.com:9000
  path: <bucket name>    # Example: wandb
  provider: s3
  region: <region>       # Example: us-east-1

To use TLS for S3-compatible storage, append ?tls=true to the bucket path:

bucket:
  kmsKey: null
  name: "s3.example.com:9000"
  path: "wandb?tls=true"
  provider: "s3"
  region: "us-east-1"

For certificate requirements, see the SSL/TLS section section below. The certificate must be trusted. Self-signed certificates require additional configuration.

The most important things to consider when running your own object store are:

1. Storage capacity and performance. It’s fine to use magnetic disks, but you should be monitoring the capacity of these disks. Average W&B usage results in 10’s to 100’s of Gigabytes. Heavy usage could result in Petabytes of storage consumption.
2. Fault tolerance. At a minimum, the physical disk storing the objects should be on a RAID array. If you use S3-compatible storage, consider using a distributed or highly available configuration.
3. Availability. Monitoring should be configured to ensure the storage is available.

There are many enterprise alternatives to running your own object storage service such as:

1. Amazon S3 on Outposts
2. NetApp StorageGRID

MinIO setup

MinIO Open Source is in maintenance mode with no active development. Pre-compiled binaries are no longer provided, and only critical security fixes are considered case-by-case. For production deployments, W&B recommends using managed object storage services or MinIO Enterprise (AIStor).

If you are using an existing MinIO deployment or MinIO Enterprise, you can create a bucket using the MinIO client:

mc config host add local http://$MINIO_HOST:$MINIO_PORT "$MINIO_ACCESS_KEY" "$MINIO_SECRET_KEY" --api s3v4
mc mb --region=us-east1 local/local-files

For new deployments, consider enterprise alternatives listed above or managed cloud object storage services.

Deploy W&B Server application to Kubernetes

The recommended installation method is using the W&B Kubernetes Operator, deployed via Helm.

For complete installation instructions, see Run W&B Server on Kubernetes (Operator), which covers:

• Helm CLI deployment
• Helm Terraform Module deployment
• W&B Cloud Terraform modules

The sections below highlight considerations specific to on-premises/datacenter deployments.

OpenShift

W&B supports deployment on OpenShift Kubernetes clusters in on-premises environments. See the reference architecture for more details and the Operator guide OpenShift section for specific configuration instructions that you can adapt for your on-premises OpenShift deployment.

Networking

For networking requirements, load balancer options, and configuration examples (including nginx), see the reference architecture networking sections.

Verify your installation

To verify the installation, W&B recommends using the W&B CLI. The verify command executes several tests that verify all components and configurations.

This step assumes that the first admin user account is created with the browser.

Follow these steps to verify the installation:

1. Install the W&B CLI:

pip install wandb

2. Log in to W&B:

wandb login --host=https://YOUR_DNS_DOMAIN

For example:

wandb login --host=https://wandb.company-name.com

3. Verify the installation:

wandb verify

A successful installation and fully working W&B deployment shows the following output:

Default host selected:  https://wandb.company-name.com
Find detailed logs for this test at: /var/folders/pn/b3g3gnc11_sbsykqkm3tx5rh0000gp/T/tmpdtdjbxua/wandb
Checking if logged in...................................................✅
Checking signed URL upload..............................................✅
Checking ability to send large payloads through proxy...................✅
Checking requests to base url...........................................✅
Checking requests made over signed URLs.................................✅
Checking CORs configuration of the bucket...............................✅
Checking wandb package version is up to date............................✅
Checking logged metrics, saving and downloading a file..................✅
Checking artifact save and download workflows...........................✅

Contact W&B Support if you encounter errors.