Tenderly

• Name: Tenderly
• URL: https://tenderly.co/
• Category: simulation-powered blockchain-operations company / EVM developer platform / RPC, monitoring, and automation middleware company
• Tags: ethereum-ecosystem
• Summary: Tenderly belongs in companies/ because the practical control surface is not just simulation tooling exists or there is another RPC provider; it is that a named operator runs the dashboard-issued Node RPCs, Virtual Environment public/admin RPC split, simulation and tracing surfaces, alerting and destination wiring, and Web3 Actions runtime many teams can end up using as their release, incident-response, and automation control plane. The useful question is not only what can Tenderly simulate? but which organization controls the workflows a team uses to decide whether a transaction is safe, which events are urgent, and what automation fires next?
• What it does:
  • Operates Node RPC across 80+ EVM networks, including Tenderly-specific simulation, gas-estimation, tracing, and decoding methods in the tenderly_ namespace
  • Provides Virtual Environments that fork live networks into private production-like environments with a dashboard, Public RPC, Admin RPC cheatcodes, and REST APIs for CI/CD and staging workflows
  • Runs monitoring and alerting infrastructure with 12 trigger types and multiple destinations spanning messaging apps, incident tools, webhooks, and Web3 Actions
  • Hosts Web3 Actions as JavaScript / TypeScript functions running on Tenderly infrastructure, with trigger-based execution, key-value storage, secrets management, and configurable execution behavior
  • Packages an operator console for simulation, tracing, debugging, and decoded transaction context that teams can treat as the default truth surface during releases and incidents
• Key claims:
  • Tenderly’s docs introduction describes the company as the simulation company for onchain operations and says engineering, finance, and risk teams use it to model transactions, deployments, and integrations against live state before capital is exposed
  • The same docs present Tenderly as a single operational layer spanning simulation, transaction understanding, monitoring, and production response across 100+ networks
  • The Virtual Environments docs say they fork a live network into a private environment with Public RPC, Admin RPC, REST APIs, unlimited faucet, state controls, and dashboard tooling for development, CI/CD, staging, and demos
  • Those docs also make the privilege split explicit: the Admin RPC can mutate balances, storage, time, and other network state, and should not be handed to external testers or dapp users
  • The Node RPC docs describe a production node with multi-regional infrastructure, WebSocket support, batching, Node Extensions, and paid-plan access managed through the Tenderly dashboard
  • The alerts docs say Tenderly offers 12 onchain trigger types and 8 destination types including Slack, Telegram, Discord, Sentry, PagerDuty, webhooks, and Web3 Actions, which makes destination semantics and alert routing part of the real operator boundary
  • The Web3 Actions docs say actions run on Tenderly infrastructure with secrets management, persistent storage, multiple trigger types, sequential-versus-parallel execution modes, and explicit per-action rate limits that can cause excess executions to be skipped
• Whitepaper: No classic standalone Tenderly company whitepaper or litepaper was found during this pass. The strongest primary materials were Tenderly’s docs introduction, Node RPC docs, Virtual Environments docs, Alerts docs, Web3 Actions docs, and llms.txt; see ../whitepapers/tenderly-primary-sources-2026-04-23.md.
• Sources:
  • https://tenderly.co/
  • https://docs.tenderly.co/llms.txt
  • https://docs.tenderly.co/products
  • https://docs.tenderly.co/node
  • https://docs.tenderly.co/virtual-environments
  • https://docs.tenderly.co/monitoring/alerts/introduction
  • https://docs.tenderly.co/monitoring/web3-actions/introduction

Internal linkages

• Product-layer note: tenderly.
• Strongest operator-platform comparisons: alchemy, quicknode, and chainstack.
• Useful automation/control-plane contrast when the question shifts from hosted infrastructure to contract-native execution: gelato.

Protocol / company boundary

• tenderly is still the right note for the product-layer cut: simulation, tracing, Virtual Environments, monitoring, and automation as reusable developer surfaces.
• This company note isolates the operating shell around endpoint issuance, dashboard-managed configuration, alert-destination routing, Web3 Actions runtime semantics, secrets handling, and the privilege boundary between Public RPC and Admin RPC.
• That split matters because a team may adopt Tenderly not just as one tool but as the place where it decides whether a transaction looks safe, where production events are routed, and what automated response is allowed to run.

Control surface

• Practical leverage sits in who can create, reset, or delete dashboard-managed endpoints; how simulations, traces, and decoded call meaning are presented; which networks and features are supported; and which alert and webhook destinations become operational truth.

• The Public RPC versus Admin RPC split in Virtual Environments is especially worth preserving because it shows Tenderly is not only observing workflows. It can also expose state-mutating cheatcode surfaces that are safe in CI but dangerous if misrouted into public or shared contexts.

• Web3 Actions add another company-run control point: execution ordering, skipped runs under rate limits, stored secrets, and the line between monitoring and automated action all sit inside Tenderly’s hosted runtime rather than inside a team’s own infrastructure by default.

• Read the durable risk here as who operates the release and response console for this onchain system?, not only as which RPC URL does the app use?

• Last reviewed: 2026-08-07 UTC