Hybrid Cloud Managed Storage
Your clouds and on-site storage under one governed layer, safely open to AI
Keep connects the object storage your organization already owns and exposes folders in it as typed, permission-scoped mounts with a full file experience on top. You decide where files live, how they are encrypted, who can reach them and what may be uploaded. Allowances and retention inherit down your organization tree, and every product that produces files lands them through one governed path, readable by people and AI agents only under their own permissions.
Opening file storage to AI agents usually means handing them a bucket. Keep mounts the object storage you already own as vaults, shares, or encrypted lockers, applies the platform's permissions to every file for people and agents alike, and inherits allowances and retention down your organization tree. It works with AWS S3, Google Cloud Storage, Azure Blob, and S3-compatible storage.
- Vaults, shares, and lockers across S3, GCS, Azure Blob, and S3-compatible backends
- Encryption policies and key management for sensitive data at rest
- Retention policies with cleanup history and lifecycle controls
- Granular sharing on the same permission engine as the rest of the platform
- A full file browser and mount management in the browser
What you get
What Keep gives your team.
Your buckets, your connection
Connect Amazon S3, Google Cloud Storage, Azure Blob Storage or S3-compatible providers, each checked with a live write, read and delete test.
Vaults, shares and lockers
Mount folders read-only as vaults, read-write as shares, or encrypted as lockers, with conflict checks that stop two writable mounts overlapping.
A full file experience
Browse, upload, download and share by folder, with resumable uploads for large files, a recycle bin, and file version history that keeps earlier versions restorable.
Encrypted with your own keys
Files are sealed under the organization's own encryption keys before they reach the storage provider, so the cloud holds only ciphertext.
Allowances and retention that inherit
Set file count, total size and per-file limits per organization, product and person. A parent sets them once and a child can only tighten.
Upload policies and public links
Govern file types, screen uploads for personal data, and control public links with expiry, passwords and organization-level guard rails.
How it works
- 1
Connect your storage
Add an Amazon S3, Google Cloud Storage, Azure Blob or S3-compatible connection. Keep checks it with a live write, read and delete probe and reports a clear outcome.
- 2
Mount folders by type
Expose folders as read-only vaults, read-write shares or encrypted lockers. Conflict checks stop two writable mounts from overlapping on the same folder.
- 3
Set allowances and upload rules
Set file count, total size and per-file limits per organization, product and person, plus retention. Upload policies screen for personal data and flag, quarantine or refuse, and reviewers release withheld files.
- 4
Share, review, restore
Share a folder by path, or give outside collaborators an expiring, optionally password-protected link. Deleted files wait in a recycle bin and overwritten files stay restorable from version history.
Ask AI about Keep
Every Keep page has an Ask AI button. It opens a chat that already has the page, its rows, and your selection. Try asking:
- Which upload policies listed here quarantine files, and which ones refuse them outright?
- Which are the largest files in the folder I am browsing?
- Which mounts on this page are read-only vaults, and which are encrypted lockers?
How teams use it
- Keep all chat attachments and AI-generated files in your own bucket in a required region.
- Give an auditor read-only access to a folder through a vault, with every access recorded.
- Share a file outside the company with an expiring, password-protected link.