Exa Production Checklist

Overview

Complete checklist for deploying Exa integrations to production.

Prerequisites

• •Staging environment tested and verified
• •Production API keys available
• •Deployment pipeline configured
• •Monitoring and alerting ready

Instructions

Step 1: Pre-Deployment Configuration

• • Production API keys in secure vault
• • Environment variables set in deployment platform
• • API key scopes are minimal (least privilege)
• • Webhook endpoints configured with HTTPS
• • Webhook secrets stored securely

Step 2: Code Quality Verification

• • All tests passing (npm test)
• • No hardcoded credentials
• • Error handling covers all Exa error types
• • Rate limiting/backoff implemented
• • Logging is production-appropriate

Step 3: Infrastructure Setup

• • Health check endpoint includes Exa connectivity
• • Monitoring/alerting configured
• • Circuit breaker pattern implemented
• • Graceful degradation configured

Step 4: Documentation Requirements

• • Incident runbook created
• • Key rotation procedure documented
• • Rollback procedure documented
• • On-call escalation path defined

Step 5: Deploy with Gradual Rollout

# Pre-flight checks
curl -f https://staging.example.com/health
curl -s https://status.exa.com

# Gradual rollout - start with canary (10%)
kubectl apply -f k8s/production.yaml
kubectl set image deployment/exa-integration app=image:new --record
kubectl rollout pause deployment/exa-integration

# Monitor canary traffic for 10 minutes
sleep 600
# Check error rates and latency before continuing

# If healthy, continue rollout to 50%
kubectl rollout resume deployment/exa-integration
kubectl rollout pause deployment/exa-integration
sleep 300

# Complete rollout to 100%
kubectl rollout resume deployment/exa-integration
kubectl rollout status deployment/exa-integration

Output

• •Deployed Exa integration
• •Health checks passing
• •Monitoring active
• •Rollback procedure documented

Error Handling

Examples

Health Check Implementation

async function healthCheck(): Promise<{ status: string; exa: any }> {
  const start = Date.now();
  try {
    await exaClient.ping();
    return { status: 'healthy', exa: { connected: true, latencyMs: Date.now() - start } };
  } catch (error) {
    return { status: 'degraded', exa: { connected: false, latencyMs: Date.now() - start } };
  }
}

Immediate Rollback

kubectl rollout undo deployment/exa-integration
kubectl rollout status deployment/exa-integration

Resources

• •Exa Status
• •Exa Support

Next Steps

For version upgrades, see exa-upgrade-migration.