Skip to main content

Vercel integration

Automatic deployment for web apps and backends.

Overview​

Appifex deploys to Vercel automatically:

  • Web apps → Vercel hosting
  • Backends → Vercel Serverless Functions

No configuration needed - it just works.

What you get​

Instant deployment​

Every code change triggers a new deployment.

Global CDN​

Your app is served from edge locations worldwide.

HTTPS included​

SSL certificates configured automatically.

Preview URLs​

Each deployment gets a unique URL for testing.

Deployment process​

  1. You make changes in Appifex
  2. Code pushed to GitHub
  3. Vercel detects the push
  4. Build runs automatically
  5. App deployed to production

URLs​

Project URL​

Your main app URL:

your-project.vercel.app

Preview URLs​

Each deployment gets a preview:

your-project-abc123.vercel.app

Custom domains​

Add your own domain:

  1. Go to Vercel dashboard
  2. Select your project
  3. Go to Settings → Domains
  4. Add your domain
  5. Update DNS records

Build settings​

Appifex configures Vercel automatically:

Web apps​

  • Framework: Vite/React
  • Build command: npm run build
  • Output directory: dist

Backends​

  • Framework: Python/FastAPI
  • Serverless functions
  • API routes at /api/*

Environment variables​

Sensitive data is stored securely:

  1. Go to Vercel dashboard
  2. Select project → Settings → Environment Variables
  3. Add your variables

Or configure in Appifex when adding integrations.

Monitoring​

Build logs​

View in Vercel dashboard:

  • Build progress
  • Error messages
  • Deploy time

Analytics​

Vercel provides:

  • Visitor analytics
  • Performance metrics
  • Error tracking

Troubleshooting​

Build failed​

  1. Check error message in Appifex activity log
  2. View full logs in Vercel dashboard
  3. AI Fix Agent often resolves common issues

Slow builds​

  • Large dependencies take longer
  • First builds are slower (cold cache)
  • Subsequent builds use cache

Domain not working​

  1. Verify DNS settings
  2. Wait for propagation (up to 48 hours)
  3. Check SSL certificate status

Best practices​

Use preview URLs for testing​

Test changes before they go live.

Monitor build times​

Large builds may indicate optimization opportunities.

Set up alerts​

Configure notifications for failed deployments.