Content & Documents · Integration

Nasuni

Add Nasuni to your product for your customers, and give your AI agents governed access to it.

Embed a Nasuni integration so your product works with the files a customer already keeps in their own Nasuni environment instead of asking them to copy data somewhere you can reach. Nasuni is hybrid cloud file storage: active data sits on edge appliances while the authoritative copy of every file and its metadata lives in the customer's own cloud object storage under the UniFS global file system, and volumes, shares and snapshots are the units their administrators actually work with. Each customer connects their own environment with their own access key, so reads and writes run under their credentials and stay scoped to their tenant. fastn owns the auth, retries, pagination and API upkeep, and the same governed connection serves your product features and your AI agents.

Start freeBook a demo

In your product

Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.

Let customers connect their own Nasuni environment so your product can read and write files in the volumes and shares they already use, with no per-customer code.

Write output your product generates straight back into the customer's own file storage rather than holding it somewhere they cannot govern.

Read volume, share and snapshot detail per tenant so your product can show where a file lives and which point in time it came from.

Support the long tail of customer estates, where each one has its own volumes, appliances and share permissions, as configuration rather than a branch in your code.

For your AI agents

Governed, audited access for the agents you build, through the MCP server.

An agent finds and reads the right file in one customer's Nasuni volume within scoped permissions, with every read audited.

An agent files a generated document into the share a customer nominates, with the write attributed to the tenant that authorised it.

An agent explains which snapshot a version of a file came from without anyone opening the console.

Example prompt

Find the latest signed copy of this contract in our Nasuni volumes and tell me which snapshot it came from.

Set up Nasuni in 4 steps

  1. 01Enable the Nasuni connector in your fastn dashboard.
  2. 02Have each customer supply an access key for their own Nasuni environment so calls run under their credentials.
  3. 03Map the volumes, shares and file paths your product uses, per customer, as configuration.
  4. 04Call it from your product and expose the same connection to your agents through the MCP gateway.

Why teams use the Nasuni integration

What you get by embedding it with fastn instead of building it yourself.

  • Ship a Nasuni integration without building it. Your customers connect their own Nasuni 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 Nasuni update is not your on-call problem.
  • One integration serves your product and your agents. The same governed Nasuni 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

MarketingHR & People OpsOperations

Compare with

EgnyteBoxDropbox

Often used alongside

Tools the same teams tend to run next to Nasuni, across other categories.

ShopifyStripeJiraAsana

Nasuni integration FAQ

How do I add a Nasuni integration to my product?

Enable the Nasuni connector in your fastn dashboard, then let each customer authenticate their own Nasuni account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Nasuni client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Do my customers each connect their own Nasuni account?

Yes. Every connection is scoped to the individual customer, so each authorises their own Nasuni 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 Nasuni 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 finds and reads the right file in one customer's Nasuni volume within scoped permissions, with every read audited.

Who maintains the Nasuni integration?

fastn does. When Nasuni 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 Nasuni integration run under?

Each customer's own Nasuni grant. Where Nasuni 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 Nasuni automatically?

Where Nasuni 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 Nasuni integration?

A common starting point: connect their own Nasuni environment so your product can read and write files in the volumes and shares they already use, with no per-customer code. 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 Nasuni integration cost?

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Nasuni does not change your per-connector cost. You can start free with 3 connected accounts.

Add Nasuni to your product

Start free with 3 connected accounts. No sales call required, and no per-customer integration code.

Start freeRead the docs
← All integrations