How deployoor compares
deployoor is viem-first and record-centric. It deploys, records to plain JSON, and feeds typed access — without coupling your app to the deploy tool.
At a glance
| deployoor | hardhat-deploy / Ignition | rocketh | @wagmi/cli alone | |
|---|---|---|---|---|
| Primary job | Deploy + source of truth + typed access | Deploy (Hardhat-native) | Deploy + runtime env | Generate typed access from ABIs + addresses |
| Foundry support | Yes | No / limited | Yes | N/A (you supply addresses) |
| Idempotent deploys | Built-in (getOrDeploy) | Varies | Yes | N/A |
| Output | deployments/*.json | Deployments / Ignition journal | Records + runtime | Generated TS |
| App runtime dep | None (plain JSON + viem) | Often coupled | Runtime environment | None |
| viem-first | Yes | ethers-era | viem-oriented | Yes |
hardhat-deploy / Hardhat Ignition
Great at deploying inside Hardhat. They stop at deployment — addresses and ABIs still need manual wiring into your app. deployoor works with Foundry too, and the deployments/ record is designed to be consumed anywhere.
rocketh
Closest philosophically (also from the hardhat-deploy lineage). rocketh ships a runtime environment; deployoor keeps deploy scripts as plain viem clients plus generated functions, with JSON records as the stable boundary.
@wagmi/cli
Excellent at turning ABIs + addresses into typed React hooks and actions. But you supply those addresses — often copy-pasted from deploy scripts. deployoor produces them as a byproduct of your own deploys (including local and testnet chains explorers never see), then feeds wagmi via @deployoor/wagmi. They compose; deployoor is not a wagmi replacement.
When to pick deployoor
- You want a committed JSON source of truth that outlives any single tool
- You use viem (or wagmi) and want typed contracts without copy-paste
- You need idempotent deploy scripts that are safe to re-run in CI
- You work across Hardhat and/or Foundry with the same deploy model
Migration
A step-by-step migration guide from hardhat-deploy, Ignition, and Foundry broadcasts is in progress. Open a discussion if you want help migrating a specific project.