Xient Bridge
The SAP Joule alternative that answers in Teams.
Joule lives inside the SAP interface and requires the SAP cloud chain. Bridge starts where that chain ends: in your Microsoft Teams, on your ECC or S/4HANA, within weeks.
Where Joule stops and Bridge starts.
Joule is SAP's assistant inside the SAP applications. It needs the Joule entitlement, BTP, Cloud Identity Services and, depending on the scenario, Work Zone - and it answers inside the SAP interface. If you run classic ECC, you are left out; if you want answers in Teams, likewise.
Bridge picks up exactly there: an agent in Microsoft 365 Copilot that reads from your SAP through approved standard interfaces and answers in Teams - as text, table or chart. No new system, no cloud of ours, no data copy. Both can run side by side; Bridge takes nothing away from Joule.
The honest comparison.
We do not talk Joule down. We put it in context: where the assistant lives, what it requires, when it is available, what it costs. The answers are on our comparison page - Bridge, Joule, Joule Work Desktop and SAP Business AI side by side, with a look at Databricks Genie.
And the argument that counts in the end: governance. Bridge is read-only by conviction, every query runs under the SAP rights of the person asking, and three independent audit trails make every transaction traceable.
This is what it looks like.
Stills from the demo videos, recorded in a demo system.
Common questions
Is Bridge a replacement for Joule?
An alternative for answers outside the SAP interface - especially for ECC and for organisations that work in Teams. Both can run in parallel.
What about Joule Work Desktop?
An early-adopter programme with direct connectivity only to S/4HANA Cloud Public Edition; pricing and governance are open. Bridge is in production on ECC and S/4HANA today.
Does Bridge need BTP?
No. With RISE or a BTP policy, Bridge can connect through the Cloud Connector, but it does not have to.
How fast, in comparison?
After the readiness check, two to three weeks of onboarding, then the pilot.
The phased plan
Bridge and Joule do not rule each other out.
What you build with Bridge today is groundwork - for your people, your governance and, if it comes to that, for Joule as well. None of it gets thrown away later.
- 01Start today
Bridge in production within weeks - in Teams, on ECC or S/4HANA, no migration, no new platform, no fundamental debate about SAP roadmaps.
- 02Coexistence
When Joule arrives in your SAP interface, Bridge keeps running alongside: Joule inside SAP, Bridge in Teams. Both read the same SAP, under the same rights.
- 03Optional: replace
If Joule does what you need and costs less - then Bridge can be replaced. It does not have to be. You decide on numbers, not on a roadmap.
What stays in every phase
- The function catalogue: which questions your organisation really asks is documented and approved.
- The permissions and approval concept CISO, privacy and works council have already signed off.
- The habit: your people ask SAP in Teams without training - whichever assistant answers.
- The numbers from the Value Review: what a question replaces and what it is worth - the basis for any later decision.
Joule or Bridge? See it live.
Thirty minutes, your questions, a real demo system - and the comparison side by side.