Your Next Store (YNS) is a free, open source e-commerce platforms project written in MDX and released under MIT. It has 5,503 GitHub stars, 671 forks and 3 open issues, and was last pushed 14 hours ago. On this registry it ranks #11 of 30 tracked projects in E-commerce Platforms, with 5 head-to-head comparisons available. It gained 13 stars over the last 6 tracked days.

What is Your Next Store (YNS)?

What it is

Your Next Store is an open-source, AI-native commerce template built on Next.js 16 and powered by Stripe. It is published under the MIT license at the yournextstore/yournextstore repository, carries roughly 5,498 stars and 668 forks, and lives squarely in the Next.js and React ecosystem, with MDX documentation and a topic set spanning Next.js, React, TypeScript, Bun, Stripe, Tailwind CSS, and commerce. A hosted demo is available at demo.yournextstore.com, and the tagline frames it as a way to launch a store in minutes without writing code by hand.

The concrete problem it addresses is that an AI coding tool asked to build a storefront has to invent the entire commerce domain before it can write anything useful. Your Next Store ships that domain already defined: products, variants, carts, and checkout exist as typed data models, and the Commerce Kit SDK exposes methods such as productBrowse() and cartUpsert() with fixed input and output shapes. An AGENTS.md file supplies project context, SDK examples, Biome rules, and a validation checklist so that Claude Code, Cursor, and Codex start from known contracts instead of guessing at them.

Key capabilities

  • AI-friendly codebase with an AGENTS.md file that documents idiomatic patterns, SDK examples, and a validation checklist for AI coding agents.
  • Commerce Kit SDK with typed headless commerce methods, including productBrowse() and cartUpsert(), each with defined input and output shapes.
  • Direct Stripe API integration covering checkout, billing, and subscriptions without an intermediary layer.
  • Next.js 16 App Router with React Server Components and the React Compiler, using patterns such as Server Actions and "use cache".
  • Bun as the JavaScript runtime and package manager, with Biome handling linting and formatting.
  • Tailwind CSS v4 and Shadcn UI, providing more than 50 accessible components built on Radix UI.
  • 149 ready-made themes on branches named theme-001 through theme-149, each with a redesigned homepage, hero, colour palette, and section layout on the same core codebase.

Who uses it and how

  • Developers launching a new storefront who clone the repository, set YNS_API_KEY in .env.local, and run bun dev to get a store on localhost:3000.
  • Teams using AI coding tools such as Claude Code, Cursor, or Codex to extend a store, relying on AGENTS.md and the typed SDK contracts to keep generated code correct.
  • Operators publishing from the command line, using bun run publish:store to trigger a production publish and wait for the
project readme (upstream, from github) — read inline

Your Next Store

Open-source AI-native Next.js e-commerce template.

Powered by Stripe. Built for AI coding tools.

Live Demo: demo.yournextstore.com

GitHub Stars Deploy with Vercel Discord Product Hunt


AI-Friendly Codebase Ships with AGENTS.md — idiomatic patterns, Commerce Kit SDK with typed methods. Claude Code, Cursor, and Codex work out of the box
Stripe-Native Direct Stripe API integration — checkout, billing, subscriptions
Next.js 16 App Router, React Server Components, React Compiler
Open Source Self-host anywhere, deploy to Vercel in one click

Quick Start

git clone https://github.com/yournextstore/yournextstore.git
cd yournextstore && bun install
cp .env.example .env.local   # Add your YNS_API_KEY from https://yns.store/manage/settings/api
bun dev

Open localhost:3000 — your store is running.

Why AI Tools Work Better Here

Familiar patterns Idiomatic Next.js App Router (Server Components, Server Actions, "use cache") — matches what LLMs have seen thousands of times
Commerce Kit SDK Methods like productBrowse() and cartUpsert() have defined input/output shapes. LLMs write correct code when they know the contracts
Well-defined domain Products, variants, carts, checkout — the data models already exist with clear types. No need for the LLM to invent them
AGENTS.md Full project context, SDK examples, Biome rules, and validation checklist — AI agents understand the codebase before writing a single line

Tech Stack

  • Next.js 16 — App Router, React Server Components, React Compiler
  • Bun — Fast JavaScript runtime and package manager
  • Commerce Kit SDK — Headless commerce API integration
  • Tailwind CSS v4 — Utility-first styling
  • Shadcn UI — 50+ accessible components built on Radix UI
  • TypeScript — Strict type-safe development
  • Biome — Lightning-fast linter and formatter

Performance and accessibility defaults — prerendered chrome on every route, optimizer-served icons, WCAG-AA colour tokens, tappable controls — are spelled out in AGENTS.md and checked by bun run build and bun test.

Prerequisites

Environment Variables

Copy .env.example to .env.local and set:

  • YNS_API_KEY — Your API token from the admin panel

Publishing & Store API from the CLI

Two small scripts in scripts/ talk to the YNS platform using only the store's YNS_API_KEY (read from .env.local / .env):

bun run publish:store            # Trigger a production publish (same as the admin "Publish" button) and wait for the build
bun run publish:store --no-wait  # Fire and forget

bun run api GET  /products?limit=5                      # Call any Store API endpoint
bun run api POST /products '{"name":"Tee","price":29.99}'

scripts/publish.sh deploys the tenant repo's remote main — push your commits first. scripts/api.sh is a thin wrapper around curl that handles auth, base-URL resolution, and pretty JSON output for every /api/v1/* endpoint (see the API documentation).

Syncing a store with the template

Stores are seeded from a snapshot of this repo and share no commits with it, so a plain merge has no base. See docs/sync.md for the graft-and-merge procedure and why merge beats rebase here.

Contributing

See CONTRIBUTING.md for coding conventions and PR checklist.

Next Steps

Refer to the API documentation for details on fetching products, managing carts, and building on top of YNS.

Themes

Your Next Store ships with 149 ready-made themes across different store categories. Each theme includes a fully redesigned homepage, hero, color palette, and section layout — all built on the same core codebase.

Themes live on branches named theme-001theme-149. Switch themes with a single command:

git checkout theme-016

Browsing themes

Each theme branch is a single commit on top of main whose message describes the theme's vibe. List them all (id + description) with:

git for-each-ref --sort=refname --format='%(refname:short)  %(subject)' 'refs/remotes/origin/theme-*'

All theme branches use a zero-padded three-digit id (theme-001theme-149). Themes modify only visual components and static assets — your products, cart, and checkout remain unchanged.

Star History

Star History Chart

Frequently asked questions

Is Your Next Store (YNS) free to use?

Your Next Store (YNS) is open source under the MIT licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does Your Next Store (YNS) do?

Launch Your Store in Minutes, No Code Needed

What is Your Next Store (YNS) written in?

Your Next Store (YNS) is primarily written in MDX. Its source is publicly available at https://github.com/yournextstore/yournextstore, and it has 5,503 GitHub stars.