Solace: event distribution, messaging infrastructure and agent integration

Solace Event Broker carries events between applications and connects brokers into an event mesh spanning clouds and data centres. Hierarchical topics, queues and routing determine which consumers receive each publication. In this product name, “broker” means messaging middleware: an order event can travel through it, while the financial application remains responsible for its trading workflow.[1]

Guaranteed messaging uses a message spool and durable queues to retain accepted work across restarts and slow consumers. Exclusive queues use one active consumer; non-exclusive queues distribute work among consumers. Capacity still matters: an exhausted spool or another resource limit can prevent acceptance, in which case the publisher does not receive an acknowledgment.[5]

Event Portal’s event APIs are design artefacts with selected event versions and associated schemas. JSON or YAML exports can include service-plan, server and binding details. Only Draft versions can be edited directly; released definitions are normally evolved through a new version. Export naming strategies resolve name collisions but do not automatically rewrite references inside schema content, so renamed schema references need attention.[6]

SEMP provides management APIs with authentication on every request. OAuth bearer tokens and management-user credentials are supported. Permissions separate global resources from Message VPN resources; a global administrator can modify all resources, while narrower roles can manage an assigned VPN. Read and write requests are also checked against the attributes being accessed.[16]

The current pricing page separates platform package, event-broker capacity and count, application services, and the services subscription. Foundation, Accelerate and Scale describe package choices. Enterprise prices require a quotation. Fixed subscriptions and annual drawdown licensing are available; micro-integrations are priced per integration and can include multiple flows.[7]

Under the MSA, invoices are normally issued in advance in USD, with undisputed amounts due within 30 days of the invoice date; customer taxes are additional. Renewal increases may equal the greater of 5% or the preceding twelve-month US CPI increase. Subscriptions ordinarily renew for one year unless notice arrives at least 30 days before expiry, subject to the order.[8]

The cloud schedule distinguishes a Solace-controlled cloud account or dedicated VPC from a Customer Private Region running in customer-controlled Kubernetes infrastructure. On-premises use brings customer responsibilities for the operating environment. The agreed region, capacity and deployment rights therefore need to match the architecture being procured.[9]

Self-managed Standard software supports up to 1,000 client connections and an 800 GB spool, but its published non-production restriction remains decisive. Enterprise supports production deployments and a larger capacity envelope. The product page lists Kubernetes, containers, virtualisation and major cloud environments; actual sizing and operations remain deployment-specific.[3]

The current direct offer advertises a free 30-day test drive.[7]

The separate Online Trial Agreement defaults to 90 calendar days unless the order or an agreed extension specifies otherwise. It limits use to non-commercial, non-production evaluation with non-production data, and does not oblige technical support. These are different scoped terms, so the offered trial and its accepted order should establish the actual period. On expiry, use must cease and software be purged or hardware returned unless a paid subscription is agreed.[11]

The Cloud Service Schedule’s daily backup and recovery undertaking expressly excludes Customer Message Data. The technical backup guide directs message-backup requirements toward replication. A procurement specification should distinguish recovery of the service and its configuration from recovery of the actual messages carried through it.[9][12]

The published product-support plan operates 24/7/365. Initial response means an engineer acknowledging receipt, measured from initial contact; Severity 1 and 2 clocks require a telephone call. Acknowledgment is separate from restoration.[14]

The SLA publishes 5% service credits from 98% to below the applicable target and 15% below 98%. Claims must be submitted in writing within two months of the downtime. Scheduled downtime and listed exclusions apply, including HA switchovers of up to 60 seconds. Falling below 98% in two of three consecutive months permits termination of the SLA on notice; that clause is scoped to the SLA.[15]

Rolling and long-term-support broker releases receive two years of Full Support. APIs receive four years from first general availability; supporting software outside Solace Cloud receives three years from its first general availability. New features can require additional licences and may have platform restrictions.[14]

Messaging-client ACL profiles govern connections and publish/subscribe topics after authentication. The preconfigured Default profile is unrestricted and is assigned when another profile is absent. A further boundary matters for queue consumers: subscribe-topic ACLs are not checked when a client binds to a queue or topic endpoint. Binding to an endpoint carrying a disallowed topic can therefore bypass that topic restriction; endpoint access must be designed alongside topic rules.[17]

Management-session revocation also needs operational care. The SEMP documentation says changes to external LDAP or RADIUS user configuration do not automatically delete existing sessions; administrators must do that manually when required. OAuth requests use bearer authentication rather than these session cookies.[16]

Agent Mesh is permissive in a fresh deployment until RBAC is enabled. Enforced scopes can constrain agent and workflow invocation, including delegated and scheduled work. Platform-management and analytics HTTP enforcement additionally requires authentication; an unauthenticated development identity is not equivalent to a fully controlled production identity.[18]

Tools can execute actions in external systems. Most built-in tools inherit the agent’s invocation authority, with specific exceptions such as sending email. Custom tools can declare required scopes, checked before model exposure and execution. Built-in code runs in-process; remote Python or Go tools run in the separate Secure Tool Runtime. This is configurable execution authority, rather than a universal human-approval requirement.[19]

Solace Corporation is the supplier identified in the MSA. A conflicting provision in an order executed by both parties takes precedence; product schedules then govern their applicable offerings.[8]

Its published headquarters is 4000 Innovation Drive, third floor, Ottawa, Ontario, Canada. The commercial contact route offers an initial requirements conversation followed by a tailored demonstration.[20]

On 5 May 2026, Bridge Growth Partners announced the closing of a Solace continuation vehicle with US$790 million in commitments, co-led by Apogem Capital, Golub Capital, HSBC Asset Management and Schroders Capital. Bridge Growth Partners III participated and HOOPP rolled its existing minority position. The announcement traces Bridge Growth’s initial control investment to 2016.[21]

A November 2023 announcement described Finalto replacing legacy messaging infrastructure with Solace PubSub+ Platform. The stated deployment combined appliances and software in London, Copenhagen, New York and Singapore, intended to distribute market data and pre- and post-trade events across front, middle and back offices. This is a dated customer-project account: the announcement describes work being deployed, rather than independently establishing present completion or measured latency.[22]

Operator

Solace Corporation

Service scope

Enterprise event distribution, persistent messaging, integration and agent infrastructure.

Customer types

Banks; Capital-markets firms; Brokers; Enterprise technology teams

Delivery

SaaS; On premises; Hosted; Managed service; API

Pricing publication

Public and quoted pricing

Headquarters

Ottawa, Ontario, Canada

Platforms

Solace Event Broker; Solace Cloud; Solace Event Portal; Solace Agent Mesh

Pricing scope

Enterprise quotation and capacity commitments; free non-production Standard software and scoped trials.

Implementation

Managed cloud or customer-operated deployments, messaging clients and configuration APIs.

Support

24/7 product support with severity-specific initial-response conditions.

Permissions and regulatory scope

Messaging technology supporting financial workflows; customer trading and regulatory duties remain separate.

Provider metadata checked 21 Oct 2026Source 2Source 8Source 1Source 7Source 3Source 12Source 14Source 22Source 20

A transport acknowledgment confirms receipt by the messaging layer; an application acknowledgment indicates processing is complete and permits removal from the queue. While a consumer remains connected, the broker waits indefinitely for its application acknowledgment. An unacknowledged message can be redelivered when the client disconnects or its flow closes. A transport-level success should therefore not be treated as confirmation that the trading or accounting operation has completed.[23]

The JavaScript guide explains that replication-group message IDs identify a particular copy on a specific queue or endpoint within a replication group. For deduplication across an entire workflow, it recommends a publisher-generated unique identifier in the payload. Applications that store processed-message IDs need to make the business update and ID storage atomic to avoid inconsistent retry outcomes.[24]

Replay is an enabled log with a storage quota, not a fixed-duration archive. The oldest entries are trimmed at 90% of its configured quota. Replay can target non-partitioned queues or topic endpoints from the oldest available entry, a date or a replication-group ID. Topic filters can exclude messages from the log while still delivering them normally; those excluded events cannot later be replayed from that log.[25]

The MSA permits order termination on 60 days’ written notice without a general prepaid-fee refund. Export requests must arrive during the term or within 30 days after the subscription ends and exclude Customer Message Data. Afterwards, retention is no longer required and deletion follows documentation, subject to law. Transition assistance is chargeable under an agreed statement of work, for at most six months after agreement termination.[8]

Cloud service deletion is irreversible and requires a Mission Control Manager or Administrator. A protected service cannot be deleted, and a service must first be removed from its event mesh. Deletion stops client access. These controls make the application cutover and independent configuration/message recovery arrangements consequential parts of an exit plan.[26]