The open-source framework for developers building custom ecommerce applications

Closed SaaS gives you a sandboxed scripting hook and a webhook contract, then stops. A DIY composable stack hands you primitives to assemble and a glue layer you maintain forever.

Vendure sits in between. The commerce fundamentals are already built and wired together, and the extension points are first-class, in the same backend as the core, with the same access to services and data the core itself uses.

Catalog, pricing, orders, customers, channels, the admin API, and the extension model all live in one NestJS application. You don't assemble Vendure Core from packages. You clone it, run it, and start extending where your business logic lives.

One repo, one data model, one set of APIs. Add your logic to a backend that is already shaped like commerce, instead of standing one up from scratch.

A Vendure deployment runs two Node.js processes from one codebase: the server handles Shop and Admin API requests, while the worker processes background jobs such as email, search indexing, and integration hand-offs. Both share a SQL database and persistent job queue.

Scale servers and workers independently. Plugins run inside the same processes, so extensions use the same topology without adding services.

For details, see the architecture overview, worker and job queue, and deployment topology.

Every extension builds on the same GraphQL surface the core exposes: one introspectable schema, one codegen pipeline. The Admin API and Shop API are both extensible, both type-safe, and both consumed the same way as the rest of Vendure.

Your customisations are your code, in your repo. The Vendure core is upgraded as a versioned dependency, the way your team upgrades anything else. Type-safety catches breaking changes at compile time, in the code you wrote, not at runtime in production.

No permanent fork to rebase, no upgrade you skip because the cost is too high. Your business logic moves forward with the platform.

Node.js, TypeScript end to end, NestJS as the application framework, GraphQL for the storefront and admin APIs, and a SQL database your operations team already runs on PostgreSQL, MySQL, or MariaDB.

These are patterns modern backend teams ship every day. Engineers who've never touched Vendure recognise the shape on day one, and hiring against this stack is hiring on the open market, not a niche skill set behind a paywall.

Vendure's codebase is typed end to end, organised by predictable, well-documented patterns, and public on GitHub. Those are the conditions modern AI coding tools need to read and write correct code, the same way a human engineer does.

Teams implement faster with AI on Vendure because the code is open, code-first, and has explicit extension points to target. Your engineers and their assistants work against the same codebase that runs in production, not a black box they have to guess at.

Self-hosting Vendure isn't a one-way door. The application you run inside your infrastructure is the same one Vendure operates on Vendure Cloud: same code, same data model, same APIs.

Moving to Cloud is a runtime change, not a re-platform. Your custom code, data model, and integrations keep working. You change where Vendure runs, not what it does.

Security's first reaction to open source is risk. The honest answer turns that around: when the code is inspectable, transparency is the control, not the gap. You can read the source, verify the release, and confirm what you install came from our pipeline.