Marketplace stack picks under $200/mo

Marketplaces have a reputation for being expensive to build. Most of that reputation comes from teams that bought enterprise pieces before they had a single transaction. You can launch a real two-sided marketplace for under $200 a month — the trick is knowing which five pieces matter and which costs actually climb.

The stack at a glance

The framework, hosting and data layer are close to free until you have volume. The two lines that grow are payments and image bandwidth — and both grow with revenue, which is the healthy kind of cost.

Why this stack

Listings live in a managed data layer

A marketplace is mostly CRUD with good search: sellers create listings, buyers browse them. A managed data layer gives you the records, the relationships (seller → listings → orders), and file uploads for photos without provisioning anything.

Stripe Connect, not plain Stripe

This is the one non-negotiable. A marketplace collects from a buyer and pays out to a seller, minus your fee. That's exactly what Stripe Connect does: seller onboarding, identity verification, and split payments. Trying to do this with ordinary Checkout means reimplementing payouts and KYC yourself — a compliance minefield you do not want.

The fastest way to sink a marketplace is to get clever with money flow. Let Connect own onboarding, payouts and the platform fee. Your job is to record who sold what to whom.

Search that's good enough

For launch, filtered queries with a few indexes beat any dedicated search service. Category, price range, location, sort by recency — that covers the first thousands of listings. Add real search infrastructure when you can measure that relevance or latency is costing you conversions.

Images without the bill shock

Listing photos are where bandwidth costs sneak up. Always serve resized, format-optimized images via signed URLs — never the original 4MB upload. This single habit keeps your bandwidth line flat while listings grow.

Wiring it together

 Buyer ──▶ Next.js (browse/SSR) ──▶ data layer (listings)
   |                                      ^
   |                                      | seller CRUD
   v                                   Seller
 Stripe Connect
   |  charge buyer, split fee, pay seller
   v
 record order + payout in data layer

Stack risks

• Payments compliance. The moment you move money between two strangers, you inherit obligations. Connect covers most of it, but read its requirements for your region rather than assuming.
• Trust and safety, not tech. Marketplaces fail on bad actors before they fail on infrastructure. Budget time for reporting, moderation and dispute flows — they're product, not plumbing.
• Image bandwidth creep. Unoptimized photos will quietly become your biggest bill. Resize at upload and serve optimized.
• Cold-start liquidity. No stack solves an empty marketplace. Seed one side manually before you automate anything.

Cost reality

At launch you're paying for hosting (near zero), a data-layer entry plan, and Stripe's per-transaction percentage. Stay under $200 by deferring dedicated search and keeping images optimized. When you cross $200, it should be because GMV — not your architecture — grew.

Your move:

Wire Stripe Connect onboarding and a single end-to-end test transaction before you build a single listing-browsing screen — the money flow is the marketplace.