Vendure Core vs Vendure Platform: When Open Source Is Enough

The question behind the question

Teams evaluating Vendure usually ask "Core or Enterprise?" The honest version of that question is: where is the line between what we should build on the free framework and what we should pay for instead of building. Get that line right and Vendure is one of the best value decisions in commerce. Get it wrong and you either pay for capability you do not need, or you rebuild an enterprise layer that already exists.

Here is how the two editions actually differ, and how to decide.

What Vendure Core gives you, for free

Vendure Core is free and open source under GPLv3. This is not a crippled community trial. Core is the full commerce framework:

• the admin dashboard,
• the GraphQL API,
• the plugin architecture,
• multi-channel support,
• multi-currency through Channels,
• and every foundational commerce building block: products, variants, orders, customers, promotions, fulfillment.

For a large share of catalog and direct-to-consumer businesses, Core plus well-chosen plugins is a complete, production-grade platform. The framework is designed to be extended, so a competent team can build a lot on top of it without ever touching the commercial tier.

What Vendure Platform adds

Vendure Platform, the commercial offering Vendure now presents publicly in place of the former tiered grid, is Core plus the enterprise capability layer that most teams stop trying to build themselves:

• a production-ready storefront,
• the enterprise plugin suite,
• an advanced pricing engine and CPQ (configure, price, quote),
• business hierarchies,
• single sign-on with OIDC and SAML,
• audit logging,
• dedicated support backed by a Service Level Agreement,
• and a commercial license.

These are not nice-to-haves invented to justify a price. They are the exact capabilities that turn into multi-month builds when an enterprise needs them and they are not there.

The signals that you actually need Platform

Reach for Platform when one or more of these is real, not hypothetical:

• Complex B2B pricing. Customer-specific price lists, quotes, and configurable products. Building a correct CPQ engine yourself is a project, not a plugin.
• Enterprise identity. Your buyers' IT requires SSO via SAML or OIDC. This is usually non-negotiable in enterprise procurement.
• Audit and compliance. You need a defensible audit trail of who changed what, for regulators or large customers.
• Business hierarchies. Multiple buying organizations, sub-accounts, and approval chains.
• An SLA you can point to. Operations needs guaranteed response times, not best-effort community support.

If two or more of these are on the table, Platform is usually cheaper than building and maintaining the same thing on Core.

When Core plus custom plugins is the better call

Stay on Core when:

• your catalog and checkout are standard, even if large,
• you have a team (or a partner) that can build and own plugins,
• your B2B needs are light or absent,
• and you want maximum control with no license line.

One thing to weigh honestly: Core is GPLv3. The copyleft terms matter if you intend to distribute modified Vendure code. For most teams running it as their own hosted commerce backend, this is a non-issue, but it is worth a five minute check with whoever owns licensing, the same way you would for any GPLv3 dependency.

The pragmatic path

You do not have to choose forever on day one. A common and sound path: start on Core, build the specific capabilities you need as plugins, and move to Platform when the enterprise requirements above become real and building them yourself stops being the cheaper option. The framework is the same underneath, so the move is an upgrade, not a migration.

Where we fit

We are Vendure specialists. We build custom Vendure plugins, including our open-source Vendure Data Hub plugin for ETL, inventory sync, and product feeds. That means we can take you a long way on Core when that is the right call, and we can tell you honestly when your requirements have crossed into Platform territory rather than quietly billing you to rebuild it.

For the architecture behind production Vendure, see our guides on Vendure production architecture and Vendure plugin architecture, or the Vendure services overview.

If you want a straight answer on Core versus Platform for your specific catalog, B2B model, and compliance needs, start a conversation.

Sources: the official Vendure pricing page and Vendure licensing announcement. Editions and terms can change; confirm current details with Vendure before a commercial decision.