FEATURES / Event Indexing
/// Event Indexing
Search that updates the instant your objects change.
Storafleet keeps a fast, local search index of your objects. Turn on a token-authenticated webhook receiver and your provider pushes create and delete events the moment they happen — even for changes made outside Storafleet. Real-time where your provider supports events (AWS, R2, MinIO), browse-time indexing everywhere else.
Start for free/// How it works
Start with browse-time indexing
Out of the box, Storafleet indexes objects as you browse them and stores them in a local MongoDB-backed index. Global search works immediately on every provider — no setup required.
Enable the webhook receiver for your provider
For AWS (SNS), Cloudflare R2 (Worker), or MinIO (bucket notifications), turn on the per-fleet receiver. Storafleet shows a one-time secret and, on AWS, auto-confirms the SNS subscription for you.
Search stays current automatically
Your provider now notifies Storafleet on every create and delete. The index updates the instant objects change — even changes made outside Storafleet. Missed events self-heal on the next browse.
Local index, zero query-time API calls
Storafleet keeps a fast MongoDB-backed search index of your objects. Global search runs entirely against that local index — no provider API calls at query time, so results are instant.
Real-time push indexing
Turn on a per-fleet webhook receiver and your provider notifies Storafleet the instant an object is created or deleted. The index updates immediately — even for changes made outside Storafleet, like pipeline writes or SDK uploads.
Browse-time fallback that always works
By default the index refreshes at browse-time: objects index as you browse. It's the universal fallback that works on every provider, with or without real-time events turned on.
Provider-native event wiring
AWS delivers events via SNS (Storafleet auto-confirms the SNS subscription), Cloudflare R2 via a Worker, and MinIO via direct bucket notifications. Other providers fall back to browse-time indexing automatically.
Token-authenticated receiver you control
A one-time secret is shown when you enable the receiver. You can rotate it or disable it whenever you want. Only requests carrying the right token are accepted by your fleet's receiver.
Idempotent and self-healing
The receiver is idempotent, so duplicate deliveries are harmless. If an event is ever missed, the index self-heals on the next browse via the browse-time fallback — nothing drifts permanently out of sync.
/// Without Storafleet
Your search index goes stale the moment something changes outside the tool you're searching in. A pipeline drops 500 files, an SDK upload lands, an object gets deleted — and search has no idea until something forces a refresh.
- Objects created by pipelines or other tools don't show up in search until someone manually browses the bucket
- Deleted objects linger in search results until the next refresh
- SDK and CLI uploads are invisible to search even though they're already in the bucket
- Re-indexing means hammering provider list APIs at query time
- A single missed change can leave search quietly wrong with no way to know
/// With Storafleet
A local index that stays current. Real-time push events on AWS, R2, and MinIO update it instantly; browse-time indexing covers every other provider and self-heals anything that slips through.
- Provider events index new and deleted objects in real time — including changes made entirely outside Storafleet
- Global search runs against a local MongoDB-backed index, with zero provider API calls at query time
- AWS uses SNS (subscription auto-confirmed), R2 uses a Worker, MinIO uses bucket notifications; others fall back to browse-time
- A one-time secret authenticates the receiver — rotate or disable it whenever you need to
- Idempotent delivery makes duplicate events harmless, and any missed event self-heals on the next browse
/// When you'll use this
Keeping search current on a pipeline-driven bucket
An ETL pipeline writes thousands of objects to a bucket on a schedule, and nobody touches Storafleet during the run. With real-time indexing on via SNS, every new object shows up in global search the moment the pipeline writes it — no waiting for someone to browse the bucket first.
Key featureReal-time push indexing for changes made outside Storafleet
Upload via SDK, find it in Storafleet seconds later
Your team uploads assets through the AWS SDK and CLI but searches for them in Storafleet. Before, a freshly uploaded file wouldn't appear until someone browsed its bucket. With the token-authenticated receiver on, the index updates on upload, so 'find that file someone just dropped' actually works.
Key featureToken-authenticated webhook receiver updating the local index
Real-time where it's supported, reliable everywhere else
Your fleets span AWS, Cloudflare R2, MinIO, and a couple of providers without event support. You enable push indexing where it's available — SNS, Worker, bucket notifications — and the rest fall back to browse-time. Either way, search stays correct, and idempotent delivery means duplicate events never corrupt the index.
Key featureReal-time on AWS/R2/MinIO, browse-time fallback everywhere else
Your storage estate deserves a control plane.
Join the DevOps teams and founders who run every cloud's buckets from one control plane.
Free plan · No credit card · 50+ cloud providers · Cancel any time