Runtime as featured inForbesRead the article

Runtime and Sift

Runtime vs Sift: Sift scores fraud and decides in real time. Runtime agents work the review queue Sift creates, investigating across ledger, processor, and tickets, then write the decision back.

Gus Trigos
Co-founder and CEO, Runtime
Updated October 8, 2026 · 6 min read

TL;DR

Sift and Runtime do different jobs. Sift scores events and automates fraud decisions using its global data network. Runtime agents investigate the cases Sift sends to manual review, across your ledger, processor, and tickets, and write the decision back to Sift with a person approving.

Feature
RuntimeRuntime
SiftSift
Core jobRuntimeInvestigate and act on casesSiftScore and decide on events
Fraud scoringRuntimeUses your Sift scoreSiftReal-time ML risk scores
Network dataRuntimeYour systems and shared org memorySift1 trillion+ events a year
Rules and automated decisionsRuntimeApprovals before money movesSiftDecisioning engine and workflows
Manual reviewRuntimeAgents draft decisions with evidenceSiftConsole, queues, ActivityIQ summaries
Data it readsRuntimeLedger, processor, bank files, tickets, SiftSiftEvents you send to Sift
Teams coveredRuntimeRisk, payment ops, finance, support, moreSiftFraud and trust and safety
Where it runsRuntimeYour cloud, or self-hostedSiftSift-hosted
PricingRuntimeBy request; free pilot for approved teamsSiftNot published

Runtime is not an alternative to Sift; a team running Sift does not need to replace it to use Runtime. Sift scores events and automates fraud decisions using its global data network. Runtime is the AI agent harness for payment and fintech teams, and its agents do the investigation and follow-up a person would otherwise do after Sift sends a case to review.

What each does

Sift is a fraud decisioning platform. Its products are Payment Protection and Account Defense, with the Sift Score API for teams that bring Sift's signals into their own models. Sift scores events in real time using a network it says processes more than 1 trillion events a year, and its decisioning engine lets teams set thresholds, workflows, and friction. Cases that need judgment go to analysts in the Sift Console, where ActivityIQ summarizes user activity and the newer Attack Detection Agent groups attacks into investigations. Sift lists fintech customers such as Remitly and CoinJar.

Runtime is a harness for building and running many agents across the org. Anyone on risk, payment ops, finance, compliance, or support builds agents from their SOPs. Agents work on their own isolated computers in your cloud and reach your tools through APIs, databases, CLIs, MCP servers, and a browser for portals with no API. They start read-only, stop for approval before anything moves money, and record every run end to end.

Where they overlap

Be honest about the overlap: both help a fraud team spend less time on manual review.

  • Sift reduces how many cases need review. Better scores and rules mean more events are accepted or blocked automatically.
  • Sift helps analysts review faster. ActivityIQ summaries and attack grouping speed up work inside the console.
  • Runtime does the review work itself. An agent gathers the evidence, applies your SOP, and drafts the decision.

If every case can be decided from what Sift already sees, Sift's own tools may be enough. The gap opens when the answer sits in systems Sift never receives: the ledger, the processor, bank files, the support history, or a sponsor bank's request.

How they work together

A typical flow for a payment or account case that Sift sends to review:

  1. Sift scores the event. Low-risk events pass, high-risk events are blocked, and the rest go to a review queue.
  2. A Runtime agent picks up the case. A Sift webhook or the queue itself triggers the agent, which pulls the user, the score, and the event history from Sift.
  3. The agent investigates outside Sift. It checks the transaction in the processor, the balance and prior entries in the ledger, open support tickets, past chargebacks, and anything the company already learned about similar cases.
  4. It drafts a decision with evidence. Accept, block, or hold, with the reasoning and the data behind it, written the way your SOP asks.
  5. A person approves in Slack or Teams. Anything that moves money, such as releasing a held payout or applying a reserve, waits for sign-off.
  6. The agent writes back. It applies the decision in Sift through the Decisions API, updates the ticket, and notifies the team that needs to know.
  7. The full record is kept. The trigger, every query and tool call, the approval, the cost, and the result are stored and exportable for your sponsor bank or an auditor.

What changes for the fraud team

  • Sift stays the source of truth for risk. Scores, rules, and decisions still live in Sift. The agent reads them and writes back to them.
  • Analysts review drafts, not raw cases. Each case arrives with the evidence already gathered from systems Sift does not see, and the analyst approves, edits, or rejects.
  • Your SOP sets the rules. The agent follows your written procedure. Once a pattern is solved, it can become a deterministic script that lives in your repo.
  • False positives teach the next run. Every resolved case, including the ones Sift flagged wrongly, becomes context the next agent run can use.

Where Runtime enters the picture

Sift creates a queue: every event it can't confidently accept or block lands in manual review. Runtime is the layer that works that queue, and the work that spreads from it. The same case often touches more than fraud. Say Sift holds a seller's payout for review. Support gets the seller's ticket, payment ops traces the payout at the processor, finance sees a recon break, and risk decides whether to release it. On Runtime that is one investigation with one record, not four separate ones, and Sift's score is one input to it.

Runtime is the AI agent harness for payment and fintech teams. It doesn't replace Sift's scoring or decisioning; it gives risk, support, payment ops, and finance agents that use Sift as a tool next to everything else they touch.

  • No single vendor to depend on. Agents run in your AWS, GCP, or Azure account or fully self-hosted, on your choice of sandbox provider with fallbacks, and on any model (Claude, GPT, Gemini, or open-weight), with harness routing across Claude Code, Codex, and OpenCode.
  • Guardrails you set. Agents start read-only, releasing a held payout or applying a reserve waits for approval, access follows roles, credentials are masked, card numbers are stripped from prompts and logs, and every run is recorded.
  • Built for teams. The agent working Sift reviews shares templates and one memory with the agents in support, payment ops, and finance, so a fraud case and the ticket behind it are worked once.
  • An engineer, not an account executive. A forward-deployed AI engineer who built payment infrastructure at Hulu's payments team at Disney, Finix, Modern Treasury, and BlackRock maps your review SOP and builds the first agents with your team.
New agent

Create a banking ops agent that handles RFIs, hold-harmless requests, and returns of funds from our partner bank, verifies against our ledger, and drafts replies for my approval.

Describe the agent you want
Agent ready

bank-ops-agent

Tools picked from your prompt

EmailLedgerSFTPMastercard
Describe the work in plain English, attach the SOP, and Runtime builds the agent.

When you need both

  • Your Sift review queue keeps growing and you are about to hire more analysts
  • Reviewers routinely leave the Sift Console to check the ledger, processor, or help desk
  • Fraud cases spill into support, payment ops, or finance work
  • You need approvals and a full run record before any payout is released or reserve applied

When Sift alone is enough

  • Most decisions are automated by Sift's scores and rules
  • Manual review volume is small and stable
  • Reviewers can decide a case from what Sift already sees
  • Fraud is the only team you want to change right now

Frequently asked questions

Is Runtime an alternative to Sift?

No. Sift scores events for fraud risk and automates decisions using data from its global network. Runtime does not score fraud. Runtime agents work the cases Sift routes to manual review and the follow-up work across other teams.

How does Runtime connect to Sift?

Through Sift's APIs. Sift can notify your systems of decisions with webhooks, and decisions can be applied to users and orders through its Decisions API, so a Runtime agent can pick up a case, investigate it, and write the approved decision back.

Does Sift have AI agents?

Sift has added AI to its console, including ActivityIQ, which summarizes user activity for investigators, and the Attack Detection Agent, the first part of its Fraud Attack Defense Suite, which detects and groups fraud attacks into investigations.

When is Sift alone enough?

When most decisions are automated by Sift's scores and rules, manual review volume is manageable, and reviewers rarely need data outside Sift's console to decide a case.

Is Sift pricing public?

No. Sift does not publish pricing; it is sold through sales. Runtime is available by request, with custom pricing, self-hosting, and a free pilot for approved teams.

Where does Runtime fit next to Sift?

Runtime works the queue Sift creates. Sift scores events and sends the uncertain ones to manual review. Runtime agents pick up those cases, investigate across your ledger, processor, and support tools, draft the decision for a person to approve, write it back to Sift, and handle the follow-up for payment ops, finance, and support.

Put an agent on your Sift review queue

Bring one SOP. A forward-deployed AI engineer builds the first agent with your team, inside your cloud.