Skip to main content

Managed Relayer

A managed relayer is a simpler experience for teams that want to get started without running infrastructure. If a managed relayer endpoint is available for your environment, it gives you the fastest path to integration.

Walrus Foundation hosted endpoints​

NetworkRelayer URL
Production (Mainnet)https://relayer.memory.walrus.xyz
Staging (Testnet)https://relayer.dev.memwal.ai

Minimal config​

Source: relayer/public-relayer.md 
import { MemWal } from "@mysten-incubation/memwal";

const memwal = MemWal.create({
  key: "<your-ed25519-private-key>",
  accountId: "<your-memwal-account-id>",
  serverUrl: "https://relayer.memory.walrus.xyz",
  namespace: "demo",
});

What to know​

  • Shared App ID: All users of the managed relayer share the same Walrus Memory package ID. Your own owner + namespace (Memory Space) isolates your data, but all users share the underlying deployment.
  • Trust assumption: The relayer receives your plaintext to embed it and encrypt it with Seal on every write, and decrypts it with Seal on every recall, so it sees your data in plaintext on both paths. By using the managed relayer, you're trusting the Walrus Foundation-hosted instance with that data. See Trust and Security Model for details.
  • Availability: The Walrus Foundation provides the managed relayer as a public good without SLA guarantees.

Storage costs​

The managed relayer covers WAL storage fees and SUI gas through its server wallets and configured gas sponsor. Account holders do not pay gas or WAL for these relayed writes. Account ownership does not determine which wallet pays for an upload. The shared service applies usage limits.

With a self-hosted relayer, you fund the relayer deployment.

If you need full control over the trust boundary or your own dedicated instance, see Self-Hosting.

Where does encryption happen?​

With the default MemWal client, the managed relayer receives your plaintext, generates embeddings, and encrypts each item with Seal before storing it on Walrus. You do not manage keys in this flow.

To keep plaintext on the client, use MemWalManual from @mysten-incubation/memwal/manual. The client generates embeddings and performs Seal encryption locally, and the relayer only receives encrypted payloads and precomputed vectors. See MemWalManual for the client-managed flow.