Blockchain-connected workflows without the relayers, validators, or backend glue
Reactor helps apps, smart contracts, and web services trigger and coordinate actions across Web2 and Web3.
One API for Web2. One function for Solidity. Start with one workflow, not a platform rewrite.
- Reactor Core deployed on ICP mainnet
- Gateway contracts deployed across 24 EVM chains
- Messaging and onchain randomness supported
- Built for app↔chain, chain↔app, and cross-chain execution
The Problem
Today, most Web2↔Web3 and cross-chain workflows depend on third-party relayers or validator networks, or a patchwork of custom bots, backend jobs, and scripts. The workflow may work, but the operating model becomes harder to explain, harder to debug, and harder to scale.
- More moving parts to operate
- More trust assumptions to explain to engineering and security teams
- More vendors and systems to manage
- Harder to debug across app and chain boundaries
- Less predictable cost as workflows grow
Most solutions force teams into a new operating model or a single ecosystem. Reactor is built to fit alongside what already works.
What You Can Build
Reactor is built for practical workflows that connect Web2 apps and Web3 contracts across chains. Start with the next workflow your product needs and expand over time.
App action → onchain execution
Trigger rewards, minting, settlement, notifications, or contract actions from existing products and services.
App action → onchain execution
Trigger rewards, minting, settlement, notifications, or contract actions from existing products and services.
Onchain event → web callback
React to contract events in your app, backend, or external service without building custom monitoring glue for every flow.
Chain to chain messaging
Move instructions and data between supported chains with a simpler execution path.
Blockchain-connected automation
Run scheduled or event-driven workflows that span applications and smart contracts.
Onchain randomness
Support product flows that need verifiable random outcomes tied to application logic.
Add policies and controls when you need them
Evaluate messages before execution with Sentinel to manage risk, provide secrets for Web2 calls, and allow or deny workflows based on defined rules.
Use Reactor where your current stack is the most painful, not where it already works.
How Reactor Works
Reactor is built around a small set of components that route, process, observe, and control messages across systems.
Reactor Gateway
Smart contracts deployed on supported chains that send and receive Reactor messages.
Reactor Gateway
Smart contracts deployed on supported chains that send and receive Reactor messages.
Reactor Core
The onchain execution and routing layer running on the Internet Computer. Core processes workflows, manages routing, and coordinates message handling.
ReactorScan
The visibility layer for tracing messages, execution status, failures, retries, and history.
Sentinel
A policy and control layer that evaluates messages during processing, determines what should run, what should stop, where additional controls are needed, and provides secrets for Web2 calls when required.
R Token
One usage token across all supported chains, so users do not need to manage multiple gas tokens across networks.
Message flow
- A web service calls
send_web_reactor_message, or a contract callssend. - Reactor routes the message into Core.
- Core processes the workflow and coordinates execution.
- Sentinel applies policy checks, enforces workflow controls, and provides secrets for Web2 calls where enabled.
- The destination step executes and the result is traceable in ReactorScan.
Better infrastructure is easier to adopt when it is easier to inspect and easier to control.
ReactorScan: Operational visibility for every message
Trace every message from source to execution. ReactorScan shows status, retries, failures, history, and the full execution trail your engineering, security, and operations teams need to operate with confidence in production.
- What happened to this message?
- Where is it now? Did it execute or fail?
- What chain, app, or system did it touch?
- Can it be retried?
- What is the deterministic message ID and full execution trail?
A visible system earns trust faster than an elegant but opaque one.
Why Teams Adopt Reactor
Most teams are not looking for a full rewrite. They want to ship the next workflow faster, with fewer moving parts and clearer visibility into what is happening in production.
Ship without expanding your stack
Add new workflows without adding relayers, validators, custom bots, or layers of backend orchestration to your stack.
Ship without expanding your stack
Add new workflows without adding relayers, validators, custom bots, or layers of backend orchestration to your stack.
Roll out one workflow at a time
Use Reactor where your current stack is most painful. Keep the rest of your system as-is.
Trace every message
ReactorScan gives teams visibility into message lifecycle, execution status, failures, retries, and history.
Keep adoption practical
Reactor is designed to fit alongside existing systems, team structures, and operating models rather than forcing a new one all at once.
Bring predictability to pricing
Starting at $0.10 per message to most destinations. A simpler usage model designed to make cost easier to understand before your workflow is live.
Add control before execution
Sentinel governs workflow execution by applying policy checks, managing risk, and providing secrets to Web2 calls, giving teams precise control over what runs and what stops.
Reactor is the simplest way to add blockchain-connected workflows alongside your current stack, starting with one workflow at a time.
Partner Program
For ISVs, system integrators, ecosystem partners, and technical consultants helping customers add blockchain-connected workflows without forcing a full stack rewrite.
ISVs and software vendors
Adding blockchain capabilities to existing platforms without requiring customers to adopt a new infrastructure stack.
What partners do
- Integrate Reactor alongside current systems
- Define initial workflow use cases
- Reduce implementation risk
- Expand from one workflow to broader adoption over time
Why partners matter
- Internal fear and credibility gaps
- Implementation risk perception
- Incumbent system comfort
- Channel reach into existing customer environments
"You do not need to rip anything out. We can add this cleanly."
Start with One Workflow
No rewrite required. Works alongside your current stack. Predictable pricing from day one.