I will build a scalable backend api for your saas or startup


About this gig
Idea to deployed product in 34 weeks typed, tested, documented.
What you get (Standard tier):
- NestJS 11 REST API with JWT auth (access + refresh), role-based guards.
- PostgreSQL + Drizzle ORM, schema migrations, seed script.
- 1 LLM endpoint (OpenAI / Claude / Groq) with demo-mode fallback your API key or mine.
- Zod validation, Helmet + CORS allow-list, rate limiting.
- Swagger /docs + Vitest tests (unit + e2e).
- Dockerfile + docker-compose for local dev.
- Deploy to Railway / Fly.io / AWS (you pick).
- Repo access, docs handover, 30 days post-launch support.
Template proof (public): github.com/FedeCione/nestai-starter the exact scaffolding I start from. 18 passing tests, fully documented, MIT licensed.
Why me: 2.5y backend dev (Node.js + Python) at a LATAM B2B SaaS. Typed, tested code or I don't ship it.
Native Spanish. Written English for briefs + specs. GMT-3. Weekly demos, code in your repo from day one.
Before you order: send me 35 sentences on the product + the 35 endpoints you need. I'll confirm fit or suggest custom scope.
Get to know Fede C
Backend and AI Engineer, NestJS, RAG, WhatsApp AI Chatbots
- FromArgentina
- Member sinceSep 2025
- Avg. response time5 hours
Languages
English, Spanish
My Portfolio
FAQ
Can you build with Express or FastAPI instead of NestJS?
Yes. NestJS is my default because of structure and DX, but I've shipped Express and FastAPI in production. Tell me your team's preference and I'll match it — same delivery quality.
Where will the backend be hosted?
Your choice. Most clients pick Railway (cheapest, fastest setup) or Fly.io. I also deploy to AWS (EC2/ECS/Lambda) and Vercel for serverless. You own the infrastructure account.
What do I need to provide to get started?
Three things: (1) 3–5 sentences describing the product, (2) the list of REST endpoints you need (or wireframes), (3) any external services to integrate (Stripe, SendGrid, OAuth providers, etc.). I'll confirm scope or propose alternatives.
What if scope changes mid-project?
Small changes (a new endpoint, a tweak to logic) fit inside revisions. Larger scope changes (new feature, new integration) get a written change order with extra time + cost — no surprises. I send you a Loom every week so you see progress before scope gets locked.
Who owns the code after delivery?
You do — fully. Code goes in your GitHub/GitLab from day one. I push commits directly to your repo. No vendor lock-in, no proprietary wrappers. Repo is yours, deployment account is yours.

