FOR STARTUP TEAMS

Onboard new engineers in minutes, not hours.

YOUR SITUATION

Your startup is growing. You've got product-market fit (or you're close). You're hiring. The team is scaling from 3 to 10 engineers.

But database migrations are becoming a team friction point:

• Merge conflicts in the migrations folder every other PR
• Onboarding is painful - new engineers struggle with 200+ migrations
• Flaky staging environments due to migration ordering issues
• Fear of deployments because migrations might break production

This isn't just a tech problem. It's slowing down your velocity.

THE PAIN POINTS

THE SOLUTION: CAPYSQUASH FOR TEAMS

3+ engineers? You need the CAPYSQUASH. Built for team collaboration and automation.

WHAT YOU GET

1. Eliminate Merge Conflicts

The problem:

# Two devs both create migration_003
migrations/
  migration_001.sql
  migration_002.sql
  migration_003.sql (from backend dev)
  migration_003.sql (from frontend dev) ← CONFLICT!

The solution:

• GitHub App catches this in PR
• Comments: "Warning: Duplicate migration number detected"
• Suggests automatic fix
• No more manual merge resolution

2. Onboarding Made Easy

Before:

# New hire's first day
git clone repo
npm install
# 3 hours later: "Why won't my migrations run?"
# 287 files, unclear order, historical conflicts

After:

# With CAPYSQUASH
git clone repo
npm install
# Runs 12 clean migrations in 10 seconds
# New hire is productive on day 1

3. Team Dashboard

Everyone sees migration health:

• PM: "Are migrations cleaned up?" → Check dashboard
• Tech Lead: "Which projects need attention?" → Multi-project view
• New Engineer: "What's the schema?" → Clean, consolidated view

REAL RESULTS: STARTUP CASE STUDY

Before CAPYSQUASH

4. Automated PR Checks

Every PR that touches migrations gets:

```markdown
## CAPYSQUASH Analysis

☑ Migrations analyzed successfully!

<ChartBar size={20} weight="bold" /> **Results:**
- New migrations: 3 files
- Consolidation opportunity: Can reduce to 1 file (67% reduction)
- Warnings: 0
- Deployment time saved: ~2 minutes

**What this gives you:**
- Visibility into every migration change
- Catches issues before merge
- Team learns best practices
- No manual checking needed

### 5. Role-Based Access Control

**Different roles for different needs:**

**Admin (Tech Lead/CTO):**
- Full access to everything
- Manage billing
- Invite/remove members
- Set organization defaults

**Member (Engineers):**
- Create/edit projects
- Run analyses
- View all projects
- Cannot manage billing/members

**Viewer (PM/Designers):**
- Read-only access
- View projects and results
- Cannot run analyses
- Cannot edit anything

## TEAM WORKFLOW EXAMPLE

### Scenario: Feature Branch with Migrations

**Day 1 - Developer adds migrations:**
```bash
# Developer works on feature branch
git checkout -b feature/user-profiles

# Adds 3 new migrations
supabase migration create add_profiles_table
supabase migration create add_avatars_column
supabase migration create add_profiles_rls

# Pushes to GitHub
git push origin feature/user-profiles

Day 1 - Automatic analysis:

• GitHub App triggers on PR creation
• Analyzes 3 new migrations
• Comments on PR:
  • "3 new migrations detected"
  • "Can consolidate to 1 file"
  • "No warnings"
  • "Deployment impact: +15 seconds"

Day 2 - PR review:

• Tech Lead sees analysis in PR
• Approves knowing migration impact
• Merges to main

Day 3 - Automated cleanup:

• Scheduled squashing runs weekly
• Consolidates all migrations from the week
• Opens PR with cleaned migrations
• Team reviews and merges

Result:

• Zero manual migration management
• Team stays focused on features
• Migration health visible to everyone

ROI CALCULATION

GETTING STARTED

Step 1: Sign Up

Create free account →

Step 2: Create Organization

• Name your organization (e.g., "Acme Startup")
• Invite team members
• Set default safety level (recommend: standard)

Step 3: Set Up First Project

• Create project (e.g., "Production API")
• Connect GitHub repository
• Install GitHub App
• Configure database connection (optional)

Step 4: Install GitHub App

• One-click install from organization settings
• Grant repository permissions
• Configure analysis settings
• Test with a sample PR

Step 5: Automate

• Set up weekly squashing schedule
• Configure webhook notifications (optional)
• Add Slack integration for team updates
• Enjoy automated migration management

Full setup guide →

MIGRATION FROM capysquash-cli

Already using capysquash-cli? Easy migration:

1. Keep using capysquash-cli locally - Nothing changes for local dev
2. Add CAPYSQUASH Platform for team features - GitHub automation, dashboards
3. Use both together - capysquash-cli for speed, CAPYSQUASH Platform for collaboration

Example workflow:

# Developer uses capysquash-cli for local quick checks
capysquash analyze migrations/

# Opens PR → CAPYSQUASH automatically analyzes
# Team reviews in CAPYSQUASH dashboard

# Production squashing via CAPYSQUASH (audit trail)
# API automates deployment pipeline

PRICING

View detailed pricing →

COMMON QUESTIONS

Q: Can we try it free first? A: Yes! Free plan includes 3 projects, 10 analyses/month, and 3 team members.

Q: What if we're still small (3-5 people)? A: Try the free plan. Upgrade to Professional when you hit limits or need GitHub automation.

Q: Can we keep using capysquash-cli too? A: Absolutely. Many teams use capysquash-cli for local dev and CAPYSQUASH Platform for team features.

Q: How long does setup take? A: 15 minutes for complete setup including GitHub App installation.

Q: What if we need on-premise? A: Enterprise plan includes on-premise deployment. Contact sales →

WHAT STARTUP TEAMS ARE SAYING

"Onboarding new engineers went from 3 hours to 10 minutes. This paid for itself in week 1."

• CTO, Series A Startup

"No more migration merge conflicts. Our velocity increased noticeably."

• Tech Lead, Y Combinator Startup

"The PM loves the dashboard. Finally visibility into migration health without asking engineers."

• Founding Engineer, Seed Stage

NEXT STEPS

Additional Resources

• GitHub Integration Guide
• API Documentation
• Team Collaboration Guide
• CLI vs Platform Comparison

Ready to eliminate migration friction? Start your free trial →