CAPYSQUASH

---

CAPYSQUASH documentation page.

---

Title: "CAPYSQUASH: CLI or Platform" Description: "Use CAPYSQUASH your way - free CLI or full Platform"

CAPYSQUASH: CLI or Platform

Use CAPYSQUASH your way: free CLI for solo devs or Platform for teams.

THE OPEN CORE MODEL

CAPYSQUASH gives you flexibility. Start with the free capysquash-cli for local development, or use the CAPYSQUASH Platform for team collaboration and visual workflows. Same powerful technology underneath.

Visual workflow with team features

Web-based platform with visual dashboards, GitHub automation, and team collaboration. Perfect for teams and individuals who want automation.

Free, open-source command-line tool

Fully-featured CLI powered by pgsquash-engine for developers who prefer terminal workflows and local-first development.

The upgrade path is about interface and automation, not features. CLI is powerful. Platform adds web UI, GitHub automation, project history, and analytics. Teams get collaboration features on top.

FEATURE COMPARISON

Featurecapysquash-cliCAPYSQUASH Platform
Core Analysis Engine☑ Full power☑ Same engine
Safety Levels☑ All 4 levels☑ All 4 levels
Docker Validation☑ Local☑ Cloud
AI Analysis☑ Optional☑ Optional
Pattern Detection
TUI Interface
Local-first
Team Collaboration
Multi-project Dashboard
Role-based Access Control
GitHub IntegrationManual☑ Automatic
Automated PR Comments
API Access
Webhooks
Activity Audit Log
White-label Branding☑ (Agency+)
SSO/SAML☑ (Enterprise)
Priority SupportCommunity☑ (Paid plans)

WHEN TO USE capysquash-cli

⌨️ TERMINAL-FIRST SCENARIOS

☑ Perfect for:

Terminal Lovers

You prefer command-line interfaces You want local-first workflows You're comfortable with shell scripts You're working offline or with sensitive data

Learning & Experimentation

First time trying migration squashing Exploring different safety levels Understanding how consolidation works Testing with sample projects

CI/CD Integration

You want to run squashing in your pipeline You're comfortable with shell scripts You need maximum flexibility You're already using CLI-based tools

Open Source Projects

Your project is public

Contributors use various setups

You want zero external dependencies

Community support is sufficient

Example Workflows:

# Quick local squash

pgsquash analyze migrations/
pgsquash squash migrations/ --safety standard

# CI/CD pipeline

pgsquash squash migrations/ --output clean/ --quiet
pgsquash validate migrations/ clean/

# Development with AI analysis

export ANTHROPIC_API_KEY="..."
pgsquash analyze-deep migrations/

WHEN TO USE CAPYSQUASH

🌐 WEB UI & AUTOMATION SCENARIOS

☑ Perfect for:

Web Interface Preference

You prefer visual dashboards over terminals You want drag-and-drop file uploads You need easy access from any device You want beautiful charts and analytics

Automation & History

Automatic GitHub PR analysis Track all squashes with before/after comparisons See optimization impact over time Get notifications for migration issues

Team Collaboration (when you need it)

Multiple developers working together Share projects and configurations Role-based access control Activity audit logs

Agency Work

Managing multiple client projects Need professional reporting White-label branding required Client handoff documentation

Enterprise Requirements

Compliance and audit trails needed

SSO/SAML authentication required

Cross-team collaboration

SLA guarantees needed

Example Workflows:

Team Lead: Creates project, sets safety level, invites team

Developer: Opens PR → Automatic analysis → Results commented

Manager: Reviews multi-project dashboard → Sees migration health

Agency: Manages 50 client projects from single dashboard

PERSONA-DRIVEN DECISION GUIDE

The "Vibe Coder" / Indie Hacker

Your Pain: Project is getting slow and messy after months of prototyping.

Use pgsquash-engine if:

  • You love terminal workflows
  • You want local-first simplicity
  • You're comfortable with command-line tools

Use CAPYSQUASH if:

  • You prefer web interfaces over terminals
  • You want automatic GitHub PR analysis
  • You want to track optimization history visually
  • You're planning to collaborate with co-founders

Recommendation: Choose based on interface preference, not team size.

The Startup Generalist / Founding Engineer

Your Pain: Need to move fast, track changes, and prepare for team growth.

Use pgsquash-engine if:

  • You're deeply technical and CLI-native
  • You prefer scripting everything
  • Budget is extremely tight

Use CAPYSQUASH if:

  • You want web-based workflow
  • You need GitHub automation for PRs
  • You want to track migration health over time
  • You're onboarding non-technical stakeholders
  • Team is growing or will grow soon

Recommendation: CAPYSQUASH for velocity and visibility, even solo.

💼 The Agency Developer

Your Pain: Wasting non-billable hours, need professional deliverables.

Use pgsquash-engine if:

  • Managing 1-2 clients
  • Very price-sensitive
  • Comfortable with manual processes

Use CAPYSQUASH if:

  • Managing 3+ client projects
  • Need professional reporting
  • Want white-label branding
  • Billing hours for migration cleanup
  • Want multi-project dashboard

Recommendation: CAPYSQUASH (Agency plan) for efficiency and professionalism.

The Backend Specialist / "Closet DBA"

Your Pain: Technical sloppiness, redundant SQL, loss of control.

Use pgsquash-engine if:

  • You want maximum control
  • You prefer local-first tools
  • You're fine with manual workflows
  • You want to understand every detail

Use CAPYSQUASH if:

  • You need to collaborate with frontend devs
  • You want API access for custom tooling
  • You need audit trails for compliance
  • You want to prove ROI to management

Recommendation: Start with pgsquash-engine, add CAPYSQUASH when you need collaboration/automation.

MIGRATION PATH

You can always start with one and add the other later:

pgsquash-engine → CAPYSQUASH

EASY UPGRADE PATH

  1. Keep using pgsquash-engine locally for development
  2. Add CAPYSQUASH for: Team collaboration GitHub automation Multi-project management
  3. Use both together: pgsquash-engine for local quick checks CAPYSQUASH for production squashing API for custom automation

CAPYSQUASH → pgsquash-engine

ALWAYS HAVE THE OPTION

CAPYSQUASH uses the same engine as pgsquash-engine Can always export and run locally pgsquash-engine remains free and open-source forever No vendor lock-in

PRICING COMPARISON

pgsquash-engineCAPYSQUASH
IndividualFree foreverFree (3 projects)
Small TeamFree forever$12/mo (Creator)
Growing TeamFree forever$29/mo (Professional)
AgencyFree forever$99/mo (Agency)
EnterpriseFree foreverCustom pricing

pgsquash-engine will always be free and fully-featured. We build a sustainable business by solving team problems, not by crippling individual tools.

QUICK DECISION MATRIX

Choose pgsquash-engine if:

  • ☑ You prefer terminal-based workflows
  • ☑ You want local-first, offline-capable tools
  • ☑ You're comfortable with shell scripts
  • ☑ You don't need web UI or automation
  • ☑ You're on a tight budget

Choose CAPYSQUASH if:

  • ☑ You prefer web interfaces over terminals
  • ☑ You want automatic GitHub PR analysis
  • ☑ You need project history and analytics
  • ☑ You want beautiful dashboards
  • ☑ You manage multiple projects
  • ☑ You're working with a team (or planning to)

Use Both if:

  • ☑ You want the best of both worlds
  • ☑ pgsquash-engine for local dev, CAPYSQUASH for production
  • ☑ Different workflows for different contexts
  • ☑ Maximum flexibility

NEXT STEPS

Ready to start with capysquash-cli?

Ready to try CAPYSQUASH?

Still not sure?

How is this guide?

On this page