solace-agent-mesh
Solace Agent Mesh is an open-source Python framework for building multi-agent AI systems that communicate through event-driven architecture. Agents can delegate tasks to each other, integrate with external systems, and execute complex workflows with minimal coupling.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | SolaceLabs/solace-agent-mesh |
| Owner | SolaceLabs |
| Primary language | Python |
| License | Apache-2.0 — OSI-approved |
| Stars | 5k |
| Forks | 267 |
| Open issues | 71 |
| Latest release | 1.28.4 (2026-06-29) |
| Last updated | 2026-06-29 |
| Source | https://github.com/SolaceLabs/solace-agent-mesh |
What solace-agent-mesh is
Built on Solace AI Connector (SAC) and Google's Agent Development Kit (ADK), SAM provides an asynchronous, event-driven runtime where agents discover peers via A2A protocol over Solace event brokers. Supports tool execution, file artifacts, dynamic embeds, and flexible gateway integrations (REST, Slack, web UI).
Get the solace-agent-mesh source
Clone the repository and explore it locally.
git clone https://github.com/SolaceLabs/solace-agent-mesh.gitcd solace-agent-mesh# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Python 3.10.16–3.13.x required; test compatibility early in your environment.
- Solace Platform event broker is a mandatory dependency; plan broker provisioning, clustering, and HA upfront.
- LLM API key and model selection baked into agent config; ensure cost controls and model governance.
- A2A protocol and agent discovery is automatic but requires careful naming/discovery strategy at scale.
- File artifacts and embeds provide useful defaults but custom metadata and resolution logic may be needed for complex use cases.
When to avoid it — and what to weigh
- Simple Single-Agent Chatbots — Event-driven architecture and orchestration add complexity. Simpler frameworks (LangChain, LlamaIndex) are more appropriate for single-agent use cases.
- Real-Time Latency-Critical Systems — Event-driven messaging introduces queuing and async delays. Systems requiring sub-100ms responses may need synchronous patterns instead.
- No Solace Platform Available — Framework is tightly coupled to Solace event brokers. Self-hosted or cloud deployments require Solace infrastructure; no built-in fallback to lighter transports.
- Minimal Operations/Infrastructure Team — Requires managing Solace broker, Python runtime, agent lifecycle, and monitoring. Organizations without DevOps maturity may find operational overhead high.
License & commercial use
Apache License 2.0. Permissive OSI-approved license allowing commercial use, modification, and distribution with attribution and liability disclaimers.
Apache 2.0 permits commercial use without royalties. However, verify whether your Solace Platform broker (if commercial) and any dependent LLM services impose separate licensing or cost constraints. Consult legal if bundling this with proprietary applications.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | High |
| DEV.co fit | Good |
| Assessment confidence | High |
Framework itself does not reveal security audits or threat model in provided data. Considerations: (1) Agent tool execution can be powerful—sanitize user inputs and restrict tool scopes; (2) event broker access control must be enforced; (3) LLM API keys and credentials in agent config—use secrets management; (4) file artifacts stored locally—validate permissions and cleanup. No security claims made without additional documentation review.
Alternatives to consider
LangChain + LangGraph
Lighter-weight, no broker dependency, simpler single-agent flows. Better for prototyping; less suitable for large-scale multi-agent orchestration.
AutoGen (Microsoft)
Group chat patterns for multi-agent workflows, lighter setup, good for research. Less event-driven; orchestration is more synchronous.
Crew AI
Focused on role-based agent teams with hierarchical or flat structures. Simpler than SAM for small teams; lacks Solace's scalability and event-driven guarantees.
Build on solace-agent-mesh with DEV.co software developers
Start with Solace Agent Mesh in 5 minutes. Review the Quick Start guide, set up a local instance, and explore the tutorial library to integrate with your data sources and workflows.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
solace-agent-mesh FAQ
Do I need a Solace Platform broker running?
Can agents be deployed across multiple machines?
What LLM models are supported?
Is this production-ready?
Custom software development services
From first prototype to production, DEV.co delivers software development services around tools like solace-agent-mesh. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across rag frameworks and beyond.
Ready to Build Scalable Multi-Agent Systems?
Start with Solace Agent Mesh in 5 minutes. Review the Quick Start guide, set up a local instance, and explore the tutorial library to integrate with your data sources and workflows.