DevOps / Cloud Infrastructure Engineer for SaaS MVP Deployment (Vercel + Render/Railway + Supabase)

• ** Please read thoroughly or your application could be denied!! *** Please read the entire post, include the answers to the questions listed along with your estimate or your application will be denied. Project Overview I’m building an MVP for a multi-tenant SaaS platform that includes: • A backend retrieval API (built by a separate backend engineer) • A React/Next.js frontend (built by a separate frontend engineer) • A Postgres + vector database • Requirements for clean staging and production environments I need a DevOps/Infrastructure engineer to configure the hosting, deployments, environment variables, and domain routing so the system is stable, secure, and demo-ready. This is a light DevOps role—simple, clean SaaS infra setup. No Kubernetes, no heavy AWS architecture. Scope of Work (Deliverables) 1. Backend Deployment (Render or Railway) Set up the backend API with: • Deployment to Render.com or Railway.app • Environment variables (DB URL, API keys, secrets) • Connection to Postgres + vector DB • Staging and Production services • Auto-deploy from GitHub main branch • Basic logs and error monitoring 2. Frontend Deployment (Vercel) Set up the Next.js frontend with: • Staging environment • Production environment • Environment variables • Domain routing (app.domain.com) • SSL certificates / HTTPS • Automatic deploy pipeline 3. Database & Vector Store Connectivity Ensure the backend can securely connect to: • Supabase/Postgres • Vector database (pgvector or equivalent) You do NOT design schemas — just infrastructure connectivity. 4. Environment Isolation (Critical) Configure: • Staging environment • Developers use this • Test documents only • Full developer access • Production environment • Locked down • Only I can upload real documents • Developers get restricted or no access Proper isolation is essential. 5. Domain / DNS / Routing Setup Configure routing for both environments: • DNS records for frontend • DNS records for backend • SSL/HTTPS • Health checks • URL testing and confirmation Domain is owned by me; you get limited access only. 6. Basic CI/CD Light, simple pipelines: • Frontend auto-deploys from GitHub → Vercel • Backend auto-deploys from GitHub → Render/Railway No complex YAML files or container clusters. 7. Security & Secrets Management Handle: • API keys via environment variables • Safe storage of secrets • Proper staging vs production key separation • No sensitive data visible to developers in production 8. Handoff Documentation (Deployment Runbook) A short document explaining: • How staging & production are configured • How deployments work • How to rotate secrets • How to add new organizations • How to recover from a failed deploy This ensures long-term maintainability. Required Skills • DevOps • Vercel • Render.com or Railway.app • CI/CD pipelines • PostgreSQL connectivity • Environment & secret management • DNS configuration • SSL/HTTPS setup Nice-to-have: • Next.js deployment experience • Multi-environment SaaS experience You are only setting up the infrastructure. Project Model • Fixed price • Milestones preferred: 1. Backend staging deploy 2. Frontend staging deploy 3. Production setup + hardening 4. Runbook delivery • Timeline: ~7–10 days depending on experience How to Apply (Follow These Steps) 1. Short Explanation Tell me which backend platform you prefer (Render or Railway) and why. 2. Relevant Experience Share 1–3 SaaS projects where you deployed: • Vercel frontend • Render/Railway backend • Postgres/Supabase 3. Your Plan Briefly outline how you would structure: • Staging • Production • Domain routing • Secret management 4. Fixed Price Quote Provide your total project quote (not hourly). Disqualifiers • Generic proposals • No experience with Vercel/Render/Railway • No examples of real SaaS deployments • Proposals that ignore staging vs production separation • “DevOps teams” or agencies applying for a simple MVP role If you can set up a clean, secure SaaS infrastructure quickly and reliably, I’d like to hear from you. Apply tot his job Apply tot his job