Postgres · Supabase · Firebase · Node
Backend architecture: auth, data, APIs and payments
CodeBlimp designs and builds the backend behind your web or mobile product — authentication, database, APIs, file storage and payments — on Postgres and Supabase by default, or Firebase when your product or your team prefers it. The backend is included in every SaaS MVP and mobile build (from ₹79,999 / $4,500); standalone backend work is quoted per scope after a call.
What's included
- Data model designed with you before any code — the schema is the product
- Authentication and roles: email, OTP, Google, Apple; admin, staff and customer permissions
- Postgres with row-level security (Supabase), or Firestore with security rules
- REST or server-action APIs with input validation on every endpoint
- Payments and subscriptions with Stripe or Razorpay, including webhooks and receipts
- File and image storage with signed URLs and size limits
- Background jobs, scheduled tasks and email or WhatsApp notifications
- Rate limiting, secrets management and security headers in production
- Backups, monitoring and an admin view of the data you need to see
- Documentation of the schema and endpoints, handed over with the repository
How a project runs
One person is accountable from the first call to handover. You see the real product on a staging link every week.
01Day 0 — Scoping
We map the entities, the roles and the money flow on one call. That drawing becomes the schema and the written scope.
02Week 1 — Foundation
Project, database, auth and the first protected endpoint live on staging. You can log in to something real within a week.
03Weeks 2–5 — Features
Endpoints and data flows ship weekly, each with validation and tests for the paths that touch money or personal data.
04Final week — Hardening
Security review, rate limits, backups verified, monitoring and alerts set up on your accounts.
05After launch
Care retainers cover dependency upgrades, database growth and new endpoints as the product evolves.
What it costs
Two price zones, no currency conversion: India pricing is capped at ₹1,00,000; international pricing is market-rate in USD. Every price is fixed once the written scope is approved.
| Tier | Scope | Timeline | India | International |
|---|---|---|---|---|
| SaaS / Web App MVP | Backend included: auth, database, APIs, billing and admin | 6–10 weeks | ₹79,999 | $4,500 |
| Full Product Build | Shared backend for web and mobile, dashboard, integrations | 12–20 weeks | ₹99,999 | $12,000 |
What moves the price
- Number of user roles and how different their permissions are
- Payments and subscriptions — one-off checkout is simple; metered billing is not
- Real-time requirements (live updates, chat) and third-party integrations
- Migration of data from an existing system
A real example
AnyComp
Verified-secretary directory, company registration flow, eSignature and a client dashboard.
A two-sided platform with customer and secretary roles, document signing inside the product, and a dashboard that tracks each registration. The case study walks through the six engineering decisions, including why the stack was chosen.
See the workWho this is not for
Saying this up front saves us both a call.
- You need a backend team to maintain a large existing system full-time — that's a hire, not a project.
- You want microservices and Kubernetes for a product with no users yet. We'll build the simplest architecture that survives your first year.
- You want us to pick Firebase or Postgres for ideological reasons. We pick for the product, and we'll build on your existing stack if it fits.
Questions founders ask
Postgres and Supabase, or Firebase — which do you recommend?
Postgres with Supabase for anything relational — marketplaces, dashboards, billing — because you get SQL, integrity and no lock-in. Firebase when the product is realtime-first, your team already knows it, or you're extending an existing Firebase app. We build on both.
Is the backend included in a SaaS MVP or mobile app price?
Yes. Every SaaS MVP (₹79,999 / $4,500) and mobile MVP (₹89,999 / $6,500) includes the backend: auth, database, APIs, storage and payments. Standalone backend work on an existing product is quoted after a scoping call.
How do you handle security?
Row-level security or security rules on the database, validation on every endpoint, rate limits on public routes, secrets kept out of the codebase, and security headers on the app. Anything that touches money or personal data gets tested before launch.
Who owns the infrastructure?
You do. Supabase, Firebase, Vercel and Stripe or Razorpay accounts are created in your name from day one, so nothing has to be migrated at handover.
Can you work with my existing backend?
Usually. Share the repository and the hosting details; within a day we'll tell you whether we can extend it, what needs fixing first, or whether a rebuild is the honest answer.
Start with a scope, not a commitment
Thirty minutes on a call, or a few lines in the form. Either way you get a written plan, a fixed quote and a realistic date.
Prefer to talk? Book a 30-min scoping call