Backend first
The commerce primitives — catalog, inventory, media, content, orders, audit — are the product. Storefronts are a presentation layer, not the platform.
About litecommerce
A commerce backend that refuses to be a template.
Most platforms force a hosted storefront on you and call the API an afterthought. litecommerce inverts that — the API and the admin are the platform, and your storefront is whatever you want it to be.
The thesis
Commerce is a backend problem.
Catalog, inventory, media, audit, multi-tenant safety, and durable data live on the server. Branding, layout, and interaction live in the browser. litecommerce keeps those two responsibilities clean.
The result: merchants pick any frontend — Next.js, Astro, plain HTML, or a native app — and consume one stable REST API from all of them.
BYO frontend, always
Tenants build storefronts on the stack they want. litecommerce exposes the same REST API to every frontend, hosted or not.
Multi-tenant from day one
Every row is tenant-scoped. Every API guard enforces it. No service-role credentials ever reach the browser.
Honest about what ships
If a capability is live, we ship it. If it isn't, we badge it. We'd rather under-promise than send prospects to a page full of fiction.
Audit by default
Admin writes, auth events, API-key rotations, and platform support access are recorded and queryable.
What litecommerce hosts
The boring-but-critical parts.
litecommerce runs the backend API, the merchant admin where tenants manage their catalog and operations, the platform admin for our internal staff, and the marketing surface you're reading right now. A hosted checkout surface — litecheckout — is in active development.
What we don't host: your tenant storefront. That stays with you. The two reference storefronts on this site are examples of what tenant-owned frontends can look like, not a template every tenant has to use.
REST APItenant-scoped, OpenAPI-ready
Merchant adminSupabase Auth, permissions, org switching
Platform admininternal litecommerce ops
Marketing + docsyou are here
See it in motion
Two real storefronts on one backend.
Both reference storefronts consume the same litecommerce API. The backend has no idea which frontend made the request — and that's exactly the point.