> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hyperlane.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

To launch your Hyperlane deployment into a production environment, follow these steps to set up your chain’s core deployment and configure Hyperlane Warp Route (HWR) deployments.

### 1. Core Deployment

To begin you'll need to set up and productionize the core components of your Hyperlane deployment.

<Columns cols={2}>
  <Card title="Update Mailbox Default ISM" icon="link" href="./core-deployment/update-mailbox-default-ism">
    Update the Interchain Security Module (ISM) associated with the Mailbox
    contract. The ISM acts as a critical security layer, verifying messages
    between chains. Ensure that the default ISM settings align with your
    security requirements.
  </Card>

  <Card title="Transfer Mailbox Ownership" icon="link" href="./core-deployment/transfer-mailbox-ownership">
    Transfer ownership of the Mailbox contract to a production-ready owner
    account. This step secures the Mailbox by ensuring only trusted parties have
    control over its configuration.
  </Card>
</Columns>

### 2. HWR Deployment

<Columns cols={2}>
  <Card title="Remove Trusted Relayer" icon="link" href="./warp-route-deployment/remove-trusted-relayer">
    Remove any test or development relayers that may have been configured
    initially. In production, ensure that only trusted, secure relayers are
    used to prevent unauthorized message relaying.
  </Card>

  <Card title="Transfer HWR Ownership" icon="link" href="./warp-route-deployment/transfer-warp-route-ownership">
    Transfer ownership of the HWR to the designated production owner. This step ensures that only trusted parties have control over critical HWR settings, such as ISM configurations, Validator options, and relayer settings.
  </Card>
</Columns>