One place for your company’s S3 storage. No keys handed out.
Give staff access to S3, not access keys.
Staff sign in and see only the buckets and folders they were given, at READ, WRITE or FULL. Partners get links that expire. AI agents get the same limits. When someone leaves, one click and they are out, with nothing to rotate. Run it on your premises and it carries your company’s name, logo and domain.
Cloud: connect a bucket and invite a colleague in minutes. Plan a rollout: your premises, your brand, SSO, SCIM.
Every key you hand out is a key you have to chase.
- Keys on laptops and in chats. Keys stay with one owner, encrypted. Nobody you invite sees them, so a lost laptop or a leaked chat does not leak a bucket.
- Offboarding by key rotation. One page lists every grant. Revoke the person and they are out. No rotation, no hunt for who else had the key.
- Files copied out to share. Partners get a link from your bucket with a password and an expiry. No consumer file-sharing service in the middle.
- Keys pasted into AI tools. Agents get a token with a scope and an expiry, and every call they make is on record.
Your storage is in S3. Your people are not S3 experts.
So someone pastes a key into a chat, and someone else uploads the file to a personal drive. Both are now outside your control.
| Today, usually | With Stream Vessel | |
|---|---|---|
| Giving access | Access keys in a chat, an S3 client to install | An invite by email to one folder |
| Who can see what | Whatever the key allows | READ, WRITE or FULL, on a connection, a bucket or a folder |
| Sending to a partner | Download, then upload to a consumer file-sharing service | A link from your bucket, with a password and an expiry |
| Someone leaves | Rotate the keys everyone was using | Revoke their access in one click |
| Finding a file | Ask the one person who knows the bucket | Search a folder or the whole bucket |
| AI tools | A key pasted into an agent’s config | An MCP token with a scope, an expiry and an audit log |
Each team sees its folder. Nobody sees the keys.
The owner connects the storage once. Everyone else gets an invite to exactly what they need.
-
Scoped. Share a whole connection, one bucket or one folder, such as
finance/. - Levelled. READ to look and download, WRITE to upload and change, FULL to delete too.
- Under Shared with me. People see what was shared with them next to their own connections, and nothing else.
Answer “who can reach what” on one page.
The questions security and auditors ask, answered without a spreadsheet.
- Every grant in one list. The Shared access page shows who has what, at which level, across all your connections.
- Revoke in one click, or in bulk. Access ends immediately. Nothing to rotate.
- Every AI call on record. Each agent tool call is logged; each token has a scope, an expiry and a rate limit.
- Keys encrypted, never shown. AES-256 at rest. Invitees and agents never receive a storage key.
- Inside your network. Run on your premises, the whole data path stays on your network.
Your company’s own MCP server. AI agents, on your terms.
People will connect AI agents to company files either way. Give them a way that keeps keys out of agent settings, limits what each agent can reach and records what it did.
- No more than the person. An agent reaches only what its user was given, and the token can narrow that to listed buckets and folders.
- Levels and expiry. READ, WRITE or FULL, expiring in 30 days, 90 days, a year, on a date you pick or never. Revoke in one click.
- The clients people use. Claude and ChatGPT sign in with OAuth, no token to paste. Claude Code, Cursor and VS Code get a connect kit.
Everything people do with files, on storage you control.
- Browse and move. Folder tree, panes side by side, cut, copy and paste, drag and drop, undo.
- Upload anything. Files and whole folders, large files in parts, straight to your storage.
- Find it. Search a folder or a whole bucket.
- Open it. Images, video, PDF, text and logs in the browser; archives as folders.
Your company’s portal, not ours.
Run it on your premises and staff open your company’s storage portal, on your domain, behind your sign-in. Nothing in it points to us.
- Your company name and logo
- Your colours
- Your domain, such as files.yourcompany.com
- Your company sign-in
- Your welcome page and onboarding
- Your support and policy links
- Only the features you switch on
Start on Cloud today. Run it on your premises when you need to.
| Stream Vessel Cloud | On your premises | |
|---|---|---|
| Runs on | Our servers | Your servers, Docker Compose with PostgreSQL |
| Storage keys | AES-256, on our servers | AES-256, on your server |
| Reaches | Storage on the internet | Storage on the internet and on your private network |
| Domain and brand | streamvessel.com | Your domain, your company name and logo |
| Sign-in | Google, GitHub or email | Your company sign-in; SSO, SAML and SCIM |
| Price | Free | Free for small teams, Enterprise for the rest |
-
1
Connect your storage
Sign in to Stream Vessel Cloud and add your S3 storage once, as its owner.
-
2
Invite your teams
Give each team its bucket or folder at the level it needs.
-
3
Run it on your premises
Run the same thing on your servers when you need your domain, your sign-in or your private network.
For the whole company.
Run it on your premises and add what a company-wide rollout needs.
- SSO and SAML
- SCIM provisioning
- Org-wide admin
- Audit export and retention