kitcommerce.store

An Astro static site. Edit src/ and public/; the legacy HTML at the repository root is not the shipped source.

npm ci
npm run dev        # http://127.0.0.1:4321
npm run build
npm run verify
npm run preview    # inspect dist/ locally

What this site is

KitCommerce is an open-source ecommerce platform whose packages are GoCommerce and Svelte Commerce — GoCommerce for the backend and admin, Svelte Commerce for the storefront — presented the way Medusa presents itself: one platform, several packages. kitcommerce.store is its website. Each package is MIT licensed and also works on its own.

	GoCommerce	Svelte Commerce
Role	Backend + admin	Storefront
Language	Go	SvelteKit
Standalone	Yes	Yes
Repository	itswadesh/gocommerce	itswadesh/svelte-commerce
Accent	Go blue #00add8	Svelte orange #ff3e00

The site takes no hue of its own and the wordmark is monochrome, because a website that wore one of the packages' colours would be claiming to be that package.

The branding rule

Since 25 September 2026 KitCommerce is presented as one product — the open-source ecommerce platform — whose two packages are GoCommerce and Svelte Commerce, the way Medusa is one platform made of packages (the owner's decision, so directories can list it under one name). What stays true, and what the verifier still holds the prose to:

• There is no KitCommerce edition, tier, cloud or enterprise version. Both packages are MIT and free to run yourself, at 0% of sales. Stores hosted on kitcommerce.store pay 1% of every successful order (since 26 October 2026); that figure and the sign-up URL live once, in src/data/pricing.json, and pages render them from there. Every price on the site is in US dollars, with no conversion: a rival that publishes only rupee prices is compared without them. See docs/decisions.md.
• Name the package that does the work when a claim is about one of them: "GoCommerce's checkout", "Svelte Commerce's 26 backends".
• Don't overstate how joined they are. The connector between them is early (0.1.0), and each package runs without the other.

Spell them GoCommerce and Svelte Commerce — never Go Commerce, SvelteCommerce or, in prose, Svelte-Commerce. The repository slug is svelte-commerce; the project is two words.

The verifier enforces this mechanically.

Page structure

Six pages, each with one job. The homepage directs; the project pages explain.

URL	Its one job
/	choose a project, and prove the software is real
/gocommerce/	understand GoCommerce
/svelte-commerce/	understand Svelte Commerce
/svelte-commerce/backends/	understand backend compatibility
/go-svelte-ecommerce/	understand how the two fit together
/gocommerce-svelte-commerce-connector/	understand integration status

The homepage leads with real product captures and a Docker command. It retains the project chooser, admin gallery, storefront proof and developer evidence. Marketplace/B2B detail is linked from compact solution cards, and the duplicate architecture section and logo marquee are consolidated. Both original architecture anchors still work.

Nav is five items: GoCommerce, Svelte Commerce, Live admin, Architecture, GitHub. Secondary navigation lives inside the project pages, not in the header.

The Docker quick start

docker-compose.yml and env.example sit at the repository root and are served from the domain, so the command on the homepage is a real download:

curl -O https://kitcommerce.store/docker-compose.yml
curl -o .env https://kitcommerce.store/env.example
docker compose up -d

Three services: postgres, gocommerce (API and admin — the admin is compiled into the binary, so a separate admin service would be theatre) and web (Caddy on port 80). This was run end to end before it was published — all three containers healthy, / serving the admin, /docs the OpenAPI page, /api/products returning JSON.

It deliberately does not start Svelte Commerce by default. The GoCommerce connector (@misiki/gocommerce-connector) is early, at 0.1.0, and is installed into a Svelte Commerce checkout rather than shipped in a storefront image, so a default storefront container would serve a page and fail to load a product from this stack. Do not add one to look complete.

GoCommerce builds from source because no image is published; pin a tag in build.context once releases exist. The env template is env.example, not .env.example, because the static host may not serve dotfiles and a download instruction that 404s is worse than none.

Image distribution

The homepage uses focused derivatives; project pages retain the complete originals.

Page	Images
/	hero composite (admin + Arialshop mobile), four admin tabs, one live-store card
/gocommerce/	the seven admin screens
/svelte-commerce/	Arialshop mobile, desktop and product
the other three	none — diagrams only

Where the numbers come from

GoCommerce figures are read from a commit, not typed: node scripts/read-facts.mjs reads GoCommerce origin/main through git and writes src/data/facts.json, whose how block says what each figure counts (modules are ext/ directories less alltest; admin screens are +page.svelte files under admin/src/routes/dash; tests are Test/Example functions less TestMain; operations are path and method pairs in every openapi.json). Pages render them through src/lib/facts.ts, data files write {modules}-style tokens, and npm run verify fails when a page states another figure, or when a local ../gocommerce checkout has moved past the file.

This is the beginning of the README. Read the rest at the original. Read the full README ↗