A Wasabi browser and file manager.
Stream Vessel lets you browse and manage Wasabi buckets through a file-manager-style interface, over Wasabi's S3-compatible API. Everyone on your team can work in the buckets from a browser, without installing a desktop client or sharing the account's keys.
What Stream Vessel adds to Wasabi
Teams on Wasabi usually choose between the web console and a desktop client installed per person. Stream Vessel is a browser app and a Chrome extension with the explorer, search, editor, metadata and share links, plus sharing by email and AI access on Cloud.
Stream Vessel is an S3 browser and file manager for AWS S3 and every S3-compatible provider. Wasabi is a preset in the connection dialog.
Connection details
| Endpoint | The region endpoint, for example s3.eu-central-1.wasabisys.com |
|---|---|
| Region | The Wasabi region of the bucket, for example eu-central-1 |
| Credentials | A Wasabi access key and secret key, ideally for a sub-user with a limited policy |
Connect Wasabi to Stream Vessel
- In the Wasabi console, create a sub-user with programmatic access and a policy limited to the buckets Stream Vessel should reach, then create an access key for it.
- In Stream Vessel, add a connection, pick Wasabi, choose the region and paste the keys.
- Test the connection, save, and your Wasabi buckets appear in the explorer.
What you can do with Wasabi in Stream Vessel
The same features work on every provider. The editions differ: sharing and AI access need a Stream Vessel Cloud account. All S3 browser features.
| Feature | Stream Vessel Cloud | Chrome extension |
|---|---|---|
| Browse buckets and folders: tree, file list, s3:// breadcrumbs | ✓ Available | ✓ Available |
| Several panes side by side, each on its own connection | ✓ Available | ✓ Available |
| Upload files and folders, multipart for large files | ✓ Available | ✓ Available |
| Copy between connections and providers | ✓ Available | ✓ Available |
| Rename objects and folders | Soon | Soon |
| Edit text and code in place | ✓ Available | ✓ Available |
| Read and edit object metadata | ✓ Available | ✓ Available |
| Search a folder or a whole bucket | ✓ Available | ✓ Available |
| Presigned links with an expiry, single and bulk | ✓ Available | ✓ Available |
| Share a connection, bucket or folder with people | ✓ Available | – Not available |
| AI access over MCP | ✓ Available | – Not available |
| Send to and import from Google Drive | ✓ Available | ✓ Available |
Sharing, AI access and transfers with Wasabi
- Share Wasabi access without sharing keys. On Stream Vessel Cloud, share a Wasabi connection, bucket or folder by email at READ, WRITE or FULL, and revoke it in one click. How secure S3 sharing works.
- Give AI agents access to Wasabi. An MCP token with a tier and an expiry lets Claude Code, Cursor or another MCP client work in your Wasabi buckets, with every call logged. S3 access for AI agents.
- Copy between Wasabi and other storage. Open Wasabi next to any other connection and drag or paste to copy across providers, or send files to Google Drive. Cloud storage transfers.
- Keys stay yours. In the Chrome extension your Wasabi keys never leave your browser. On Cloud they are encrypted with AES-256 and never shown to the people or agents you give access. Where keys are stored.
Good to know about Wasabi
- Use the bucket's own region endpoint. Wasabi buckets live in one region, and requests should go to that region's endpoint. If a bucket lists but objects fail to load, check the connection's region.
- Minimum storage duration. Wasabi bills a minimum storage duration for every object. A delete, or a move (a copy and a delete), of a recently uploaded object can still be billed for the remaining days. Stream Vessel asks before deleting; check your Wasabi plan's terms.
- Searching is cheap here. Wasabi does not bill API requests, so the cost-aware pause during long searches matters less. Choose "don't ask again" for the connection and search runs to the end.
- Share without sub-users for everyone. On Stream Vessel Cloud, share a bucket or folder by email at READ, WRITE or FULL instead of creating a Wasabi sub-user per person.