Content & Documents · Integration
Wasabi
Add Wasabi to your product for your customers, and give your AI agents governed access to it.
Wasabi is hot cloud object storage with a deliberately plain model: one storage class, no egress or request charges, and an S3 compatible API so existing tooling points at a Wasabi endpoint instead of an Amazon one. For an integration that plainness is the feature, because there are no access tiers to choose between and no retrieval delay to design around, so a read is simply a read. Two facts do bite. A bucket lives in one region and is reached through that region's endpoint, so which host to talk to is one of the things a customer tells you at setup. And a minimum storage duration applies, which means an object deleted shortly after it was written is still charged for the full period, so lifecycle rules deserve a moment's thought rather than a copied default. Each customer supplies their own access key and secret, and fastn holds those per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Wasabi buckets so files your product handles stay in storage they control and pay for.
Write output your product generates straight into a bucket, addressed through the region endpoint that bucket actually lives in.
Read objects on demand without budgeting for egress, which changes what is reasonable to serve directly from storage.
Set lifecycle rules deliberately, since the minimum storage duration means an early delete is not an early saving.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent lists objects under a prefix and reads the one it needs, scoped to the bucket it was permitted.
An agent writes a generated file into a nominated bucket, with the key it wrote recorded.
An agent reports what exists under a prefix without downloading everything to find out.
Example prompt
List what is in this bucket under the reports prefix and tell me when the newest object was written.
Set up Wasabi in 4 steps
- 01Enable the Wasabi connector in your fastn dashboard.
- 02Have each customer supply their own access key and secret so objects are written into storage they own.
- 03Decide which buckets, prefixes and region endpoints your product uses, and set lifecycle rules with the minimum storage duration in mind.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Wasabi integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Wasabi integration without building it. Your customers connect their own Wasabi account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Wasabi update is not your on-call problem.
- One integration serves your product and your agents. The same governed Wasabi connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Azure Blob Storage
Nasuni
DropboxOften used alongside
Tools the same teams tend to run next to Wasabi, across other categories.
Shopify
Stripe
Jira
AsanaWasabi integration FAQ
How do I add a Wasabi integration to my product?
Enable the Wasabi connector in your fastn dashboard, then let each customer authenticate their own Wasabi account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Wasabi client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Wasabi account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Wasabi account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Wasabi integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent lists objects under a prefix and reads the one it needs, scoped to the bucket it was permitted.
Who maintains the Wasabi integration?
fastn does. When Wasabi changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose permissions does the Wasabi integration run under?
Each customer's own Wasabi grant. Where Wasabi holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Wasabi automatically?
Where Wasabi supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Wasabi integration?
A common starting point: let each customer connect their own Wasabi buckets so files your product handles stay in storage they control and pay for. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Wasabi integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Wasabi does not change your per-connector cost. You can start free with 3 connected accounts.
Add Wasabi to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.