The enterprise commerce platform for complex B2B, built code-first
Build with Core or Platform. Run it yourself or on Vendure Cloud. Two independent decisions; the architecture stays the same either way.
Closed SaaS slows you down. DIY composable bleeds you out.
Closed SaaS suites lock you into rigid data models, opaque roadmaps, and an integration tax that never ends. DIY composable stacks promise flexibility but turn into a forever-job of wiring, monitoring, and maintaining other people's services.
Vendure sits between them: a code-first commerce platform with the modeling depth of composable and the operational simplicity of managed runtime. One coherent backend, no rigid SaaS limits, no MACH glue work.
One Vendure, two adoption decisions
Adoption splits along two independent axes: what you build with, and how you run it.
Build with a capability layer. Start with Vendure Core, the open-source commerce framework, or Vendure Platform, Core plus the enterprise capability layer most teams stop trying to build themselves.
Run it where it fits. Self-host on your own infrastructure, or run on Vendure Cloud, the managed runtime for any Vendure project, Core or Platform.
Same architecture, same plugin model, same APIs across every combination. Move along either axis later without re-architecting.
Pick a capability layer
Core is the open-source foundation. Platform is Core plus the enterprise capability layer: enterprise plugins, a production-ready storefront, dedicated support, and a commercial license.
Vendure Core
The open-source commerce framework, free under GPLv3. One coherent backend on TypeScript, NestJS, GraphQL, and PostgreSQL. Spin up a project with the Vendure create command and prototype on your own terms before committing.
- Open source under GPLv3, fully extensible
- TypeScript, NestJS, GraphQL, PostgreSQL
- Plugin model shared with Platform and Cloud
- Community support, with paid Core Expert Access available
Vendure Platform
Core plus the enterprise capability layer. Contract pricing and customer-specific price lists, company hierarchies and approval workflows, audit-grade governance, SSO, and advanced search, maintained under one contract by the team that ships Vendure. Commercial license, IP indemnification, SLA-backed support.
- 25+ enterprise plugins covering 100+ enterprise features
- Production-ready Next.js storefront included
- Commercial license with IP indemnification
- SLA-backed support and quarterly roadmap calls
Pick a deployment
The deployment decision is independent of the capability layer. Self-host the same Vendure project on your own infrastructure, or run it on Vendure Cloud, the managed runtime for Core or Platform.
Self-hosted
Run Vendure on infrastructure you control: AWS, Azure, GCP, or your own data center. Your team owns deployment, scaling, observability, and the on-call rota. Supported on Core or Platform.
- Deploy on any cloud or your own data center
- Full control over networking, data residency, and operations
- Your team operates production
- Same codebase as Cloud, no Cloud-only features to give up
Vendure Cloud
The managed runtime for any Vendure project, Core or Platform. Push-to-deploy, autoscaling, backups, regional deploys, and observability, run by the team that builds Vendure.
- Managed runtime for Core or Platform
- Push-to-deploy, autoscaling, point-in-time backups
- Multi-region deploys, EU-only data residency option
- Bring-your-own-cloud supported
Same architecture across every combination
Catalog, pricing, orders, customers, channels, business logic. One extensible backend on TypeScript, NestJS, GraphQL, and PostgreSQL, with the same plugin model and APIs across Core, Platform, and Cloud. Open APIs and a plugin model built for the systems already in your stack: ERP, PIM, fulfillment, payment, and search.
Custom plugins written against Core run on Platform run on Cloud, unchanged. The four combinations (Core self-hosted, Platform self-hosted, Core on Cloud, Platform on Cloud) are all supported paths. Pick what fits today, move along either axis when your needs change. The payoff: lower integration overhead, faster delivery on commerce changes, and an architecture your team owns no matter where it runs.



