Summary

  • Wasabi created a dedicated AI business on 10 September, appointing Pinaki Mukherjee to lead strategy, partnerships and sales development.
  • Its channel model can separate storage from a GPU supplier while leaving account administration with that supplier. A standalone account is a different arrangement.

Independence has more than one customer

Wasabi's new AI business has an attractive message for a GPU cloud: buy storage from a company that is not also trying to sell your customer compute. The 10 September announcement puts Pinaki Mukherjee, senior vice president and general manager, in charge of AI strategy, partnerships and go-to-market activity from Silicon Valley. This is a change in commercial organisation, not an announcement of a new GPU service.

There are two customers in that pitch. The neocloud wants a storage supplier that does not compete for its core revenue. The AI company buying from the neocloud may want its data relationship to survive a change of compute supplier. Satisfying the first preference does not automatically satisfy the second.

Wasabi's neocloud offering makes the channel incentive explicit. It describes a storage-only business with no GPU or compute offering, and lets partners offer storage through their own branding and domain. Wasabi Account Control Manager, or WACM, and its integration tools support provisioning, usage reporting and account management. The partner can add a storage business without building the underlying service and keep a coherent customer-facing operation.

That is useful distribution, not evidence of a defective product. But a brand-neutral storage supplier and an independently administered customer account are different things.

The account sits somewhere

The distinction is visible in Wasabi's account documentation. A Control Account is the paying account and can manage channel accounts and sub-accounts. An optional channel layer can manage its own sub-accounts. The end user's sub-account is itself a Wasabi Console account; it is not simply a folder inside a GPU machine.

Administration nevertheless has a hierarchy. Depending on account type and permissions, the sub-account controls include credential resets, quota settings, suspension and deletion requests. Hard quotas can block uploads; soft quotas issue a notification without enforcing the limit. These are documented management powers, not evidence that any partner has abused them.

The payment chain matters too. Wasabi's account-control billing guide says sub-accounts inherit restrictions arising from the Control Account's billing status. Its example is uploads being disallowed after an unpaid control invoice passes its grace period. An AI customer's ingestion path can therefore depend on an upstream commercial account, even when the storage infrastructure is functioning. The document does not establish that every payment dispute stops reads or deletes data.

There is an alternative within the same product family. Wasabi documents a Standalone Account, created through the relevant WACM sign-up form, which is neither attached to nor billed through the partner's WACM account. Access to that capability depends on the partner's setup. It would be wrong to describe all Wasabi customers as captive sub-accounts, or to assume that a branded sign-up page tells the buyer which arrangement it has chosen.

A key is not a handover

Another boundary appears in the account-control API FAQ. Management keys and S3 storage keys have different purposes. Cancelling the account-control API subscription invalidates its control keys; existing sub-accounts continue to operate, while the parent loses its management and sub-invoice access. Cancellation is not the same operation as deleting those accounts. Nor does that FAQ describe an automatic transfer to a replacement administrator.

The practical question for an AI buyer is therefore specific: if compute moves, what happens to the storage account, its administrator, its billing relationship and its support path? The reviewed pages do not settle every transfer condition. Those conditions belong in the selected account arrangement and the commercial agreement, not in an inference from S3 compatibility.

Wasabi's new team can widen the market for independent storage. The stronger version of that proposition would make independence legible at both levels: a supplier that does not sell competing compute, and an account arrangement whose continuing authority the customer understands.