Skip to content
Documentation
Multi-Chain Deploy

Deployment Pipeline

Deploy frontends to Vercel and smart contracts to any supported EVM chain with auto-verification.

Two Types of Deployment

Create provides sandbox previews for development and production deployments for going live.

Sandbox Preview
Automatic on every code generation
  • • Every code generation auto-deploys to a Vercel sandbox
  • • Live preview in iframe with hot-reload
  • • Temporary URL (sb-*.vercel.run)
  • • Auto-redeploy when sandbox expires
Production Deployment
Ship to production when ready
  • • GitHub Integration: Push code via OAuth2 (custom commit message, branch selection)
  • • Vercel Production: Deploy frontend with a production URL
  • • Contract Deployment: Deploy smart contracts to blockchain (separate from frontend)

Smart Contract Deploy Flow

Contracts are compiled on the server with solc-js (Solidity ^0.8.20, OpenZeppelin v5) and deployed through the user's wallet.

1

Compile Contract

Server compiles the contract using solc-js with Solidity ^0.8.20 and OpenZeppelin v5.

2

Pre-flight Check

Gas estimate and constructor parameters review before deployment.

3

Wallet Confirmation

Wallet popup appears -- user confirms the transaction and pays gas from their own wallet.

4

Wait for Receipt

Wait for the transaction to be mined and receive the deployed contract address.

5

Auto-Verify on Block Explorer

Non-blocking verification on Basescan, Arbiscan, Optimism Etherscan, or Polygonscan.

DAO Governor Sequential Deploy

DAO Governor projects require deploying 3 contracts in sequence, each depending on the previous.

1

Deploy GovernanceToken

Deploy the ERC-20 governance token and retrieve the tokenAddress.

2

Deploy DAOTimelock

Deploy the timelock controller and retrieve the timelockAddress.

3

Deploy DAOGovernor

Deploy the governor contract using the tokenAddress and timelockAddress from previous steps.

4

Setup Roles & Renounce Admin

Configure proposer/executor roles on the timelock and renounce deployer admin privileges.

Supported Networks

Deploy to L2 EVM chains and Solana. Ethereum L1, Avalanche, BSC, zkSync, Scroll, and Linea are not supported.

MainnetProduction Networks
  • • Base (Chain ID: 8453)
  • • Arbitrum (Chain ID: 42161)
  • • Optimism (Chain ID: 10)
  • • Polygon (Chain ID: 137)
  • • Solana (mainnet-beta)
TestnetTesting Networks
  • • Base Sepolia (Chain ID: 84532)
  • • Arbitrum Sepolia (Chain ID: 421614)
  • • Optimism Sepolia (Chain ID: 11155420)
  • • Polygon Amoy (Chain ID: 80002)
  • • Solana (devnet)

Gas Estimates & Verification

Gas costs and block explorer verification details.

Gas Estimation
  • • Static lookup table per contract type and chain
  • • Testnets always show $0 estimated cost
  • • Estimates shown during pre-flight check
  • • Actual gas paid by user at time of transaction
Auto-Verification
  • • Basescan (Base)
  • • Arbiscan (Arbitrum)
  • • Optimism Etherscan (Optimism)
  • • Polygonscan (Polygon)
  • • Non-blocking -- deploy completes before verification finishes

Security Model

Create never holds private keys. All transactions are signed by the user.

User-Signed Transactions
The user always signs from their own wallet. The server never has access to private keys.
Mainnet Confirmation
All mainnet deployments require explicit user confirmation before the transaction is submitted.
Testnet Wallets
Testnet deployments use faucet-funded wallets so users can test without spending real funds.
Test First
Always deploy to a testnet first and verify all functionality before deploying to mainnet.

Ready to deploy?

Build your project in Create and deploy to any supported chain.

Start Building