Blockchain-connected workflows without the relayers, validators, or backend glue

Reactor helps apps, smart contracts, and web services move data and trigger actions across Web2 and Web3. Integrate through the Web2 API, Solidity function, or both. Use whichever fits your system.

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, many Web2 to Web3 and cross-chain workflows depend on a patchwork of relayers, validators, bots, backend jobs, and custom scripts. That creates real problems:

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 require teams to adopt an entirely new operating model and lock into a single ecosystem.

"Crypto and blockchain is probably one of the most complex sectors out there. Ultimately you want the blockchain enablement, the technology to be on the backend, to be seamless."

- Bloomberg

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.

Sentinel

Evaluate messages before execution using Sentinel to manage risk, provide secrets to Web2 calls, and allow or deny workflows based on defined rules.

Onchain randomness

Support product flows that need verifiable random outcomes tied to application logic.

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 governs workflow execution by applying policy checks, managing risk, and providing secrets to Web2 calls.

Message flow

A web service calls send_web_reactor_message, or a contract calls send.
Reactor routes the message into Core.
Core processes the workflow and coordinates execution.
Sentinel applies policy checks 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.

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 without expanding your current stack.

Fusion 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.

ISVs and software vendors

Adding blockchain capabilities to existing platforms without requiring customers to adopt a new infrastructure stack.

System integrators

Delivering blockchain-connected features for clients alongside the systems they already run.

Ecosystem partners

Expanding service offerings to include blockchain-connected workflows as a practical, low-friction capability.

Technical consultants

Helping engineering and product teams adopt Reactor safely, starting with one workflow at a time.

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."

Operational Visibility

Trace every message from source to execution. ReactorScan shows message lifecycle, status, retries, failures, and history. Everything your engineering, security, and operations teams need to trust a new system.

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.

Tokenomics

Token Details:

Token Name: Reactor
Token Symbol: R
Total Supply: 1,000,000,000
Use: Payment of fees for onchain and offchain messaging

Distribution:

Community: 30%
Ecosystem: 25%
Team & Advisors: 18%
Marketing: 10%
Token Sale: 10%
Airdrops & Liquidity: 7%

Disclaimer: The R Token is designed solely for consumptive use within the Reactor ecosystem, including messaging fees, automation, randomness, and cross-chain transactions. Holding R Tokens does not entitle the holder to any share of Archly Reactor Inc.’s revenue, profits, equity, or governance rights. The R Token should not be viewed as an investment or as representing ownership in Archly Reactor Inc.

Start with One Workflow

No rewrite required. Works alongside your current stack. Starting at $0.10 per message to most destinations with predictable pricing from day one.

Reactor One-Pager