Streaming & Messaging · Integration
Solace PubSub+
Add Solace PubSub+ to your product for your customers, and give your AI agents governed access to it.
Solace PubSub+ is an event broker built to move messages between systems that were never designed to talk to each other, which is why it speaks several protocols at once and why a topic hierarchy rather than a queue name is usually how things are addressed. An embedded integration publishes to a customer's own topics, consumes from their queues, and lets your product take part in an event mesh that already spans their estate. Ordering and redelivery are what you have to get right: a consumer that acknowledges too early loses a message, and a duplicate delivery has to be tolerated rather than assumed away. Each customer supplies their own broker host, message VPN and credentials, so nothing crosses tenants. fastn holds those credentials and keeps the connection maintained.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own broker and message VPN so your product joins the event flow they already run.
Publish an event to their topic when something happens in your product, so their systems react without polling you.
Consume from a queue so work raised elsewhere in their estate reaches your product in order.
Support each customer's own topic hierarchy as configuration rather than a naming scheme you impose on them.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent publishes an approved message to a nominated topic, with the publish logged per tenant.
An agent reads recent messages from a queue to explain what a downstream system was sent.
An agent reacts to an event and runs the next step of a workflow within scoped permissions.
Example prompt
Read the last few messages on this queue and tell me which downstream system should have picked them up.
Set up Solace PubSub+ in 4 steps
- 01Enable the Solace PubSub+ connector in your fastn dashboard.
- 02Have each customer supply their own broker host, message VPN and credentials.
- 03Agree which topics your product publishes to and which queues it consumes from, then map the message payloads.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Solace PubSub+ integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Solace PubSub+ integration without building it. Your customers connect their own Solace PubSub+ account inside your product and work their topics, streams and messages there, with no per-customer code on your side.
- Handle the part that actually costs time: ordering and replay are the whole problem: a consumer that falls behind must be able to resume without losing or double-processing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Solace PubSub+ update is not your on-call problem.
- One integration serves your product and your agents. The same governed Solace PubSub+ connection powers in-product features and gives AI agents scoped, audited access, so you move events between your product and your customers' systems without either side polling without wiring it twice.
Used by these teams
Compare with
Apache Kafka
RabbitMQ
Azure Service BusOften used alongside
Tools the same teams tend to run next to Solace PubSub+, across other categories.
Snowflake
Airtable
PostgreSQL
Anthropic ClaudeSolace PubSub+ integration FAQ
How do I add a Solace PubSub+ integration to my product?
Enable the Solace PubSub+ connector in your fastn dashboard, then let each customer authenticate their own Solace PubSub+ account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Solace PubSub+ client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Solace PubSub+ account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Solace PubSub+ 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.
Can AI agents use this Solace PubSub+ 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 publishes an approved message to a nominated topic, with the publish logged per tenant.
Who maintains the Solace PubSub+ integration?
fastn does. When Solace PubSub+ 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.
Can my product replay Solace PubSub+ messages after an outage?
Yes, within the retention the customer's own Solace PubSub+ 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.
How is one customer's stream kept separate from another's?
Each customer authorises their own Solace PubSub+ 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.
What can I build with the Solace PubSub+ integration?
A common starting point: let each customer connect their own broker and message VPN so your product joins the event flow they already run. 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 Solace PubSub+ integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Solace PubSub+ does not change your per-connector cost. You can start free with 3 connected accounts.
Add Solace PubSub+ to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.