Skip to main content

What is Walrus Console?

Walrus Console is the developer-first interface for interacting with the Walrus network. It gives you a hosted place to store, manage, and serve data without running your own Walrus client or handling wallets and tokens directly. You sign in and upload your first file in minutes, then manage everything from one place; when you want programmatic access, you mint an API key.

How Walrus Console relates to Walrus​

Walrus is the underlying protocol: a decentralized network that stores data as blobs, coordinated onchain through Sui. You can use Walrus directly through the CLI and SDKs, which give you low-level control over blobs, storage epochs, and payments.

Walrus Console sits on top of that protocol as a managed developer surface. It handles the parts that are otherwise manual: account and wallet provisioning, storage payment, metadata, and a dashboard and API for organizing your data. Use the CLI and SDKs when you want direct protocol access, and use Console when you want a hosted, managed experience.

Core concepts: spaces, folders, and files​

Console organizes your data in three levels.

  1. A space is the top-level container tied to your account. Console creates a Personal Space for you automatically when you sign up. A space tracks how much storage you have used against your storage cap.

  2. A folder is a named container inside a space that holds files. All folders are private and encrypted with Seal.

  3. A file is an individual object that lives inside a folder. Uploads are asynchronous: you upload a file, then poll its status until Console confirms that Walrus stores it. Each file can carry metadata you define, which you can use later to search and organize your data.

Encryption and privacy​

warning

On Walrus, anyone who has a blob ID can read the bytes of a stored blob. Do not rely on obscurity for sensitive data.

Console private folders solve this by encrypting every file client-side with Seal before upload. Console stores ciphertext only and never sees your plaintext or your decryption keys. Setting up a private folder uses a short reserve, sign, and finalize handshake that provisions the folder's Seal access policy onchain. Encryption on upload and decryption on download both happen on your machine.

Asset types​

Console is built around a single navigation shell that treats your data as typed assets. Files and memory are both first-class asset types managed the same way.

Files are general-purpose objects you upload and retrieve.

Memory refers to Walrus Memory namespaces, the portable memory layer for AI agents. Connect your Walrus Memory account from the Memory tab to view your memories and delegate keys in Console. Managing memories and delegate keys happens on the Walrus Memory dashboard. See Walrus Memory in Console.

Accounts and sign-in​

You sign in through Google or Apple using Sui zkLogin capabilities. Console derives a Sui address from your identity and silently provisions a Pearl wallet (the embedded wallet Console manages for you), so you do not manage private keys or hold tokens to get started. There is no invite or waitlist: sign in and start storing data.

Identities from different providers map to separate accounts, so the Google and Apple identities of one person own separate data.

You own your data. Console does not migrate data you previously stored on Walrus outside the product; you re-upload it.

API keys and roles​

You mint API keys under Integrations in the Console web app, choosing a read_write or read_only role for each. A plain API key works with the MCP server and with any application you write against the API, but it cannot mint further keys. A Management API key mints keys programmatically instead, and cannot upload, download, or manage assets. The choice is not permanent, so you can create a Management API key at any time. Console shows the full key (prefixed hbr_) once, at creation, and cannot recover it afterward, so store it like a cloud secret access key. For what each role can do, see the API reference.

Alongside the API key, Console generates a service private key (prefixed suiprivkey1) in your browser and shows it once next to the API key. Console stores only the derived public address. You keep the private key locally and use it to sign the transaction that finalizes a private folder and to authenticate decrypt sessions with Seal. It does not need a token balance.

If a key leaks or you want a fresh one, use Rotate on the key in Integrations. Rotation is revoke-first: Console revokes the old key, mints a replacement with the same role and name and a new service private key, and shows the new secrets once. There is no overlap window, so anything using the old key stops working the moment you rotate and starts again when you paste in the new secrets. Rotate and Revoke are separate actions with separate confirmations.

Connect AI clients with the MCP server​

Console publishes an open source MCP server that exposes file and folder operations as tools for AI clients. See Connect AI clients with the MCP server for installation, the tools it exposes, and how it handles your credentials. After you create an API key, Console walks you through connecting your agent from the same screen. See Connect from the Console web app.

Walrus Memory in Console​

If you use Walrus Memory, connect your Walrus Memory account to Console from the Memory tab. Console verifies that you own the account, then shows your memories and the delegate keys your agents use. Console shows memory metadata only. It never reads or stores memory content.

This view is read-only. To manage memories and delegate keys, use the Walrus Memory dashboard. Console links you there from the Memory tab. Disconnecting your Walrus Memory account removes the connection and Console's copy of the metadata. It does not delete any memory.

Storage, epochs, and renewal​

Walrus storage is time-bound. You pay to store data for a number of storage epochs, and data expires when its storage runs out. Console manages epochs and payment for you rather than asking you to track them by hand.

Console extends the storage of your files automatically before it expires, so you keep your data without a manual renewal step. See Storage, Epochs, and Renewal.

Storage limits​

Each space holds up to 5 GB of storage and five folders, and each upload is capped at 100 MiB. Console manages WAL token handling on your behalf.

Delete your account​

You can delete your Console account from Settings, under Account Deletion. Choose Delete account, type DELETE to enable the button, then choose Permanently delete. Deletion permanently removes your folders, files, and API keys. Any MCP integration using one of those keys stops working immediately. It cannot be undone. Memories stored in Walrus Memory are not deleted and remain available outside Console. Only the link between the two accounts is removed.

What Walrus Console includes​

Walrus Console includes the following:

  • Google and Apple sign-in, and a Personal Space.
  • Private, Seal-encrypted folders, and file upload and download.
  • API keys, key rotation, and the MCP server.
  • Automatic storage renewal.
  • Account deletion.
  • Walrus Memory account connection, to view your memories and delegate keys.