Litestore is one Next.js app on Postgres and Prisma, and you change it by editing your own copy.
Litestore publishes 56 typed events through Inngest. You can add your own reaction in code or let an outside system subscribe through a signed webhook.
Postgres rejects writes that would leave payments or stock in an inconsistent state. For example, a bug in your fork can't refund more than the customer paid for an order.
Postgres stops refunds and ledger rows from going above what an order was paid.
Postgres rejects a stock movement that doesn't add up.
Indexes keep emails, SKUs and slugs unique.
Two scripts verify the migration SQL and the live database.
Each one links to the guide that explains how it works.
The Prisma schema shows how products, stock, orders and refunds connect.
Read the guideOutside services call oRPC or REST, and the admin uses server actions.
Read the guideA shopper's assistant can search the catalog and build a real cart.
Read the guideOutside systems can subscribe to any of the events the store publishes.
Read the guideYou extend Litestore by changing your own copy of the code. That works well for a team that reads code, but some common platform features aren't there.
Our guide takes you from a fresh clone to a running store with sample data.