The Tenderly Alternative That Doesn’t Punish You for Growing

Tenderly sells Node RPC by quote, metered in Tenderly Units, with no free RPC tier. SwiftNodes is self-serve with published flat prices, a free tier, card or crypto payments and 128 chains. Keep Tenderly for simulation and move the RPC traffic.

Feature-by-feature: SwiftNodes vs Tenderly

Feature data sourced from Tenderly’s public pricing page and SwiftNodes’ own published rates. Last reviewed 2026-10-13. Pricing changes frequently — verify on the source site before deciding.

Switching from Tenderly: what changes in your code

Standard JSON-RPC and WebSocket calls need only a new URL. Your Tenderly endpoint:

https://<network>.gateway.tenderly.co/<ACCESS_KEY>
wss://<network>.gateway.tenderly.co/<ACCESS_KEY>

becomes:

https://rpc.swiftnodes.io/rpc/<chain>?key=YOUR_API_KEY
wss://rpc.swiftnodes.io/ws/<chain>?key=YOUR_API_KEY
(over HTTP the key can go in an x-api-key header instead; <chain> is eth, base, arbitrum, solana, ... see /docs/supported-chains)

Before

import { createPublicClient, http } from "viem";
import { mainnet } from "viem/chains";

const client = createPublicClient({
  chain: mainnet,
  transport: http("https://mainnet.gateway.tenderly.co/YOUR_ACCESS_KEY"),
});

After

import { createPublicClient, http, webSocket } from "viem";
import { mainnet } from "viem/chains";

const client = createPublicClient({
  chain: mainnet,
  transport: http("https://rpc.swiftnodes.io/rpc/eth?key=YOUR_API_KEY"),
});

// Subscriptions: same key over WebSocket
const ws = createPublicClient({
  chain: mainnet,
  transport: webSocket("wss://rpc.swiftnodes.io/ws/eth?key=YOUR_API_KEY"),
});

Tenderly-specific methods and what to call instead

Point a staging deployment at SwiftNodes first and compare a few hundred real calls against Tenderly; standard JSON-RPC methods return the same chain data from any provider, so differences point at a real problem worth knowing about before you cut over.

Plans are month to month: you can run both providers side by side during the switch and cancel Tenderly when you are satisfied.

Measured, not claimed

Every week we call each method on every EVM chain through the same endpoint customers use, and publish the result. From the run on 2026-10-18:

• 107EVM chains probed weekly through the customer path
• 97serve debug_traceCall
• 46serve trace_block (Parity traces)
• 88serve archive state with &archive=1
• 85accept JSON-RPC batch requests

Per-chain detail is on the method support matrix and in the method reference, including what each chain actually returns for everyday calls such as eth_estimateGas and eth_subscribe.

Why developers switch from Tenderly to SwiftNodes

Frequently asked questions