The use case: how Mews deploys Temporal
Mews, a hospitality cloud platform, uses Temporal Cloud to orchestrate long-running payment-related Workflows such as bill closing, webhook processing, partial refunds, chargeback lifecycles, and KYC onboarding. Temporal also runs some periodic jobs in its job-scheduler service.
In the customer’s words
In the past, we might have tried to approximate these with a tangle of jobs and events and then under-scope the feature to reduce riskOther AI tools used by Mews
Other public relationships recorded on usedby.
Explore Mews’s AI stackOther companies using Temporal
Customers across industries, with public evidence.
BFI FinanceConfirmed
EmergentConfirmedMaria EducaçãoConfirmed
ReplitConfirmed
ShareChatConfirmedStradaConfirmedGo straight to the source
Based on Temporal’s published case study. We check the public evidence; the results are reported by the vendor.
temporal.io- Last checked
- Nov 20, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 6,000 bills per dayChecked
Printed word for word on the page, near the name of Mews.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Mews.
- Mews uses TemporalChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
By moving bill closing into an independent Temporal Workflow, the main automation flow no longer had to block on variable-length processing. Today, Temporal reliably closes around 6,000 bills per day for Mews.


