VERCEL DEPLOYMENT

 

Hobby (Free) Plan

You can have up to 200 projects (websites/apps) under one account. Each project can have its own:

• Production deployment
• Preview deployments
• Custom domain (optional)
• GitHub repository or folder in a monorepo

Other important Hobby limits include:

• 100 deployments per day
• 1 concurrent build
• 45 minutes maximum build time per deployment

Pro Plan ($20/month)

• Unlimited projects
• 6,000 deployments per day
• Faster builds and more resources

Enterprise Plan

• Unlimited projects with custom enterprise limits and additional collaboration and security features.

For your use case

Since you've been building multiple React/Vite projects such as:

• Galaxy EduCore Portal
• CCYI Global Academy
• Library Management System
• Staff Training Portal
• Other CCYI websites

you can comfortably host all of them on a single free Vercel Hobby account, provided you stay within the usage limits. You have room for up to 200 separate projects, which is far more than most individual developers need.

If your goal is to host many client websites, you can either:

• Create one Vercel account and manage up to 200 projects (Hobby), or
• Upgrade to Pro when you need unlimited projects, team collaboration, or higher deployment limits.

Given the number of educational and business projects you're planning, a single Vercel account should be sufficient for quite a while before you'd need to upgrade.

what steps can i take to deploy on vercel

Since you're already using React, Vite, GitHub, and VS Code, deploying to Vercel is straightforward. Vercel automatically detects Vite projects and configures the build settings in most cases.

Option 1: Deploy from GitHub (Recommended)

Step 1: Push your project to GitHub

Open VS Code and run:

git init
git add .
git commit -m "Initial commit"
git branch -M main
git remote add origin https://github.com/YOUR_USERNAME/YOUR_REPOSITORY.git
git push -u origin main

Or use the Source Control panel in VS Code.

Step 2: Sign in to Vercel

1. Go to https://vercel.com
2. Click Continue with GitHub
3. Authorize Vercel to access your GitHub account.

Step 3: Import your project

1. Click Add New Project
2. Select your GitHub repository.
3. Click Import.

Vercel usually detects that it is a Vite/React project automatically.

Step 4: Verify the build settings

Normally these are filled in automatically:

Setting	Value
Framework	Vite
Build Command	npm run build
Output Directory	dist
Install Command	npm install

Step 5: Deploy

Click Deploy.

Within about a minute, you'll receive a URL such as:

https://your-project.vercel.app

Option 2: Deploy from VS Code using the Vercel CLI

Install the CLI:

npm install -g vercel

Login:

vercel login

Move into your project folder:

cd your-project

Deploy:

vercel

For a production deployment:

vercel --prod

The CLI will guide you through linking the project and deploying it.

Every time you update your website

If your project is connected to GitHub:

git add .
git commit -m "Updated homepage"
git push

Vercel will automatically build and deploy the latest version. Every push to your production branch creates a new production deployment, while other branches can generate preview deployments.

Add your own domain (Optional)

After deployment:

1. Open your project in Vercel.
2. Go to Settings → Domains.
3. Add your custom domain (for example, ccyiglobal.org).
4. Update your DNS records as instructed by Vercel.

Common deployment errors

If deployment fails, check for:

• Missing package.json
• Build errors (npm run build should work locally)
• Incorrect import paths
• Missing environment variables (.env)
• Wrong output folder (should be dist for Vite)

I can also help you deploy your projects

Based on what we've worked on together, I can walk you through deploying any of these:

• ✅ Galaxy EduCore Portal
• ✅ CCYI Global Academy
• ✅ CCYI Library Management System
• ✅ Covenant University Staff Training Portal
• ✅ Any React/Vite project

If you share your GitHub repository (or the project folder), I'll guide you through the deployment and help resolve any build errors until the site is live.