Walrus Console Goes Live as Managed Layer for AI Data

High attention and emotional sentiment detected.

Console lets developers upload files and manage folders. It also connects that data to AI tools through an API key or an MCP server. It handles the wallet, the WAL payments, and the storage renewals in the background. So builders never touch the underlying protocol directly.

What Walrus Console Does

The official blog post calls Console “the new managed way to build on Walrus.” The docs call it “the developer-first interface for interacting with the Walrus network.”

The app lives at console.walrus.xyz. Sign-in works through Google or Apple. Those two identities map to separate accounts and do not share data.

Inside, users get file and folder management, API keys, and an MCP server. It works with Claude Code, Cursor, Codex, and Claude Desktop. Console also surfaces memories stored through Walrus Memory. So developers can see which agents use a record and when it expires.

Files uploaded through Console stay portable. According to the blog, they are “ordinary Walrus blobs and stay retrievable through the protocol directly.” In other words, the data does not get locked inside the dashboard.

How the Managed Layer Works

Walrus operates a decentralized blob-storage network. A committee of storage nodes stores the data, while the Sui blockchain handles coordination and payments. Users pay for storage with the WAL token.

Raw Walrus asks a lot of a developer. You need a client, a wallet, epoch selection, and WAL to pay for storage. Console hides all of that.

Instead, the managed layer provisions accounts and wallets, pays for storage, and tracks metadata. It then exposes a dashboard, an API, and an MCP server. The API base URL is api.console.walrus.xyz, and bearer keys carry an “hbr_” prefix. Console also sponsors gas through Enoki.

Developers who want epoch-level control still use the existing Walrus CLI and SDKs. So Console is an extra surface beside the protocol, not a replacement for it.

Who Built Walrus Console

The Walrus Foundation published Console. Walrus was developed at Mysten Labs as its second major protocol after Sui.

Kimberly Logan, Head of Product at the Walrus Foundation, is the named executive on the announcement. “Walrus Console is for builders whose edge lives in their data,” she said in the launch blog. She added that data and agent memory become “a first-class asset: one that moves with them, has built-in protections, and can be independently verified.”

Adeniyi Abiodun, co-founder and chief product officer at Mysten Labs, also called it live. “Walrus console is LIVE,” he posted on X. “This is how we take Walrus Protocol to everyone building with AI.”

The MCP package, @mysten-incubation/walrus-console-mcp, is MIT-licensed and sits in the Mysten Labs incubation SDK repo. It was published on npm about a day before the launch.

Encryption and the Centralization Question

Console offers private folders with client-side encryption. According to the overview docs, every file in a private folder is encrypted with Seal before upload. “Console stores ciphertext only and never sees your plaintext or your decryption keys,” the docs state.

The MCP docs go further. “Encryption, decryption, and signing all happen locally,” they say. The service private key signs on-chain access grants and unwraps Seal keys on the user’s own machine.

Still, “managed” and “decentralized” pull in different directions here. The bytes and availability proofs sit on Walrus nodes.

WAL Token and Usage So Far

WAL traded around $0.037 on October 7, according to DefiLlama. That put the market cap near $97 million, against a fully diluted value of roughly $185 million. Circulating supply sits at 2.617 billion of a 5 billion max.

The token has had a rough year. It hit an all-time high near $0.76 in May 2025, then an all-time low near $0.02 in August 2026. So it trades down about 90% from the peak.

Usage on Walrus is still modest. DappAtlas cited DefiLlama fee data on October 7. It showed about $120 in fees over 24 hours and roughly $3,234 over 30 days. So the AI-storage narrative is big, while the on-chain footprint remains small.

Walrus repriced underlying storage in June 2026 to $0.023 per gigabyte per month. Users pay in WAL, billed on encoded size. Console then manages that WAL handling for them. This article is not financial advice.

What Walrus Console Leaves Unanswered

No Console-specific price appears in the launch post, product page, or API reference. The docs do list hard-looking caps. Each space allows 5 GB and five folders, and each upload is capped at 100 MiB. Yet the docs do not say whether that is a free tier or a product-wide limit.

Other gaps remain. Walrus has not named who operates the Console API and web app. It has not stated the service-level guarantee if that hosted layer goes down. There is also no public audit of the Console service or the incubation MCP package yet.

As of publication, no major outlet such as CoinDesk, The Block, or Bloomberg had covered the launch. The announcement is only hours old. So the clearest read on the quiet is “too early,” not consensus either way.

The blog lists more features ahead: shared company spaces, granular access controls, and native delegate-key management for Walrus Memory. For now, Console is the entry point the team says it will build everything else on. OCT will track adoption and pricing as the first independent usage data appears.