{"apiVersion":"1","missingFactMeaning":"Not recorded means no sourced value is recorded in this profile. It does not mean the capability is unavailable.","capabilityEvidenceMeaning":"Documented means supported by the cited supplier material, not independently tested. Unknown is not a negative finding. Conditional capabilities do not count as strict matches. Evidence applies to the named product only; it does not establish live integrations, contractual availability or measured outcomes.","item":{"id":"161","slug":"flows-engine","name":"Flows Engine","canonicalUrl":"https://igamingdiscovery.com/products/flows-engine","supplierSlug":"flows","supplierName":"Flows","supplierUrl":"https://igamingdiscovery.com/suppliers/flows","productTypeSlugs":["workflow-automation"],"kind":"software","summary":"Orchestrates events and actions across an iGaming technology stack.","description":"Flows Engine is the core orchestration platform behind the Flows product suite. Teams use it to connect systems and configure workflows around incoming data and actions. Published examples include routing jackpot events into player communications and internal notifications.\n\nStart evaluation with a concrete event-to-action journey. Test failure handling and downstream completion separately from the receipt of an event; procurement should establish the visibility and operating controls needed by the people running those workflows.","buyerFit":"Product and operations teams coordinating several systems without replacing the whole stack.","useCases":["Coordinate player-event workflows","Route operational notifications","Connect data to downstream actions"],"capabilities":["Workflow configuration","System orchestration","Event-driven routing"],"delivery":"Connected orchestration platform; published examples use webhooks, APIs and Kafka event inputs.","pricing":"Request a proposal specifying event volumes, environments, connectors and support.","website":"https://flows.world/solutions/","attributes":[{"key":"role","label":"Role","value":"Core workflow orchestration layer.","sourceUrl":"https://flows.world/solutions/"},{"key":"event-inputs","label":"Event inputs","value":"Published examples include webhooks, APIs and Kafka.","sourceUrl":"https://flows.world/flows-blog/flow-of-the-week-seamless-jackpot-data-orchestration/"},{"key":"action-targets","label":"Action targets","value":"Player communications and internal tools in the documented jackpot workflow.","sourceUrl":"https://flows.world/flows-blog/flow-of-the-week-seamless-jackpot-data-orchestration/"},{"key":"execution-controls","label":"Execution controls","value":"Request evidence of retries, idempotency, failure queues and reconciliation for the proposed flow.","sourceUrl":"https://flows.world/flows-blog/flow-of-the-week-seamless-jackpot-data-orchestration/"}],"faqs":[{"question":"How is the Engine different from FlowsPlay?","answer":"The Engine supplies orchestration; FlowsPlay is the gamification layer built on the platform.","sourceUrl":"https://flows.world/solutions/"},{"question":"Does a workflow require the operator’s own data?","answer":"Yes. The documented jackpot example starts with a live event source, then uses connected systems for actions.","sourceUrl":"https://flows.world/flows-blog/flow-of-the-week-seamless-jackpot-data-orchestration/"},{"question":"Is there a public fixed price?","answer":"No fixed price was confirmed in the reviewed material. Request a scoped commercial proposal.","sourceUrl":"https://flows.world/"}],"sources":[{"label":"Flows — solutions","url":"https://flows.world/solutions/","checkedAt":"2026-10-08T00:00:00.000Z","publisher":"Flows","supports":"Product identity and core role."},{"label":"Flows — platform overview","url":"https://flows.world/","checkedAt":"2026-10-08T00:00:00.000Z","publisher":"Flows","supports":"Connected platform and configuration positioning."},{"label":"Flows — jackpot orchestration example","url":"https://flows.world/flows-blog/flow-of-the-week-seamless-jackpot-data-orchestration/","checkedAt":"2026-10-08T00:00:00.000Z","publisher":"Flows","supports":"Illustrative inputs and downstream workflow."}],"reviewedAt":"2026-10-08T00:00:00.000Z","popularity":{"score":25,"confidence":"low","coverage":0,"reviewedAt":"2026-10-08T00:00:00.000Z","methodVersion":"commercial-reach-v2","basis":"calculated"},"capabilityProfile":{"vocabularyVersion":"2026-10-10.4","scope":"product","reviewState":"out_of_scope","reviewedAt":null,"reviewDueAt":null,"facts":[]},"facts":[{"key":"purpose","label":"Product purpose","value":"Orchestrates events and actions across an iGaming technology stack.","status":"recorded","sourceUrl":null,"sources":[]},{"key":"buyerFit","label":"Buyer fit","value":"Product and operations teams coordinating several systems without replacing the whole stack.","status":"recorded","sourceUrl":null,"sources":[]},{"key":"role","label":"Product role","value":"Core workflow orchestration layer.","status":"recorded","sourceUrl":"https://flows.world/solutions/","sources":[{"label":"Flows — solutions","url":"https://flows.world/solutions/","checkedAt":"2026-10-08T00:00:00.000Z","publisher":"Flows","supports":"Product identity and core role."}]},{"key":"coverage","label":"Scope and coverage","value":null,"status":"not_recorded","sourceUrl":null,"sources":[]},{"key":"event-inputs","label":"Event inputs","value":"Published examples include webhooks, APIs and Kafka.","status":"recorded","sourceUrl":"https://flows.world/flows-blog/flow-of-the-week-seamless-jackpot-data-orchestration/","sources":[{"label":"Flows — jackpot orchestration example","url":"https://flows.world/flows-blog/flow-of-the-week-seamless-jackpot-data-orchestration/","checkedAt":"2026-10-08T00:00:00.000Z","publisher":"Flows","supports":"Illustrative inputs and downstream workflow."}]},{"key":"action-targets","label":"Action targets","value":"Player communications and internal tools in the documented jackpot workflow.","status":"recorded","sourceUrl":"https://flows.world/flows-blog/flow-of-the-week-seamless-jackpot-data-orchestration/","sources":[{"label":"Flows — jackpot orchestration example","url":"https://flows.world/flows-blog/flow-of-the-week-seamless-jackpot-data-orchestration/","checkedAt":"2026-10-08T00:00:00.000Z","publisher":"Flows","supports":"Illustrative inputs and downstream workflow."}]},{"key":"execution-controls","label":"Execution controls","value":"Request evidence of retries, idempotency, failure queues and reconciliation for the proposed flow.","status":"recorded","sourceUrl":"https://flows.world/flows-blog/flow-of-the-week-seamless-jackpot-data-orchestration/","sources":[{"label":"Flows — jackpot orchestration example","url":"https://flows.world/flows-blog/flow-of-the-week-seamless-jackpot-data-orchestration/","checkedAt":"2026-10-08T00:00:00.000Z","publisher":"Flows","supports":"Illustrative inputs and downstream workflow."}]},{"key":"workflow-governance","label":"Workflow governance","value":null,"status":"not_recorded","sourceUrl":null,"sources":[]},{"key":"delivery","label":"Delivery & integration","value":"Connected orchestration platform; published examples use webhooks, APIs and Kafka event inputs.","status":"recorded","sourceUrl":null,"sources":[]},{"key":"pricing","label":"Pricing","value":"Request a proposal specifying event volumes, environments, connectors and support.","status":"recorded","sourceUrl":null,"sources":[]}]}}