/ tech-stacks / Best Tech Stack for Building an E-commerce Store as a Solo Developer
tech-stacks 9 min read

Best Tech Stack for Building an E-commerce Store as a Solo Developer

The ideal tech stack for solo developers building an e-commerce store in 2026. Frontend, backend, database, hosting, and more.

Hero image for Best Tech Stack for Building an E-commerce Store as a Solo Developer

Let me save you three months of research. If you're a solo developer building an e-commerce store, you do not need to build everything from scratch. I learned this the hard way by spending eight weeks building a custom checkout flow when Shopify does it better in five minutes.

But there are good reasons to build your own. More control, no monthly platform fees eating your margins, and the ability to customize everything. Here's the stack that gives you both speed and control.

Layer Tool Why
Frontend Next.js Fast pages, SEO-friendly, image optimization built in
Backend Medusa.js or Saleor Open-source e-commerce engines that handle the hard parts
Database PostgreSQL Handles product catalogs, orders, and inventory reliably
Auth Built into Medusa/Saleor Customer accounts handled by the commerce engine
Hosting Vercel (frontend) + Railway (backend) Managed, affordable, scales when needed
Payments Stripe Best developer experience, supports subscriptions and one-time payments

The Numbers Behind This Stack (2026)

Here is what each piece actually costs and how mature it is, with every figure pulled from the source on 2026-05-30.

Tool License / cost Latest version Adoption signal
Next.js Open source, free 16.2.6 139,595 GitHub stars, about 40.1M npm downloads per week
Medusa.js Open source (MIT), free to self-host 2.15.5 34,049 GitHub stars, about 109,000 npm downloads per week
Saleor (core) Open source (BSD-3), free to self-host Saleor Cloud Select around $159/month (check current pricing) 22,936 GitHub stars
PostgreSQL Open source, free 18.4 (released 2026-05-14) The default relational database for serious commerce
Vercel Hobby free, Pro $20/user/month Managed platform $20 monthly usage credit on Pro
Railway $5 one-time trial credit, Hobby $5/month, Pro $20/seat Managed platform Resource-metered billing on top of the base
Render Free web tier, Starter $7/month, Postgres from $6/month Managed platform Free web services spin down after 15 minutes idle
Stripe No monthly fee, 2.9% + 30 cents per US online card charge Pay as you go No setup, monthly, or hidden fees

The big takeaway is that the open-source core of this stack costs nothing to license. Your only real spend is hosting (single digit to low double digit dollars per month early on) and Stripe's per-transaction cut, which you only pay once money is actually moving.

Why This Stack Works for Solo Developers

E-commerce has a ton of solved problems. Cart logic, inventory management, order processing, tax calculation. Building these from scratch is a trap. I've seen solo developers spend months recreating what Shopify gives you for $39/month.

The trick is using an open-source commerce engine (Medusa.js or Saleor) that handles the boring infrastructure while giving you full control over the frontend experience. You get the customization of a custom build with the reliability of battle-tested software.

This approach also means you own your data and your code. No platform lock-in. No surprise fee increases. No begging support to add a feature.

Frontend: Next.js

For e-commerce, page speed directly impacts conversion rates. Every 100ms of load time costs you roughly 1% in sales. Next.js gives you server-side rendering, automatic image optimization, and static generation for product pages. That means fast pages without any extra work.

The framework is also a safe bet for the long haul. As of 2026-05-30 the project sits at 139,595 GitHub stars and pulls roughly 40.1 million npm downloads per week, with the latest release being version 16.2.6. That is not a framework that is going away. The commerce ecosystem around Next.js is mature too. There are starter templates for Medusa, Saleor, and Shopify's Storefront API. You're not starting from zero.

Alternative. If you want something even faster to build, use Shopify with a custom Hydrogen storefront. You lose some control but gain a lot of speed. Shopify's Basic plan is $29/month and its Grow plan is $79/month (billed yearly), with online card rates of 2.9% + 30 cents on Basic dropping to 2.7% + 30 cents on Grow. Honestly, if your primary goal is selling products and not building software, Shopify might be the better call. No shame in that.

Backend: Medusa.js

Medusa.js is my pick for solo developers. It's Node.js-based (so you stay in JavaScript/TypeScript land), it's open source under the MIT license, and it handles products, orders, customers, discounts, shipping, and payments out of the box. It is genuinely free to self-host, and the project is healthy: 34,049 GitHub stars and around 109,000 npm downloads per week as of 2026-05-30, with the current release at version 2.15.5.

I like Medusa over Saleor because it keeps you in JavaScript and the learning curve is gentler. Saleor is excellent, but its core is a Python and Django GraphQL API, so self-hosting means running Python, PostgreSQL, and Redis together. Saleor's source is free (it carries 22,936 GitHub stars), though if you want their managed Saleor Cloud the entry tier runs around $159/month with usage-based fees on top (check current pricing). For a solo developer who wants one language and a gentle on-ramp, Medusa wins. You can add features without touching core code.

Why not just Stripe alone? Stripe handles payments, but it doesn't manage inventory, product variants, shipping calculations, or order fulfillment. You could build all that yourself, but you'd basically be rebuilding Medusa with worse code and more bugs.

Database + Auth + Hosting

Database. PostgreSQL is the standard for e-commerce. It handles complex product queries, inventory counts, and order relationships without breaking a sweat. Medusa uses Postgres by default, so there's nothing to configure. It's free and open source, and the current major version is 18 (18.4 shipped on 2026-05-14), so you are building on something modern and actively maintained.

Auth. Medusa handles customer authentication. Customers can create accounts, save addresses, track orders. You don't need to wire up a separate auth provider for this.

Hosting. Put the Next.js frontend on Vercel for fast global CDN delivery. Vercel's Hobby plan is free forever and is plenty for launch (1M edge requests and 100GB transfer per month), and the Pro plan is $20 per user per month with a $20 monthly usage credit baked in. Run the Medusa backend on Railway or Render. Railway gives you a one-time $5 trial credit, then a $5/month Hobby plan that suits solo side projects, with resource usage metered on top. Render has a real free web tier, though free web services spin down after 15 minutes of inactivity and the free Postgres database expires after 30 days, so for anything live you want Render's $7/month Starter web service plus a managed Postgres instance from $6/month. Total cost for a new store is realistically $0 to $25/month until you have real traffic.

What I'd Skip

Building your own cart. Cart logic is deceptively complex. Discount stacking, tax calculations, shipping rules, inventory reservation. Use what Medusa gives you.

WooCommerce. It's 2026. PHP-based WordPress commerce with a mountain of plugins is not the developer experience you want. If you're going the WordPress route, just use Shopify instead.

Headless CMS for products. Your commerce engine IS your product CMS. Don't add Contentful or Sanity just for product descriptions. That's an extra service, extra cost, and extra complexity for zero benefit.

Custom payment processing. Stripe handles PCI compliance, fraud detection, and international payments. It charges 2.9% + 30 cents per successful US online card charge with no setup, monthly, or hidden fees, so you pay nothing until you make a sale. Do not try to process credit cards yourself. Ever.

Getting Started

  1. Set up Medusa. Run npx create-medusa-app@latest and follow the prompts. As of 2026-05-30 that pulls create-medusa-app version 2.15.5, which scaffolds the matching Medusa 2.15.5 backend. You'll have a working backend with admin dashboard in about 10 minutes.

  2. Add the Next.js storefront. Medusa provides a Next.js starter. Clone it, connect it to your Medusa backend, and customize the design.

  3. Configure Stripe. Add your Stripe keys to Medusa. Test the full checkout flow with Stripe's test cards.

  4. Add 5-10 products. Don't launch with an empty store. Add real products with good images, descriptions, and pricing.

  5. Deploy and start selling. Push the frontend to Vercel, the backend to Railway, and start driving traffic. You can always add features later, but you can't make sales without a live store.

The best e-commerce stack for a solo developer is one that handles the commodity features so you can focus on what makes your store unique. Products, branding, and customer experience are where you win. Not custom cart implementations.

Sources

All figures checked on 2026-05-30.

Built by Kevin

Like this? You'll like what I'm building too.

Two ways to support and get more of this work.

Desktop App

HEARTH

A privacy-first Life OS for your desktop. Journal, tasks, and notes that stay on your machine. Coming soon, direct download from this site.

Read more
Digital Products

MY TOOLKITS

Receipts-first toolkits for shipping after hours, building Claude agents, publishing on Amazon, and more. The exact methods I used, not theory.

Browse on Whop

Need This Built?

Kevin builds products solo, from first version to live. If you want something like this made, work with him.