Wasabi OEM Quick Start Guide

Bundle Wasabi Hot Cloud Storage with your own solution and offer it as a complete, branded package to your customers and channel partners.

This guide provides an overview of the tools and features available to Wasabi OEM partners. For detailed setup instructions, follow the links to each product's full documentation.

Why Partner With Wasabi as an OEM?

As a Wasabi OEM partner, you integrate Wasabi Hot Cloud Storage directly into your product and offer it as part of your solution. Your customers get a seamless experience—and you get predictable, low-cost cloud storage without the complexity of building or managing it yourself.

You choose how to brand it: fully white-label under your own name, or use the Powered by Wasabi badge to leverage Wasabi's market recognition. Either way, you control the customer relationship, pricing, and go-to-market strategy.

OEM partners typically build solutions in areas such as:

• Backup and disaster recovery

• Video surveillance and security

• SaaS platforms and application development

• Media workflows and content delivery

• AI/ML and data analytics

To learn more about the OEM program and partnership benefits, see the Wasabi OEM Partner Program.

OEM Features at a Glance

Wasabi Account Control Manager (WACM)

WACM is Wasabi's multi-tier account management platform. It lets you create, manage, and bill customer accounts from a single console, reducing setup time from days to minutes.

Key capabilities are:

• Provision customer accounts (Sub-Accounts) with configurable storage quotas and trial periods

• Consolidated billing across all managed accounts with sub-invoicing for each customer

• Usage tracking with per-account, per-bucket storage and egress metrics

• Trial account support to create 30, 60, or 90-day trials that auto-convert to paid accounts

• User role management for Admin, Staff, Staff Lite, and Viewer roles for your team

• Account lifecycle management to suspend, restore, and manage accounts, as needed

Account Hierarchy

WACM supports a multi-tier account structure designed for OEM and channel distribution:

• Account Governance (AG)—Top-level oversight across multiple Control Accounts. This is used when distributing through multiple channels.

• Control Account—Your paying Wasabi account. All Sub-Account billing consolidates here.

• Channel Account—Optional tier for giving resellers and distributors their own WACM access to manage Sub-Accounts.

• Sub-Account—An individual Wasabi storage account for an end customer.

A typical OEM account hierarchy looks like this:

For complete documentation, refer to Getting Started With WACM and the WACM Product Guide.

Channel Accounts

Channel Accounts let you extend WACM access to your resellers, distributors, or regional partners. Each Channel Account user can create and manage their own Sub-Accounts without seeing other partners' accounts.

How It Works

1. You create a Channel Account from your Control Account in WACM.

2. You assign a user to the Channel Account. They receive an email invitation.

3. The Channel Account user logs into WACM and creates Sub-Accounts for their end customers.

4. All billing rolls up through the Channel Account to your Control Account.

5. You can track per-Channel Account usage and generate sub-invoices.

Channel Account features include:

• Per-partner usage reporting and CSV/Excel/JSON export

• Storage quota management per Channel Account

• Data cards showing paid accounts, trial accounts, average storage, and total storage

• Assign or reassign existing Sub-Accounts to Channel Accounts

For complete documentation, refer to the Channel Accounts Product Guide and Managing Multiple Partners Under One RCS Contract.

Custom Cloud Console (CCC)

CCC is a white-labeled version of the Wasabi Management Console. Your customers interact with a branded interface (your logo, your colors) instead of the standard Wasabi Console.

Capabilities include:

• White-labeled interface customizable at the Control Account level

• Channel Accounts inherit your branding automatically

• Bucket and object management for end customers

• S3 access key generation and management

• SSO support via OpenID Connect or SAML

• Self-service Sub-Account signup form integration

• Usage statistics and monitoring

• Multi-region support

For complete documentation, refer to Getting Started With CCC and CCC With Channel Accounts.

Custom Storage URLs

Replace the default Wasabi S3 endpoint (s3.wasabisys.com) with your own branded domain (for example, s3.yourcompany.com). Your customers connect to storage using your domain, and the Wasabi infrastructure is invisible.

Setup Overview

1. Choose a subdomain for each region (for example, s3.us-east-1.yourcompany.com).

2. Create three DNS CNAME records (SSL verification, path-based access, and virtual-host access).

3. Wasabi provisions an SSL certificate for your domain.

4. Once live, your customers use your branded URL for all S3 operations.

Requirements

• Must be an approved Wasabi OEM partner

• Each storage region requires its own custom URL

• Domain must be a subdomain (for example, s3.yourdomain.com), not a bare root domain

For complete documentation, refer to Custom Domains.

WACM Connect API

The WACM Connect API provides programmatic access to all WACM functionality, allowing you to automate account management and integrate it into your own systems.

You can automate:

• Create, read, update, and delete Sub-Accounts and Channel Accounts

• Provision trial accounts that auto-convert to paid

• Query storage utilization and billing data per account or per bucket

• Manage account members and permissions

• Retrieve invoices and usage reports

Authentication: API key-based, available from your WACM Control Account settings.

For complete documentation, refer to WACM Connect API Reference and API Account Types.

Wasabi S3 API and SDK Guides

Wasabi is fully compatible with the AWS S3 and IAM APIs. Any application that works with Amazon S3 works with Wasabi. No code changes are required. Wasabi has integration guides for all major AWS SDKs and tools:

Since Wasabi is S3-compatible, any other tool or library that supports Amazon S3 will also work with Wasabi. See the full list of AWS SDKs, tools, and services compatible with Wasabi.

Wasabi S3 endpoint format: s3.<region>.wasabisys.com (or your custom domain if configured)

For complete documentation, refer to Wasabi S3 API Reference and Storage Regions and Service URLs.

Common OEM Integration Models

As an OEM, you integrate Wasabi storage into your own product. Your customers buy your solution, and Wasabi is the storage engine behind it. The integration model you choose depends on how you deliver your product.

Single-Product Integration

Your product connects directly to Wasabi storage. You use a single Control Account with WACM to provision and manage a Sub-Account for each of your customers. Use the WACM Connect API to automate account provisioning from within your own platform, so customers get storage as part of your onboarding flow.

An example is a backup software vendor whose product stores customer backups in Wasabi. When a customer signs up, the vendor's platform automatically provisions a Wasabi Sub-Account via the API.

Platform Integration With Your Own Reseller Network

You build Wasabi into your platform and distribute your product through your own reseller network. Each reseller gets a Channel Account in WACM so they can provision and manage storage for the customers they bring on. All billing consolidates to your Control Account.

An example is a surveillance platform sold through regional security integrators. Each integrator gets a Channel Account to manage their installed customer base, while the platform vendor maintains oversight and consolidated billing.

Hybrid—Direct and Reseller

You sell your product directly to some customers and through resellers to others. Both models work simultaneously. Direct customers are Sub-Accounts under your Control Account, while resellers each get a Channel Account to manage their own customers.

All integration models support both Pay-as-you-go and Reserved Capacity Storage (RCS) pricing.

Branding Options

Getting Started

1. Apply for the OEM program. Contact the OEM team to discuss your use case and get approved.

2. Set up your Control Account. Once approved, you can self-activate your WACM Control Account and start configuring immediately.

3. Configure branding. Set up Custom Cloud Console theming and custom storage URLs.

4. Provision your first customer. Create a Sub-Account via WACM or the WACM Connect API.

5. Integrate. Use the WACM Connect API and S3 API to connect your platform.

For OEM Program details, refer to Wasabi OEM Partner Program.

Contact the OEM team (wasabi.com/contact-us/oem).