Confluent Cloud

Enable the Confluent Cloud connector in your fastn dashboard, then let each customer authenticate their own Confluent Cloud account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Confluent Cloud 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 Confluent Cloud account and only ever sees their own topics, streams and messages. 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 publishes an event within governed permissions.

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

Yes, within the retention the customer's own Confluent Cloud setup keeps. Consumer position is tracked per tenant, so a consumer that falls behind resumes from where it stopped rather than skipping ahead or starting over, which is the difference between a gap in your data and a duplicate in it.

Each customer authorises their own Confluent Cloud connection, so topics, credentials and consumer positions are theirs alone. That matters more here than in most integrations, because a misrouted message is delivered before anyone can review it.

A common starting point: produce messages to their own topics from 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 Confluent Cloud does not change your per-connector cost. You can start free with 3 connected accounts.