Skip to content
Cased Documentation

Deploy Foundations

Learn the core concepts behind Cased’s deployment system
Cased Deploy Overview

Philosophy

Cased’s approach to deployments is built on three core principles:

  1. Enhance, Don’t Replace

    • Integrates with your existing GitHub Actions workflows
    • No need to rewrite deployment scripts
    • Adds safety, visibility, and control to your current process

  2. Developer Experience First

    • Clear UI for deployment operations
    • Real-time deployment status visibility
    • Streamlined approval workflows
    • Slack integration for common tasks

  3. Safety by Design

    • Built-in deployment queue management
    • Automated health monitoring
    • Intelligent rollback capabilities
    • Comprehensive audit trails

Core Concepts

Deployment Targets

A deployment target represents a specific environment where your code can be deployed. Each target:

  • Links to a specific GitHub Actions workflow
  • Has its own configuration and safety rules
  • Can be marked as production or non-production
  • Maintains its own deployment queue

Deployment Monitoring

Cased actively monitors deployments through multiple channels:

  1. Metrics Monitoring

    • System metrics (CPU, memory, etc.)
    • Application metrics
    • Custom metric support
    • Integrations with:
      • Datadog
      • CloudWatch

  2. Error Tracking

    • Sentry integration
    • Error rate monitoring
    • Exception tracking
    • Impact analysis

  3. Health Assessment

    • Real-time health status
    • Anomaly detection
    • Correlation analysis
    • Automatic rollback triggers

Deployment Safety

Cased implements multiple layers of deployment safety:

  1. Queue Management

    • Prevents concurrent deployments
    • Handles stale deployment cleanup
    • Configurable timeout settings
    • Environment-specific rules

  2. Approval Workflows

    • Required approvers configuration
    • Team-based approval rules
    • Time-window restrictions
    • Branch protection rules

  3. Auto-Rollback

    • Configurable health thresholds
    • Multiple monitoring services
    • Customizable rollback conditions
    • Automatic or manual triggers

Deployment Triggers

Deployments can be initiated through multiple channels:

  • GitHub pull request merges
  • Direct branch deployments
  • Slack commands
  • Web interface
  • API calls
  • CLI tools

Integration Points

Cased connects with your development workflow through:

  1. GitHub

    • Actions workflows
    • Repository integration
    • Branch protection
    • Pull request tracking

  2. Monitoring Tools

    • Datadog metrics
    • CloudWatch metrics
    • Sentry error tracking
    • Custom metric sources

  3. Communication

    • Slack notifications
    • Email alerts
    • Web dashboard
    • API webhooks

Best Practices

  1. Environment Strategy

    • Define clear deployment targets
    • Implement progressive deployment patterns
    • Use consistent naming conventions
    • Configure appropriate safety rules

  2. Monitoring Setup

    • Define key health metrics
    • Set appropriate thresholds
    • Configure comprehensive logging
    • Enable relevant integrations

  3. Team Workflow

    • Establish clear approval chains
    • Document deployment procedures
    • Set up appropriate notifications
    • Define emergency procedures

Getting Started

  1. Connect GitHub and set up your first deployment target
  2. Configure approval workflows
  3. Set up Slack integration