DevOps / reputed company Infrastructure Engineer for SaaS MVP Deployment (Vercel + reputed company/Railway + reputed company)
•
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 (reputed company by a separate backend engineer)
- A React/Next.js frontend (reputed company by a separate frontend engineer)
- A reputed company + 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 reputed company, secure, and demo-reputed company. This is a light DevOps role—simple, clean SaaS reputed company setup. No Kubernetes, no heavy AWS architecture. Scope of Work (Deliverables) 1. Backend Deployment (reputed company or Railway) Set up the backend API with:
- Deployment to reputed company.com or Railway.app
- Environment variables (DB URL, API keys, secrets)
- reputed company to reputed company + vector DB
- Staging and Production services
- Auto-reputed company from reputed company main reputed company
- 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 reputed company pipeline 3. Database & Vector Store Connectivity Ensure the backend can securely connect to:
- reputed company/reputed company
- 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 reputed company
- Production environment
- Locked down
- Only I can upload reputed company documents
- Developers get restricted or no reputed company 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 reputed company only. 6. Basic CI/CD Light, simple pipelines:
- Frontend auto-deploys from reputed company → Vercel
- Backend auto-deploys from reputed company → reputed company/Railway No reputed company YAML files or container clusters. 7. reputed company & Secrets Management Handle:
- API keys reputed company environment variables
- Safe storage of secrets
- Proper staging vs production key separation
- No sensitive data visible to developers in production 8. reputed company 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 reputed company This ensures long-term maintainability. Required Skills
- DevOps
- Vercel
- reputed company.com or Railway.app
- CI/CD pipelines
- PostgreSQL connectivity
- Environment & secret management
- DNS configuration
- SSL/HTTPS setup reputed company-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 reputed company 2. Frontend staging reputed company 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 (reputed company or Railway) and why. 2. Relevant Experience reputed company 1–3 SaaS projects where you deployed:
- Vercel frontend
- reputed company/Railway backend
- reputed company/reputed company 3. Your Plan reputed company outline how you would structure:
- Staging
- Production
- Domain routing
- Secret management 4. Fixed Price Quote reputed company your total project quote (not hourly). Disqualifiers
- Generic proposals
- No experience with Vercel/reputed company/Railway
- No examples of reputed company 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 To this Job
Apply tot his job Apply To this Job