Solace Agent Mesh Pricing, Editions and Licensing (as of October 2026)

Solace Agent Mesh pricing is only partly public. As of October 2026 Solace states that Agent Mesh is free for everyone to evaluate, and “always free for individuals and companies making less than $25M/year in revenue”. Above that threshold there is a commercial licence for self-hosted Enterprise or the managed Agent Mesh Cloud Service, and Solace publishes no prices for either. The open-source Python edition that started the product was archived in September 2026. This page sets out what each offering is, what the licence says, what is not published, and what actually drives the cost.

It belongs to the Solace Agent Mesh overview in the Solace cluster. For the broker and platform price model, see Solace editions and pricing.

Solace Agent Mesh pricing: what is published

Offering	Who it is for	Price	Production use	Source
Desktop app (macOS, Windows, Linux)	Anyone evaluating or building	Free, no credit card	No: “for evaluating and building, not for running a production workload”	Solace
Free tier	Individuals, and companies under US$25M a year in revenue	Free	Yes, per Solace, self-hosted or on Solace Cloud	Solace
Enterprise (self-hosted)	Larger organisations	Not published	Yes; GA since 2 December 2025	Solace
Agent Mesh Cloud Service	Organisations wanting it managed	Not published	Early Access since 28 April 2026, “by invitation or request”	Solace
Community (Python, Apache-2.0)	Historical	Free	Archived September 2026, no fixes	GitHub

The edition names have shifted. The December 2025 launch named two editions, Enterprise and Community. Solace’s 2026 pages talk instead about a free offering, self-hosted deployment and the managed cloud service, and the Community edition’s code is archived. When you ask for a quote, ask which named edition and which feature list it covers.

Which Agent Mesh offering applies to you

The free tier and the US$25M threshold

The desktop app is the on-ramp. Solace’s September 2026 announcement packages “the full Agent Mesh runtime, an in-memory event broker, and the UI” in one installer, plus the CLI. It is explicit about the limit: everything “sits in one process on an in-memory event broker, without production-grade storage or authentication, so it is not supported for team or production workloads.”

Free production use is a separate statement. The same page says: “If you are an individual user or your enterprise makes less than $25M/year in revenue, you can use the Solace Agent Mesh in production for free.” In practice that means the self-hosted Kubernetes deployment or Solace Cloud, not the desktop app.

What the public pages do not say:

• whether revenue is measured for the legal entity or the whole corporate group, which matters for a small plant owned by a large parent
• whether the free tier includes support, or the Cloud Service, or only self-hosted software
• what happens when revenue crosses the threshold mid-term
• whether a production Solace event broker is included or licensed separately

Those are not trick questions. They are the four answers a finance team will want before a pilot becomes a dependency.

What the Agent Mesh licence says

The commercial terms sit in the Agent Mesh Schedule to the Master Supply Agreement, last revised 15 December 2025 when we checked it in October 2026. It applies on premises, in a customer-controlled cloud and in Solace-hosted cloud. The clauses worth reading closely:

1. Scope. A “non-exclusive, non-transferable, non-sublicensable” right for “internal business purposes only”. Building agents for your customers’ use needs a different conversation.
2. No reverse engineering. Customers must not “decompile, or otherwise attempt to discover the source code”, which confirms the current runtime is not distributed as open source under these terms.
3. No competing products. Customers may not use Agent Mesh “to develop Agents or applications that compete directly with Solace’s Agent Mesh offering”. System integrators and software vendors should read this one twice.
4. Your data. Solace commits not to “use Agent Mesh Data to train or improve Agent Mesh across customers.”
5. Your agents, your responsibility. The customer is responsible for “designing, developing, testing, deploying, and monitoring” agents, and for agent output complying with AI and privacy law.
6. Model providers. Solace “has no liability for the Output, security, compliance, performance, availability, or content of any Model Providers.”

Clauses 5 and 6 are normal for the category, and they matter in a plant: if an agent drafts a wrong work order, the plant owns that outcome, so human approval on any write action is a design requirement, not a nicety.

What happened to open source

The Python repository was published under Apache-2.0 in January 2025 and gathered about 4,900 GitHub stars. It was archived in September 2026, and its README now says the Python version “won’t receive new features, bug fixes or security updates.” The last PyPI release was 1.28.8, on 28 August 2026. The Apache-2.0 licence still applies to that code, so a team can fork it, but it would then own every security fix and lose compatibility with the Go runtime. As of 9 October 2026 we found no public Go source repository in the SolaceLabs or SolaceProducts organisations. If open source is a procurement requirement, Agent Mesh no longer meets it.

Solace Agent Mesh pricing beyond the licence: the real cost drivers

Cost line	What drives it
LLM tokens	Number of agents, tasks per day, context size. Agent Mesh tracks token spend by agent, model and task, and Smart Context Management keeps large tool results out of prompts
Event broker	A production Solace broker or Solace Cloud service, unless you already run one
Platform	Kubernetes, PostgreSQL for sessions, object storage for artifacts
Licence	Enterprise or Cloud, priced on request
People	Tool development, evaluations, agent ownership and review

Questions to ask before you budget

• Which edition name and which feature list does the quote cover?
• What is the pricing metric: agents, executors, tasks, users or Platform Capacity Units?
• Is the Solace event broker included, or licensed separately?
• For the free tier, is revenue counted per legal entity or for the whole group?
• Is the Cloud Service generally available in our region, and with what SLA?
• What support response times come with each option?
• What happens to pricing and terms if Agent Mesh packaging changes again?

Run the pilot before the negotiation, not after. A two-week pilot on the free desktop app, using one real use case and a realistic token budget, gives you the numbers a quote should be compared against: tasks per day, tokens per task and the tools each agent needs. Without them, the first price you see is the only reference you have.

Where it gets hard

• Comparing quotes. With no list price, you cannot benchmark. Ask for the pricing metric (agents, executors, tasks, capacity units) in writing.
• The threshold cliff. A free pilot in a subsidiary can become a commercial licence when group revenue is counted.
• Edition drift. Names and packaging changed three times in a year. Tie the contract to a feature list, not an edition name.

An independent read of the terms before signing is part of an owner’s engineer role. For the architecture these licences cover, see Solace Agent Mesh architecture.

---

Related: Solace Agent Mesh overview · Solace Agent Mesh MCP and A2A · Solace editions and pricing · Solace hub