Deploying your app

Deploy to Vercel, Netlify, AWS, GCP, Railway, or Render with one click — including the build process, platform config, and CI/CD pipelines.

Deploying your app

VibeCaaS deploys your application to every major cloud platform. Pick the target that fits your needs — static hosting, serverless functions, containers, or full VMs — and every deployment includes automatic SSL, a CDN, and monitoring.

This builds on Environments & secrets; to put your app on your own domain afterwards, see Custom domains.

Supported platforms

PlatformBest forNotable features
VercelNext.js and React appsEdge functions, preview deployments, automatic SSL
NetlifyJAMstack and static sitesForm handling, functions, split testing
AWSEnterprise-grade infrastructureEC2, Lambda, ECS/Fargate, Elastic Beanstalk
Google CloudScalable managed infrastructureApp Engine, Cloud Run, Firebase
RailwaySimple full-stack appsAutomatic database provisioning, rollbacks
RenderUnified build-and-run platformAuto-deploy from Git, managed databases, cron jobs

The deployment process

Every deployment follows four steps:

  1. Build — optimize and bundle your application.
  2. Configure — set environment variables and domains.
  3. Deploy — push to production servers.
  4. Monitor — track performance and errors.

Trigger it with one click from your dashboard, or from the CLI:

vibecaas deploy --prod

Platform configuration

Vercel

Deploy Next.js and React apps with zero configuration.

npm i -g vercel
vercel
 
# Or deploy via Git integration
git push origin main

Netlify

Configure the build and redirects in netlify.toml:

[build]
  command = "npm run build"
  publish = "dist"
 
[[redirects]]
  from = "/api/*"
  to = "/.netlify/functions/:splat"
  status = 200

AWS

Use Amplify for hosting, or S3 + CloudFront for static assets:

amplify init
amplify add hosting
amplify publish

Google Cloud

Define an App Engine service in app.yaml:

runtime: nodejs18
 
handlers:
  - url: /.*
    script: auto
 
env_variables:
  NODE_ENV: "production"

Railway

railway login
railway link
railway up

Railway automatically provisions PostgreSQL, MySQL, Redis, and MongoDB databases.

Render

# render.yaml
services:
  - type: web
    name: my-app
    env: node
    buildCommand: npm install && npm run build
    startCommand: npm start

CI/CD pipelines

Wire up continuous deployment so a push to main builds, tests, and ships automatically.

# .github/workflows/deploy.yml
name: Deploy to Production
 
on:
  push:
    branches: [main]
 
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
      - run: npm ci
      - run: npm run build
      - run: npm run test
      - name: Deploy to Vercel
        run: vercel --prod --token=$VERCEL_TOKEN

The pipeline runs three phases: test (automated tests), build (production bundle), and deploy (push to production).

Best practices

  • Environment variables — never commit secrets to Git. Use platform secret management for keys and connection strings. See Environments & secrets.
  • Health checks — implement health-check endpoints so failed deployments roll back automatically.
  • Zero-downtime deploys — use blue-green deployments or rolling updates to stay available during releases.
  • Resource optimization — enable caching, CDN, and compression to cut server load and response times.

Next steps