One-click
deployments
for teams
Stop wrestling with deployment scripts. ShipFlow gives your team instant deployments, rollbacks, and version tracking through GitHub Issues. Works with any CI/CD pipeline.
Free forever for small teams. Be the first to know.
# Just create an issue with these labels:
labels: ["deployment", "prod"]
# ShipFlow handles the rest:
Application: @myapp/web
Version: 2.4.1
Deployed in 47 seconds
# Wiki updated, team notified, rollback ready Works with:
Everything you need to ship faster
Stop context-switching between terminals, dashboards, and Slack. Deploy from where you already work.
One-Click Deploys
Deploy any app to any environment with a single GitHub Issue. Non-technical team members can deploy too.
Deployment Queue
One deployment at a time per environment. No race conditions, no overwrites. See your position in the queue.
Quick Rollbacks
Something wrong? Roll back to any previous version in seconds. One click from the wiki dashboard.
Version Dashboard
Auto-generated wiki shows what version is deployed where. Never lose track of your environments.
Monorepo Native
Built for monorepos. Deploy individual apps independently with proper versioning and changelogs.
Works With Anything
Vercel, Netlify, AWS, custom scripts. ShipFlow wraps your existing deployment, not replaces it.
Up and running in 5 minutes
Three simple steps. No infrastructure changes. Works with your existing CI/CD pipeline.
Install the Action
Add ShipFlow to your repo with a single workflow file. Run the init command to set up issue templates.
- uses: shipflow/action@v1
with:
action: init
license_key: ${{ secrets.SHIPFLOW_LICENSE_KEY }} Create an Issue
Use the generated issue templates to deploy. Select your app, version, and environment.
# New Issue: "Deploy web 2.4.1 to prod"
labels: ["deployment", "prod"]
Application: @myapp/web
Version: 2.4.1 Watch It Deploy
ShipFlow builds, deploys, updates the wiki, and closes the issue. Track everything in one place.
Deployment successful in 47s
Wiki updated: Deployment-Status
Tagged: @myapp/web@prod
Issue #142 closed Get early access
We're building the deployment tool teams actually want. Join the waitlist and be the first to know when we launch.
Free forever for small teams. No spam, unsubscribe anytime.
Frequently asked questions
- How does the deployment queue work?
- ShipFlow ensures only one deployment runs per app/environment at a time. If someone else is deploying, you'll see your position in the queue. This prevents race conditions and failed deploys from concurrent changes.
- What counts as a "seat"?
- A seat is any GitHub user who creates deployment issues. Read-only access to the wiki dashboard is free. You only pay for users who deploy.
- Does it work with private repositories?
- Yes! ShipFlow works with both public and private repositories. Your code and deployment logs never leave GitHub.
- Can I use my existing CI/CD pipeline?
- Absolutely. ShipFlow wraps your existing deployment scripts or integrates directly with Vercel, Netlify, and AWS. It orchestrates, not replaces.
- How does the wiki dashboard work?
- ShipFlow automatically updates your repository's GitHub Wiki after each deployment. It shows current versions, deployment history, and provides one-click deploy/rollback buttons.
- What happens if deployment fails?
- The issue stays open with error logs. Fix the issue and comment to retry, or use the rollback button to restore the previous version. The lock is released so others can deploy.
- Do you support monorepos?
- Yes! ShipFlow was built for monorepos. Deploy individual apps with independent versioning. Works great with Turborepo, Nx, and Lerna.
- Can I try before buying?
- Yes! The Starter plan is free forever for up to 3 team members and 1 repository. Perfect for trying out ShipFlow before upgrading.