★ Marketplace · stack
Best Tech Stack for a marketplace MVP
My opinionated stack for a marketplace MVP, layer by layer, with why I'd pick each tool and what would change my mind. Adjust the answers to fit your team.
- Runs in your browser
- No signup
Your stack
Tech stack for Marketplace
10 layers, picked for your answers. Boring where it should be, so your effort goes into the product.
- Frontend
Next.js (React + TypeScript)
Server rendering for SEO, file-based routing and the biggest React ecosystem. TypeScript end to end catches whole classes of bugs before users do.
- What would change my mind
- A purely internal tool with no SEO needs, where a plain Vite + React single-page app is simpler.
- Alternative
- Vite + React SPA, or Remix / React Router
- Backend / API
Separate TypeScript API service (Node.js + Fastify)
A dedicated service you can scale, monitor and audit on its own, sharing TypeScript types with the frontend.
- What would change my mind
- An early MVP with modest traffic, where Next.js route handlers inside the web app are enough.
- Alternative
- NestJS, or Go for a hot path
- Database
PostgreSQL (managed: Neon or AWS RDS)
Relational, transactional and boring. JSON columns cover the semi-structured bits, and pgvector covers embeddings if you add AI.
- What would change my mind
- Truly schemaless, write-heavy event data at very high volume. Add a specialised store for that slice only.
- Alternative
- MySQL, or MongoDB for document-shaped data
- Auth
Clerk
Prebuilt sign-in UI, organisations, roles and MFA. Hours instead of weeks for a B2B-ready login.
- What would change my mind
- Per-user pricing at consumer scale, or a hard requirement to keep auth in-house.
- Alternative
- Auth.js (NextAuth)
- Payments
Stripe (Razorpay if your customers are mostly in India)
Checkout, subscriptions, invoices and webhooks with the best docs in the business. Marketplaces use Stripe Connect for payouts.
- What would change my mind
- A market or payment method Stripe doesn't serve well, or merchant-of-record needs (tax handled for you), where Paddle or Lemon Squeezy fit.
- Alternative
- Paddle (merchant of record)
- Hosting
Vercel
Git push to deploy, preview URLs for every branch and no servers to manage, which is exactly what an MVP team needs.
- What would change my mind
- Long-running processes, heavy compute or strict data-residency requirements.
- Alternative
- Netlify, or Railway for a container
- Realtime
Pusher Channels or Ably
Managed WebSockets: add live updates and presence without operating connection servers.
- What would change my mind
- Very high message volume, where pricing pushes you to run your own.
- Alternative
- Socket.IO on your API service
- Background jobs
Inngest or Trigger.dev
Durable background functions with retries, schedules and a dashboard, written in the same TypeScript codebase.
- What would change my mind
- Very high throughput or strict data residency, which points to a queue in your own cloud.
- Alternative
- BullMQ + Redis
- Analytics
PostHog
Product analytics, funnels, session replay and feature flags in one tool, with a generous free tier.
- What would change my mind
- A marketing-only site, where a simple privacy-friendly counter like Plausible is enough.
- Alternative
- Plausible (simple), or Mixpanel
- Email
Resend
Reliable transactional email with a clean API and good deliverability defaults.
- What would change my mind
- Marketing campaigns and newsletters, which belong in a separate tool.
- Alternative
- Postmark
This is the stack I'd pick.
Want me to build on it? I ship MVPs on exactly this kind of stack.
What makes a marketplace different
A marketplace is two products on one database, plus money moving between them. Payouts, seller onboarding and trust (reviews, disputes) shape the architecture more than the listing pages do.
Risks to plan for
Payout complexity
Split payments, refunds after payout and seller KYC. Lean on Stripe Connect instead of moving money yourself.
Search quality
Buyers leave if they can't find supply. Postgres full-text search is fine early; plan for a search service when filters multiply.
Messaging scope
Real-time chat is expensive to build well. Start with email notifications and reply links if you can.
The stack at a glance
With the preset answers for a marketplace (you can change them above), this is the stack layer by layer.
| Layer | Pick | Alternative |
|---|---|---|
| Frontend | Next.js (React + TypeScript) | Vite + React SPA, or Remix / React Router |
| Backend / API | Separate TypeScript API service (Node.js + Fastify) | NestJS, or Go for a hot path |
| Database | PostgreSQL (managed: Neon or AWS RDS) | MySQL, or MongoDB for document-shaped data |
| Auth | Clerk | Auth.js (NextAuth) |
| Payments | Stripe (Razorpay if your customers are mostly in India) | Paddle (merchant of record) |
| Hosting | Vercel | Netlify, or Railway for a container |
| Realtime | Pusher Channels or Ably | Socket.IO on your API service |
| Background jobs | Inngest or Trigger.dev | BullMQ + Redis |
| Analytics | PostHog | Plausible (simple), or Mixpanel |
| Resend | Postmark |
Want the price tag too? Run the same product through the Marketplace cost estimate.
Questions founders actually ask
What payment setup does a marketplace need?
Do I need a separate search engine?
Web or mobile first for a marketplace?
Why does the picker recommend boring technology?
Is this stack good enough to scale?
Stack by product type
- Stack for a B2B SaaS
- Stack for an AI chatbot
- Stack for an AI agent
- Stack for a mobile app
- Stack for a fintech app
- Stack for an e-commerce store
- Stack for a booking app
- Stack for a CRM
- Stack for a learning platform
- Stack for a social / community app
- Stack for an internal tool
Or start from a blank slate with the full tech stack picker.
More from the workbench
Fine print
Tools: on the house.
Engineer: by the hour.
The opinion was free. The implementation is where I come in.
I'm Himanshu, an AI and full-stack engineer. I build MVPs, AI agents and the growth plumbing around them for early-stage startups.