Runtime vs Notion Agents

Notion Agents and Runtime at a glance

Notion Agents are the AI agents built into Notion. Every Business and Enterprise user gets Notion Agent, a personal assistant that searches the workspace and acts in Notion on request. Custom Agents, launched in February 2026 and generally available on Notion credits since May 4, 2026, are team agents that run on their own. They trigger on a schedule, a Notion page or database change, a Slack message or emoji, an email, or a calendar event, and they can read and write Notion, post to Slack, browse the web, hand off to other agents, and call tools like Linear, HubSpot, Stripe, Ramp, and GitHub through MCP. Notion says customers built more than a million Custom Agents during the beta. Typical jobs: internal Q&A, ticket triage, standups, status reports, and inbox management.

Runtime is the AI agent harness for payment and fintech teams. Payment ops, risk, compliance, finance, underwriting, onboarding, and support build agents from their SOPs. Each agent works on its own isolated computer in your cloud, reaches your ledger, processor, data warehouse, and ticketing tools through APIs, databases, CLIs, and MCP servers, and uses a browser for portals with no API. Agents start read-only, stop for approval before anything moves money, and record every run end to end.

Who each is for. Notion Agents fit any company that runs its knowledge and projects in Notion and wants quick automation of everyday team work. Runtime fits payment companies that want agents doing the operational work itself, under the controls a sponsor bank expects.

How they differ

Knowledge work vs money movement

Notion Agents are excellent at work that lives in documents and databases: answering questions from the wiki, routing requests, summarizing a week of updates. Payment operations work is different. A held payout, an ACH return with an odd code, or a dispute where the evidence contradicts the claim needs an agent that queries the ledger, pulls the processor record, reads the bank file, and reasons through an exception. Runtime agents are built for that, and they stop for a named approver before releasing a payout, applying a reserve, booking a ledger entry, or replying to a sponsor bank.

Where the agent runs and who holds the data

Notion Custom Agents run on Notion's infrastructure, and Notion Workers, its beta runtime for custom code, also runs there. Enterprise adds zero data retention with LLM providers and DLP and SIEM connections. Runtime agent computers run in your own AWS, GCP, or Azure account, or the whole platform is self-hosted with Helm. Credentials are masked, card numbers and SSNs are stripped from prompts and logs, and PCI data can stay in your environment.

Models

Notion lets you pick from Claude, GPT, Gemini, and Grok models, or use Auto, and admins can now restrict which models agents use. Runtime lets you bring any model, including open-weight models served in your own cloud for PCI and PII work, and routes between models and harnesses (Claude Code, Codex, OpenCode) with fallbacks when a provider goes down.

The record your sponsor bank asks for

Notion logs each agent run with its trigger, actions, and errors, and Enterprise records configuration and access changes in the audit log. That's good governance for workspace automation. Runtime records every run end to end: the trigger, every query and tool call and what it returned, the approvals, the cost, and the result. When a sponsor bank, auditor, or examiner asks how a case was handled, you export the run.

Self-serve vs forward-deployed engineer

Notion is self-serve: anyone with access can describe an agent and turn it on in minutes. Runtime pairs you with a forward-deployed AI engineer whose team built payment infrastructure at Hulu's payments team at Disney, Finix, and Modern Treasury. The FDE maps your processes, builds the first agents with your team, sets up guardrails with security, and trains your admins, so your team builds the next ones. Once a process is solved, Runtime agents can turn it into deterministic code that lives in your repos.

Where Notion Agents are stronger

• Speed to first agent. No engineer needed; a team lead can ship an agent the same afternoon.
• Workspace context. If your SOPs, projects, and meeting notes already live in Notion, agents start with that context.
• Everyday team work. Q&A, triage, standups, and status reports across every department, not just operations.
• Built-in governance for that work. Per-agent permissions, version history, spending caps, and controls on who can create agents.
• Cost for light usage. If you already pay for Notion Business, adding a few agents is inexpensive.

Pricing

Notion: Custom Agents require a Business plan (from $20 per member per month) or Enterprise (custom). Since May 4, 2026, Custom Agents run on Notion credits at $10 per 1,000 credits, with usage based on task complexity. Workers are free to try during the beta.

Runtime: Free ($0, one session), Teams from $99 per seat per month, and Enterprise with custom pricing and self-hosting. Teams usually measure it against the work of analysts they were about to hire. Rain replaced $250k in vendor spend with Runtime.

Which should you choose

Choose Notion Agents if

• Your company already runs its docs, projects, and knowledge in Notion
• The work is Q&A, triage, reporting, and coordination
• You want any team to build agents self-serve, today
• The agents don't need access to payment systems or the ability to move money

Choose Runtime if

• The queue is payment exceptions, recon breaks, disputes, alerts, or bank RFIs
• Agents need your ledger, processor, data warehouse, and portals with no API
• Card data or PII must stay in your cloud, with models you choose
• You need approvals on money movement and an audit trail your sponsor bank will accept

Plenty of teams run both: Notion holds the SOPs and the team wiki, Runtime agents do the payment work and post results back where people already look.

Frequently asked questions

What are Notion Custom Agents?

Custom Agents are team-wide AI agents in Notion that run on their own, triggered by a schedule, a Notion page or database change, a Slack message, an email, or a calendar event. They read and write Notion pages and databases, post to Slack, browse the web, and call connected tools through MCP. They require a Business or Enterprise plan and run on Notion credits.

Can Notion agents handle payment operations?

They can help around the edges, such as summarizing a queue, routing tickets, or drafting a status report. Investigating a held payout or a recon break means querying your ledger and processor, reading bank files, and sometimes logging into portals with no API, with approval before anything moves money. That is the work Runtime is built for.

Is Notion AI secure enough for financial data?

Notion offers SAML SSO on Business and, on Enterprise, zero data retention with LLM providers, SCIM, audit logging, and DLP and SIEM connections. Agents run on Notion's infrastructure. If card data or PII must stay in your own cloud, Runtime runs agent computers in your AWS, GCP, or Azure account, or fully self-hosted.

How much do Notion Custom Agents cost?

Custom Agents need a Business plan (from $20 per member per month) or Enterprise. Since May 4, 2026 they run on Notion credits, sold at $10 per 1,000 credits, with usage depending on how complex each run is.

Can we use Notion and Runtime together?

Yes. Many teams keep SOPs and runbooks in Notion. Runtime agents can read those procedures, do the investigation in your payment systems, and post results back to Slack or a Notion page.