Spwig is open source
The commerce platform is AGPL-3.0. The SDKs are Apache. Fork it, run it, ship it — on your infrastructure or ours.
Spwig Commerce
The full open-source commerce platform. Django + PostgreSQL, multi-language, multi-currency, headless-ready. AGPL-3.0-or-later.
Explore the ecosystem
Two licences by design: AGPL for the platform, Apache for the SDKs.
Spwig Installer
One-command install. Docker, PostgreSQL, Redis, TLS, admin bootstrap.
View on GitHubSpwig Components
Themes, provider integrations, and utility components. Marketplace-installable.
View on GitHubTheme SDK
Build custom storefront themes. Apache — ship proprietary themes without AGPL obligations.
View on GitHubHeadless SDK
JavaScript SDK for headless storefronts and apps.
View on GitHubProvider SDKs
Payment, shipping, email, GeoIP integrations. Apache so proprietary provider integrations are welcome.
View on GitHubReact SDK
React bindings and hooks for the headless SDK.
View on GitHubSame binary. Licence file flips the flags.
There's no 'Community build' vs 'Pro build' — the same repo builds every edition. A signed licence file toggles paid modules at runtime.
Community
Auto-bootstraps a signed licence on first boot. No server round-trip. No key required.
- Full platform, storefront + admin
- Themes, page builder, all providers you configure
- Full POS terminal support
- Marketplace access + telemetry (opt-out)
- Rate-limited GeoIP / geocoder / push
Pro
Purchased licence key, activated in-admin.
- Everything in Community
- Hosted email gateway (warm IPs, DKIM)
- Higher hosted-service rate limits
- Priority support
- Advanced reporting
Enterprise
Purchased licence key, activated in-admin.
- Everything in Pro
- Enterprise SSO (Azure AD, Okta)
- Highest hosted-service rate limits
- Dedicated onboarding
Fork the repo and patch out the gates — the licence permits it. You just can't call the result 'Spwig'.
What AGPL actually means for you
Plain-language read of the licence — not a lawyer's opinion.
You can
- Run Spwig for your own store, forever, for free.
- Modify the code however you like.
- Distribute your modified version to friends, colleagues, clients.
- Offer it as a hosted service to third parties.
- Fork it and go your own way.
You must (if you distribute or offer over a network)
- Publish your modifications under AGPL-3.0-or-later.
- Make your modified source available to your users.
You cannot
- Take Spwig, close-source your modifications, and offer it as SaaS without publishing the source.
Practical example
A merchant running Spwig for their own store has no publication obligation — they're the user, not offering a service. An agency that builds a modified fork and hosts it for clients does have to make the modifications available to those clients.
Apache SDKs. AGPL core. Proprietary providers welcome.
A payment company can build a Spwig provider integration and ship it as a proprietary, closed-source component — because the SDK it builds against is Apache-2.0. Only modifications to the AGPL core would trigger publication obligations, and provider integrations aren't modifications to the core.
This is the same pattern that lets proprietary WordPress plugins, Odoo modules, and Django third-party apps coexist with copyleft cores. It's intentional.
How we fund this
The Community edition is free by design because we make money on adjacent products. Here's the deal — plainly.
Pro & Enterprise editions
Paid licence keys unlock hosted email gateway, higher rate limits, priority support, and enterprise SSO. Same binary — the key just flips the flags.
Managed Hosting
If you'd rather not run servers, we host Spwig for you. Managed infra, updates, backups, support.
Marketplace
A commission on paid components in the marketplace. Optional — the platform works without it.
Our Promise
The open-source commerce core stays AGPL. DCO not CLA — we can't unilaterally relicense, and that's the point.
We'd rather have you self-hosting Community for free than gated behind a paywall. That's the model.
Our commitments
Small print, plainly stated.
DCO, not CLA
Contributions are signed off under the Developer Certificate of Origin — no copyright assignment paperwork. You keep the copyright on what you contribute. We couldn't relicense the platform without every contributor's consent, and that's the point.
Trademark
SPWIG® is a registered trademark of Spwig Pte Ltd. The AGPL covers the code, not the marks. A fork can call itself anything except "Spwig" or something confusingly similar. See the trademark policy for the details.
Anonymous telemetry
Community installs send one anonymous ping per day: install UUID, version, edition, country, feature-flag bucket counts. No IPs stored, no customer data. Opt out with SPWIG_TELEMETRY=0.
Join the community
Ask questions, share what you build, and help shape the roadmap.
Optional — for those who don't want to run servers
Don't want to self-host?
Spwig Hosting starts at €35/mo. Managed infrastructure, updates, backups, and support — get your store live in minutes.
See hosting plans