Kaltura

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

Yes. Every connection is scoped to the individual customer, so each authorises their own Kaltura 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.

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 looks up a media entry and its metadata before answering a question about it.

fastn does. When Kaltura 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.

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

Where Kaltura 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.

A common starting point: browse and search their own media entries from inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

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