deployoor.dev valid

deployoor

Deploy EVM contracts from TypeScript with your own viem wallet. A deploy is an artifact plus a client, so scripts, tests, and your app share typed contract objects. Hardhat and Foundry.

For agents: deployoor is a TypeScript library for deploying EVM smart contracts with a viem wallet, with Hardhat and Foundry support; includes full documentation and recipe

evm smart contractsviemtypescript deploymenthardhatfoundry

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T12:36:32.214Z. Cached copy · Source on deployoor.dev

# deployoor

Deploy EVM contracts from TypeScript with your own viem wallet. A deploy is an artifact plus a client, so scripts, tests, and your app share typed contract objects. Hardhat and Foundry.

## When to use deployoor

deployoor deploys EVM smart contracts from TypeScript with a viem wallet client you supply, records
every deploy as plain JSON under `deployments/<chainId>-<network>/`, and hands back a typed viem
contract object. It is an MIT-licensed npm package: no account, no API key, no hosted service.

Reach for it to:

- deploy a contract from a TypeScript script, with no framework runtime booted
- deploy the same contracts to several chains in one loop over viem clients
- make a deploy step idempotent, reusing a record unless the bytecode, constructor args or linked
  libraries changed
- sign with a wallet other than a raw private key: an encrypted keystore, cloud KMS, a Ledger,
  Privy, Turnkey, Coinbase CDP, Openfort, or a JSON-RPC account
- give an app typed contract access with no copied addresses or ABIs, through `@deployoor/wagmi`
- run integration tests over the real deploy path, in memory, through `@deployoor/testing`
- verify already-deployed contracts from committed records, with no recompile

Look elsewhere to compile or test Solidity (that stays with Hardhat or Foundry), to run a local
chain for a person to use, to orchestrate proxy upgrades, or if the project has no TypeScript.

How an agent should drive it: `pnpm add -D deployoor viem`, compile, then `npx deployoor generate`
to write `./deployers/`, then call the generated `getOrDeploy<Contract>({ walletClient,
publicClient, args })` from an ordinary Node script. Full instructions, including the API surface
and the mistakes that cost the most time, are at https://deployoor.dev/AGENTS.md.

## Documentation

- [Introduction](/introduction)
- [Comparisons](/comparison/)
- [Hardhat](/comparison/hardhat)
- [Hardhat Ignition](/comparison/hardhat-ignition)
- [hardhat-deploy](/comparison/hardhat-deploy)
- [Installation](/getting-started/installation)
- [Quickstart](/getting-started/quickstart)
- [Deployment records](/concepts/deployment-records)
- [Deployment stores](/concepts/deployment-stores)
- [Idempotency & redeployment](/concepts/idempotency)
- [Version control](/concepts/version-control)
- [Recipes](/recipes/)
- [Privy](/recipes/privy)
- [Coinbase CDP](/recipes/coinbase-cdp)
- [Turnkey](/recipes/turnkey)
- [Openfort](/recipes/openfort)
- [Deploy scripts](/guides/deploy)
- [Configuration](/guides/configuration)
- [Testing](/guides/testing)
- [Consume in your app](/guides/consumption)
- [Verify contracts](/guides/verify)
- [Plugins](/guides/plugins)
- [Hardhat](/guides/hardhat)
- [Foundry](/guides/foundry)
- [Upgrading to 0.7](/guides/upgrading)
- [Migrate from Hardhat scripts](/migrate/hardhat)
- [Migrate from Hardhat Ignition](/migrate/hardhat-ignition)
- [Migrate from hardhat-deploy](/migrate/hardhat-deploy)
…

Related sites

Find similar publishers by meaning →

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=deployoor.dev · GET /v1/domain/deployoor.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for deployoor.dev:
1. POST https://agentwebmap.com/v1/sites/deployoor.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://deployoor.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/deployoor.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/deployoor.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.