How I Saved My Company Money: Bypassing Vercel’s $20/Seat Fee with GitHub Actions
A step-by-step guide to automating deployments, removing bottlenecks, and cutting overhead costs using Vercel CLI.
The $20 Bottleneck
I love Vercel. For frontend developers, it is hands down one of the best hosting platforms out there — fast, intuitive, and developer-friendly. But for small teams and startups, there is one major headache: The Pricing.
At $20 per user per month, the costs stack up quickly. In my previous team, we tried to be frugal. To save budget, we authorized only one admin account to handle deployments on Vercel.
The result? A massive bottleneck.
Every time a developer finished a feature, they had to ping that one specific person: “Bro, can you merge and deploy this?”
It was a nightmare. We had created a human dependency in an era where everything should be automated. That one developer became a glorified “deploy button,” while the rest of the team sat idle, waiting for the release.
I realized there had to be a better way. Why should we pay extra just to trigger a build? That is when I found the solution: Bypassing the seat limit by delegating the work to a robot — specifically, GitHub Actions.
The Loophole: GitHub Actions Free Tier
Here is the math that Vercel doesn’t tell you explicitly.
GitHub Actions provides 2,000 free automation minutes per month for public and private repositories (on the Free plan). For a small team, a typical frontend build takes about 2–3 minutes. That means you can run roughly 600 to 1,000 deployments per month for free.
Unless your team is deploying every 10 minutes, 24/7, you will likely never hit this limit.
By moving the deployment responsibility from a “paid human seat” on Vercel to a “free robot” on GitHub, we eliminate the cost entirely. The secret weapon is the Vercel CLI. It allows the GitHub runner to authenticate and trigger deployments just like a developer would from their local terminal, but automatically.
Step-by-Step: Setting Up the Workflow
Here is how we automated our pipeline using the Vercel CLI and GitHub Actions.
1. Gather Your Credentials To make the “robot” trusted by Vercel, you need three pieces of information:
- Vercel Token: Generate this in your Vercel Account Settings (Tokens).
- Project ID: Found in your Project Settings on Vercel (or in .vercel/project.json if you link locally).
- Org ID: Found in your Account/Team Settings.
2. Set Secrets in GitHub Go to your GitHub Repository > Settings > Secrets and variables > Actions. Add these as “Repository Secrets” to keep them safe:
- VERCEL_TOKEN
- VERCEL_PROJECT_ID
- VERCEL_ORG_ID
3. The Workflow Script Create a file in your repo at .github/workflows/deploy-preview.yml. This script uses pnpm (because it’s fast) and the official Vercel CLI to build and deploy.
Here is the exact workflow I use:
name: Preview Deployment
on:
pull_request: branches: [main]
env:
VERCEL_ORG_ID: ${{ secrets.VERCEL_ORG_ID }}
VERCEL_PROJECT_ID: ${{ secrets.VERCEL_PROJECT_ID }}
jobs: Deploy-Preview: runs-on: ubuntu-latest steps:
- uses: actions/checkout@v4
- name: Install pnpm
uses: pnpm/action-setup@v3
with:
version: 8
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '20.x'
cache: 'pnpm'
- name: Install Vercel CLI
run: npm install --global vercel@latest
- name: Pull Vercel Environment Info
# This pulls your env vars from Vercel UI
run: vercel pull --yes --environment=preview --token=${{ secrets.VERCEL_TOKEN }}
- name: Install Dependencies
run: pnpm install
- name: Build Project Artifacts
# Builds the app locally on the runner
run: vercel build --token=${{ secrets.VERCEL_TOKEN }}
- name: Deploy Project Artifacts to Vercel
# Uploads the .vercel/output folder
run: vercel deploy --prebuilt --token=${{ secrets.VERCEL_TOKEN }}
A Note on Ethics & Scaling
To be clear, this method is fully legal and uses Vercel’s official CLI tools. We aren’t “cracking” anything; we are simply optimizing our resources.
However, it is fair to mention that Vercel’s paid Team Plan ($20/seat) does offer value beyond just deployment access. It provides collaborative features like comments on preview deployments and easier role management via the dashboard.
For a small team focused on shipping code, this CLI automation is a perfect, cost-effective solution. But as your organization scales to an Enterprise level where cross-team collaboration is critical, paying for those native features might eventually be worth the investment.
The Results: Faster Releases, Zero Cost
After implementing this workflow, the impact was immediate.
1. $240/Year Savings Per Head We immediately cut the $20 monthly fee. It might seem small, but for a bootstrapped startup, every dollar counts. We are now leveraging the GitHub Actions free tier, which refreshes every month and is more than enough for our team’s volume.
2. The “Gatekeeper” is Free My colleague, who used to be the sole “Deployment Guy,” is the happiest person on the team. He no longer has to interrupt his deep work or flow state just to handle manual deployments. He can now focus entirely on coding complex features, knowing the pipeline handles the rest.
3. Accelerated Feature Velocity Most importantly, our release cycle is faster. Developers don’t wait in line anymore. Once a Pull Request is merged to main, the robot takes over, and the feature is live in minutes. We democratized the deployment process without sacrificing security or quality.