Your storage, one product. Your brand, your servers.
Give your customers more than storage: a product they sign in to every day.
Today a new customer gets an endpoint, a key and a hunt for a client. Give them a product on your domain instead: accounts, keys, buckets, files, sharing and AI access, wired into your API and running on your servers.
Price per terabyte is easy to compare. The product on top is not.
- Higher revenue per customer. A product people open every day is a product they upgrade.
- Accounts you could not win before. Agencies, studios and office teams buy storage they can open in a browser.
- Lower churn. Sharing, search and previews live on your storage. Leaving means losing them.
- Fewer tickets. No “which client should I use”, no “where do I put my keys”.
Skip the year of product work.
A storage product looks simple until the first customer with half a million objects in one folder.
| Build your own | Stream Vessel white label | |
|---|---|---|
| Time to launch | Quarters of front-end and back-end work | A finished product, wired into your API |
| Accounts and keys | A console for keys, then a client to find | One account; keys created for the customer, never pasted |
| Large buckets | A folder of 500,000 objects has to be paged and searched; it is the first thing that breaks | Paged listing, 1000 entries at a time, search across the whole bucket |
| Big files | Multipart, resume and progress to write | Multipart in parts, straight to your storage |
| Sharing | Hand out keys, or build it | Invites at READ, WRITE or FULL, public links with password and expiry |
| AI agents | Another project on the roadmap | A ready-to-use MCP server, scoped tokens and an audit log |
| Upkeep | A team to keep it current | Updates from us, on the release you choose |
One account, from sign-up to the first file.
Stream Vessel works through your platform’s API, so everything your customers do happens in your systems. No second registration, no keys to copy, no separate tool to learn.
- Sign-up and users. A customer who signs up with you has access right away. Users and team members come from your accounts.
- Keys made for them. Access keys are created, rotated and revoked through your API. Customers get access, not keys to paste.
- Buckets in place. Buckets are created and listed through your API and open on your endpoint, already connected.
- Your plans and limits. Quotas, usage and plan limits from your platform, shown where customers work with their files.
One adapter against your API. We write it.
You send us your management API docs and a sandbox. We build and test the adapter, and keep it working as your API changes.
- We build. The adapter for four kinds of calls: users, keys, buckets, quotas and usage.
- You run. The app, its database and the MCP server as containers behind your load balancer, next to your storage.
- You decide. Which features ship, which domain they live on, and when to take an update.
Inside your management console, or as your management console.
- Built into the console you have. Storage pages live inside your existing console, behind the same sign-in and in the same look. Customers move between billing and files without noticing a seam.
- The console, from Stream Vessel. No console yet, or ready to replace yours? Stream Vessel becomes it: accounts, team, keys and buckets next to files, sharing and AI access.
Win customers from other providers, with their data.
Customers stay with a provider they do not like because moving is hard. Yours copy their buckets across in the browser, in your product, on the day they sign up. No scripts, no tickets, no professional-services bill.
- Old storage next to the new. A customer adds the storage they are leaving as a second connection and sees both side by side.
- Drag buckets and folders across. Copy whole folders from the old storage into yours, with nothing to install.
- Every file accounted for. Progress for each file, and a retry for only what failed.
- Nothing lost on the way. Transfers between storages copy, never move, so the source stays intact until the customer has checked.
Everything for their files, running today.
Everything below runs in Stream Vessel Cloud for real users on real buckets. A white label is the same product, with your name on it.
- Browse like a desktop. Folder tree, panes side by side, cut, copy and paste, drag and drop, undo.
- Upload anything. Files and folders, multipart for large files, straight from the browser to your storage.
- Find it fast. Search a folder or a whole bucket, built for buckets with millions of objects.
- Open without downloading. Images, video, audio, PDF and text; zip and tar archives as folders; a code editor.
- Share without sharing keys. Invites at READ, WRITE or FULL to a bucket or folder; public links with a password and an expiry.
- On any device. The same product on phones and tablets, no install.
Make your storage the one AI agents can use.
Your customers are wiring AI agents into their work, and the agents need files. Hand them an MCP server for your storage on day one, under your domain.
- Every popular client. Claude and ChatGPT sign in with OAuth, no token to paste. Claude Code, Cursor and VS Code get a ready-made connect kit.
- 27 tools. List, search, read, write, copy, move and delete; links to share; multipart for large files.
- Access your customers can trust. Tokens limited to READ, WRITE or FULL, to the buckets and folders listed, and to an expiry. Never a storage key.
- Every call on record. An audit log of each tool call, rate limits per token, and revoke in one click.
Your servers, your data, your release schedule.
Stream Vessel runs in your data centre or your cloud account, run by you.
- Files stay on your storage. Uploads and downloads go between your customers and your storage, never through the app.
- Keys stay in your systems. Created through your API and held on your servers.
- Nothing comes back to us. No calls home. Analytics, if any, are yours to choose.
- No dependency on us. The core is open source under AGPL-3.0. If we went away tomorrow, your deployment keeps running.
Your customers sign in to your product. Nothing in it points to us.
- Your product name and logo
- Your colours
- Your domain, for the app and the MCP server
- Your sign-in
- Your terms and privacy policy
- Your support links
- Your welcome and onboarding
- Only the features you offer
One license per deployment. Your margin grows with your customers.
- No fee per customer. Sign up as many customers as you can sell to.
- No fee per terabyte. Your storage revenue stays yours.
- Integration included. We build and maintain the adapter for your API.
- Updates and support included. New releases from us, on the schedule you choose.
Three steps to your own storage product
The first vendors get a direct line to our engineers, a say in the roadmap, and partner pricing fixed for the term.
-
1
See it on your storage
Connect one of your buckets in Stream Vessel Cloud and use it as your customers would.
-
2
Talk to us
Send us your API docs. We reply with questions, then propose scope and a price.
-
3
Launch under your name
We build the adapter, you deploy on your premises. Your customers sign in to your product.
Running S3 for your own staff rather than selling it? The company S3 portal is for you.