A newly built Next.js App Router store foundation for developers and businesses creating a digital-product shop. The original MIT-licensed Vercel Commerce storefront has been adapted with a MySQL and Drizzle product provider, server-side carts, Stripe Checkout and signed webhooks, order storage, editable shadcn-style components, protected administration pages, demonstration products, seed data, environment examples, and detailed setup guidance.
A self-hostable digital-commerce starter adapted from Vercel's Next.js Commerce with Stripe, MySQL, Drizzle, editable shadcn-style UI and a protected admin area.
Next.jsReactStripeMySQLDrizzleshadcn/ui
Included in the release
Vercel Next.js Commerce storefront adapted for a custom MySQL provider
MySQL schema, Drizzle ORM migration, seed catalogue, products, variants, collections, carts, orders and content pages
Stripe Checkout with server-verified prices, promotion codes, signed webhooks and pending/paid order records
Protected admin login, dashboard overview, product view and order view
Local demonstration catalogue and SVG artwork so the design works before infrastructure is connected
Environment template, password-hash generator, project map and production checklist
Guidance for MySQL, Stripe testing, Node.js, pnpm and self-hosted deployment
Third-party licence notices retained for compliant commercial modification and redistribution
Best outcomes
Start from a working storefront instead of an empty Next.js project
Replace the demonstration catalogue with your own products and branding
Use editable component source with ChatGPT Codex or another developer
Deploy to Vercel or self-host behind Nginx on an Ubuntu VPS
Extend the starter with fulfilment, customer accounts, email receipts or a larger admin system
Open-source foundation and commercial reuse
Why this source code can be supplied as a commercial CodeKits template
The right to modify and redistribute this starter comes from its software licences—not simply because the tools are available at no charge. Vercel Next.js Commerce and shadcn/ui use the permissive MIT licence, which allows use, copying, modification, distribution, sublicensing and sale when the required copyright and licence notices are preserved.
Vercel Commerce foundation
The storefront began with Vercel's MIT-licensed Next.js Commerce project. Its App Router structure, React Server Components, search, collection, product and cart patterns provide a proven starting point. The active Shopify provider has been replaced with the CodeKits MySQL and Drizzle implementation.
Editable shadcn-style components
shadcn/ui follows a source-code ownership model: component code is placed inside the project instead of hidden inside a hosted design service. This starter includes editable Button, Card, Input, Label, Badge and Table primitives that can be restyled, extended or composed into new store and dashboard screens.
CodeKits additions
The product price covers the adapted MySQL commerce provider, Drizzle schema and migration, Stripe checkout and webhook flow, protected administration area, demonstration catalogue, configuration templates, documentation, testing work and continued support—not exclusive ownership of the underlying open-source projects.
Notices included with the source
The original Vercel MIT notice remains in the suppliedlicense.md file.
A third-party notice lists the principal frameworks, libraries and their licences.
Buyers may customise and deploy the code while continuing to preserve applicable open-source notices.
Vercel hosting is optional, while Stripe accounts, processing fees and service terms remain separate.
Vercel, Next.js, shadcn/ui, Stripe and other names belong to their respective owners. CodeKits.shop is not claiming sponsorship or endorsement by those projects. Buyers remain responsible for reviewing the notices and licences included with the version they receive.
Continued support included
You are supported after purchase or delivery.
Support continues after handover, with practical help related to your purchased productrather than leaving you with code and no direction.
Questions answered
Get clear follow-up answers about the supplied code, setup documentation, configuration, and technical handover.
Tailored command sheets
Request practical command sheets for installation, deployment, server configuration, updates, and common troubleshooting.
Included support covers reasonable questions and guidance connected to the purchased product or agreed project scope. New features, substantial redevelopment, managed hosting, and third-party charges are quoted separately.
Honest performance guidance
Choose visual effects that suit your customers' devices.
Next.js itself can be fast, but animation-heavy Magic UI components, large templates, WebGL effects, blur layers, and excessive client-side JavaScript may feel slow or less smooth on older phones and computers. I will explain this trade-off before recommending a design.
Faster alternatives when animation is not essential
Lean React interfaces with purpose-built components and fewer dependencies
Restrained business interfaces with predictable controls instead of constant motion
Standard HTML and CSS sites for simple content, speed, and broad compatibility
Reduced-motion versions of animated layouts for older or lower-powered devices
Performance testing before launch so design choices match the target audience
A lighter custom React build or standard HTML/CSS website is often a better option when maximum smoothness, accessibility, and support for older hardware are more important than complex animation.
A directly engineered React interface backed by a custom Node.js API and MySQL database may look more restrained than an animation-led template, but that can feel more professional for dashboards, portals, stores, and operational applications. Fewer decorative effects and third-party visual layers can mean more predictable controls, clearer feedback, easier maintenance, and fewer distracting hover, scrolling, stacking, or low-powered-device glitches. Performance still depends on careful architecture, implementation, and testing rather than the technology names alone.
Next.js store deployment
Build a Stripe and MySQL store on Ubuntu.
The release package will include a command workflow for Node.js, the MySQL schema, the Next.js production build, PM2 and an Nginx reverse proxy.
Install production dependencies from the lockfile
Import the supplied MySQL store schema
Build and supervise Next.js with PM2
Check Nginx before applying the new configuration
Final command sheets are tailored to the project and hosting setup.
✓ Ubuntu packages updated
✓ Store database prepared
✓ Next.js production build completed
✓ Application saved in PM2
✓ Nginx proxy checked and reloaded
Included download files
The source is built. A customer-safe ZIP and its file preview will be published after final release checks; secrets, dependencies, build caches and local environment files will not be included.
No packaged files are available to display yet.
Release preparation
The template has been created, but checkout remains disabled until the distributable ZIP, licence notices and download fulfilment have completed final testing.