OSS Tanbou
View on GitHubProject website

separate a GraphQL-only commerce core from storefronts and independently deployed extensions

OSS scale score 307.1OSS health 100Update pace 24 commits/30d
About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
23,398
Primary language
Python
License
BSD-3-Clause
Repository last updated
Oct 2, 2026
On this page

Overview

Saleor exposes catalog, checkout, orders, customers, promotions, and payments through a GraphQL-only headless commerce core. The dashboard and storefront are separate projects, while apps, webhooks, metadata, and API extensions keep custom logic outside the core process.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Use GraphQL as the single commerce API surface

Backend interaction, configuration, and extension are API-first, allowing storefronts and external systems to integrate through one GraphQL contract.

Sources: [2]

Model pricing, currency, stock, and products per channel

Native multichannel controls support regional, multi-brand, and other commerce configurations where catalog and inventory rules differ by channel.

Sources: [2]

Deploy apps and webhook-driven extensions independently from the core

Custom logic can live in apps, webhooks, and API extensions instead of monolithic plugins, supporting independent scaling and deployment.

Sources: [2]

Best fit

Fits complex headless commerce with multichannel and continuous extension

It is relevant when front-end technology should remain decoupled from commerce logic and multiple teams or channels need to evolve independently.

Sources: [2]

Before adoption

The service-oriented model can be excessive for small sites

Saleor's README explicitly notes that a small, low-traffic business without strong availability requirements may find this architecture more complex than a traditional monolith.

Sources: [2]

Use a stable 3.x release instead of the main development branch

The main branch is documented as potentially unstable. Production deployments should use release tags and align compatible versions of Core, Dashboard, and Storefront.

Sources: [2][4]

saleor-platform is for local development only

The all-in-one Saleor Platform Compose repository explicitly says it is not intended for production deployment.

Sources: [3]

Official sources

  1. [1]saleor/saleor repository(2026-10-01)
  2. [2]Saleor README(2026-10-01)
  3. [3]Saleor Platform README(2026-10-01)
  4. [4]Saleor 3.23.37 release(2026-10-01)
  5. [5]Saleor BSD-3-Clause license(2026-10-01)
Supplemental curator note

Saleor separates the dashboard and storefront from a GraphQL-only commerce core. This service-oriented model is more complex than a small monolith but supports independent deployment, technology-agnostic extensions, and multichannel commerce.

Try it in 3 steps

  1. 1

    Clone Saleor Platform

    Fetch the official local-development stack containing the Core API, Dashboard, databases, cache, and supporting services. It is not a production deployment template.

    git clone https://github.com/saleor/saleor-platform.git && cd saleor-platform
  2. 2

    Apply migrations and seed example data

    Apply the database schema and create example data plus the documented development superuser.

    docker compose run --rm api python3 manage.py migrate && docker compose run --rm api python3 manage.py populatedb --createsuperuser
  3. 3

    Start the Saleor stack

    Start the services. The Core API is available at http://localhost:8000 and the Dashboard at http://localhost:9000.

    docker compose up
Check the official README

Growth

Growth trends · Last 30 days

23,398 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
24
Open PRs
90

Development activity is still being collected.

Built with

Categories and tags

Categories

Tags

GitHub data

GitHub dataView detailed GitHub data
View on GitHub

GitHub Topics

  • python
  • store
  • commerce
  • shop
  • ecommerce
  • cart
  • graphql
  • headless
  • headless-commerce
  • multichannel
  • shopping-cart
  • composable
Stars
23,398
Forks
6,139
Watchers
362
Open issues
198
Contributors
260
Owner type
Organization
Primary language
Python
Repository last updated
Oct 2, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?