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

# Go Live with Rye: Production Checklist

> Learn how to move your Rye integration from staging to production.

<Steps>
  <Step title="Create a production account">
    1. Create a production account at [**console.rye.com**](https://console.rye.com/register).
    2. Copy your **Production API key** from the [Account page](https://console.rye.com/account).
    3. Get Rye's **live Stripe publishable key** (you'll use it to tokenize cards on the client).

    <Warning>
      Note that you must use Rye’s Stripe publishable key, not your own Stripe key. Using your own Stripe key will cause an error when confirming the checkout intent.
    </Warning>
  </Step>

  <Step title="Set production environment variables">
    Update your deployment environment to use production values.

    ```bash theme={null}
    RYE_API_KEY=                                 # From https://console.rye.com/account
    RYE_API_BASE=https://api.rye.com             # Production base URL
    NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=pk_live_51LgDhrHGDlstla3fOYU3AUV6QpuOgVEUa1E1VxFnejJ7mWB4vwU7gzSulOsWQ3Q90VVSk1WWBzYBo0RBKY3qxIjV00LHualegh # Rye’s live publishable key
    ```
  </Step>

  <Step title="Enable HTTPS and app hardening">
    Ensure your application is secure and compliant.

    * Force HTTPS.
    * Review CORS to allow only your production origin(s).
    * Add a CSP, secure cookies, and rate limiting (or WAF) at the edge.
  </Step>

  <Step title="Observability and alerts">
    * Emit metrics for key events: `intent created`, `awaiting_confirmation`, `confirmed`, `completed/failed`.
    * Add error tracking on the server and client.
    * Create on-call alerts for elevated failure rates.
  </Step>

  <Step title="Cutover test plan">
    * Run an end-to-end smoke test with your team using a low-risk product.
    * Validate: offer totals, tax/shipping, confirmation path, and post-order updates.
    * Have a rollback plan (env toggle back to staging).
  </Step>
</Steps>