saleor
Saleor is an open-source, GraphQL-native e-commerce API platform written in Python. It provides a headless, API-first architecture for building composable commerce systems with multi-channel, multi-currency, and multi-warehouse support.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | saleor/saleor |
| Owner | saleor |
| Primary language | Python |
| License | BSD-3-Clause — OSI-approved |
| Stars | 23.1k |
| Forks | 6.1k |
| Open issues | 229 |
| Latest release | 3.23.17 (2026-07-07) |
| Last updated | 2026-07-07 |
| Source | https://github.com/saleor/saleor |
What saleor is
A GraphQL-only backend for e-commerce built on Python, offering webhook-based extensibility, dashboard customization via iframes, and service-oriented architecture. Core features include order management, payment orchestration, cart, promotions, and product catalog management without monolithic plugin dependencies.
Get the saleor source
Clone the repository and explore it locally.
git clone https://github.com/saleor/saleor.gitcd saleor# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Python backend; requires Docker-based deployment or local Python environment setup. Node.js/npm for CLI tooling and storefront scaffolding.
- GraphQL-only API necessitates client libraries capable of GraphQL subscriptions and mutations; REST endpoints not available.
- Webhook-based extensibility demands external service infrastructure for payment gateways, inventory, CMS integrations, and custom business logic.
- Multi-channel architecture implies schema design discipline; pricing, tax, and stock rules are per-channel, not global defaults.
- Active development cycle (latest release July 2026); production environments should track stable 3.x releases, not main branch.
When to avoid it — and what to weigh
- Solo developer or micro-business with light traffic — Service-oriented architecture adds operational complexity versus simpler alternatives like WordPress or Magento for single-developer small shops.
- Need for monolithic plugin ecosystem and tight language coupling — Saleor enforces API-only extension patterns; traditional server-side template rendering and language-specific frameworks are not supported.
- Minimal operational infrastructure or DevOps capacity — Requires deployment orchestration, independent service scaling, and webhook management. Not suitable for teams with no DevOps support.
- Requirement for proprietary, closed-source customizations — BSD 3-Clause license requires source disclosure of modifications; not suitable for organizations requiring strict IP protection of extensions.
License & commercial use
BSD 3-Clause License. Permissive OSI-approved license allowing commercial use, modification, and distribution. Requires retention of copyright and license notice in source and binary distributions.
BSD 3-Clause is a permissive open-source license explicitly allowing commercial use without royalty or attribution requirements in deployed services. However, if modifications are distributed, source disclosure is required. Verify your use case (internal deployment vs. redistribution) aligns with BSD 3-Clause terms. Saleor Cloud offers managed SaaS; verify commercial support options separately on saleor.io.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | High |
| DEV.co fit | Good |
| Assessment confidence | High |
BSD 3-Clause license and active maintenance suggest security-conscious development, but no independent security audit data provided. Webhook-based extensibility and iframe dashboard apps require secure integration patterns on operator side. GraphQL API is single entry point; ensure proper authentication, authorization, and rate-limiting. Recommend review of payment PCI compliance for payment integration patterns. Standard OWASP considerations apply; operator responsible for infrastructure hardening.
Alternatives to consider
Shopify Plus / Shopify Custom Apps
Fully managed SaaS with built-in payment, shipping, tax; lower operational overhead but less control and locked to Shopify's ecosystem.
WooCommerce (WordPress)
PHP-based monolith with plugin architecture; simpler for solo developers and small shops but less composable and higher downtime during custom deployments.
Medusa
Node.js-based headless commerce platform; similar composable architecture but TypeScript-native and smaller ecosystem; compare language/tooling fit.
Build on saleor with DEV.co software developers
Assess self-hosting vs. Saleor Cloud, review GraphQL extensibility patterns, and confirm Python/DevOps resources align with your team. Test the API with a developer account at cloud.saleor.io.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
saleor FAQ
Can I use Saleor with a non-Python frontend?
Do I have to use Saleor Cloud or can I self-host?
How do I extend Saleor without modifying the core?
Is Saleor suitable for a startup with 1-2 engineers?
Work with a software development agency
Adopting saleor is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source ecommerce software in production.
Ready to evaluate Saleor for your commerce platform?
Assess self-hosting vs. Saleor Cloud, review GraphQL extensibility patterns, and confirm Python/DevOps resources align with your team. Test the API with a developer account at cloud.saleor.io.