Vendure vs Spryker
Spryker is a genuine enterprise B2B and marketplace platform, priced and staffed like one. This comparison is about the programmes that never needed that scale.
The short answer
Choose Vendure when
- The marketplace never launched and the approval chains stayed simple
- You want mainstream TypeScript, not Yves, Zed and Glue
- You need to deploy outside a PaaS on AWS
- A post-Oryx storefront rebuild is being funded
Choose Spryker when
- You operate a real marketplace with third-party sellers
- You need a mature packaged B2B suite
- You are a large, well-funded programme with a long runway
- A managed PaaS on AWS is the operating model you want
The biggest pain points on Spryker, and how Vendure solves them
The licence keeps working when the contract ends
Spryker is source-available but proprietary. Its public licence covers evaluation, and production use requires a separate agreement. Vendure Core is GPLv3 and cannot be revoked or discontinued for you, the plugin-licence exception keeps your customisations proprietary, and your data sits in your own SQL database. Exit means continuing to run what you already have. Deployment follows the same logic: any cloud or on-premises rather than a PaaS on AWS.
You buy the depth you use, at a price that does not move with revenue
Spryker is sold as a sales-quoted annual subscription, with no public price list. Vendure Core is free, Scale is €2,499 a month on a 12-month term and Enterprise starts at €60,000 a year: flat, cumulative, with no GMV charge, no per-order surcharge and no per-user fee.
Your existing developers already know the stack
Spryker means PHP plus proprietary Yves, Zed and Glue conventions, where a small change spans many layers and the skills do not transfer elsewhere. Vendure is TypeScript end to end on NestJS and GraphQL, with plugins beside the core and no forks.
How they compare
Six dimensions, the same six on every Vendure comparison page. Every claim about Spryker is sourced at the foot of this page.
| Dimension | Vendure | Spryker |
|---|---|---|
| Architecture and extensibility | VendureTypeScript end to end on NestJS, with GraphQL Shop and Admin APIs. Plugins sit beside the core. No forks, no extension cap. | SprykerPHP 8 and Symfony across more than 750 modules, split into Yves, Zed and Glue. You extend by overriding classes across those layers. |
| Licensing and cost model | VendureFree open-source core under GPLv3. Four flat, cumulative plans from €199 a month on a 12-month term, with Enterprise from €60,000 a year. No GMV, per-order or per-user fees. | SprykerSource-available but proprietary: production use requires an active contract. Sales-quoted annual subscription, no public price list. |
| B2B depth | VendureCompany accounts and quotes from Starter. Organization hierarchy at Growth. Contract pricing, single-level order approvals, the audit log and the Next.js B2B storefront at Scale. PunchOut (cXML), Configurator and multi-level approvals with timeouts and delegation at Enterprise. | SprykerMature and wide: business units, roles, approvals, RFQ and quotes, customer-specific pricing, self-service portal, asset-based catalogs, plus a full marketplace suite. |
| Hosting and operations | VendureSelf-host on any cloud or on-premises, in any region. Managed Vendure Cloud is planned for Q1 2027, with a base set of Cloud resources in each paid plan. | SprykerA managed PaaS on AWS. The Code Upgrader ships with PaaS+, not with self-managed deployment. |
| Ecosystem and talent | VendureMainstream TypeScript, Node and GraphQL. No proprietary skill silo. | SprykerPHP plus proprietary conventions, so the skills are Spryker-specific rather than transferable. A focused network of specialised partners. |
| Migration effort | VendureExport catalogue, business-unit and customer-specific price data from Zed. The Twig-based Yves storefront is rebuilt and Glue integrations remapped. | SprykerNot applicable. |
Vendure pricing: a free open-source core, then four flat tiers
Vendure Core is free under GPLv3. Starter, Growth, Scale and Enterprise add B2B capabilities cumulatively, on a flat fee with no GMV, per-order or per-user charges.
Where Spryker is strong
Where Spryker is the better answer, we say so. For a real marketplace with third-party sellers, Spryker fits. This comparison is about the programmes that never got there.
The B2B suite is mature
Business units, roles and permissions, approvals, RFQ and quotes, customer-specific pricing, a self-service portal and asset-based catalogs. This is packaged depth and we should not pretend it is thin.
The marketplace suite is complete
Merchant portal, offers and split orders. If you are operating a real marketplace with third-party sellers, that is Spryker's ground and we would say so directly.
It fits very large, well-funded programmes
Spryker publishes enterprise references in manufacturing, wholesale and B2B marketplaces. Very large multi-entity B2B programmes with dedicated budget and long runways get a managed PaaS on AWS and a platform built for that scale.
When teams move from Spryker to Vendure
If the marketplace never launched and the approval chains stayed simple, the renewal is the moment to ask whether the platform underneath should stay the same.
Complexity that never arrived
where the marketplace never launched and the approval chains are simpler than the licence assumes
Upgrade and maintenance overhead
where a small change spans Yves, Zed and Glue, and each class override has to be carried through every upgrade
Spryker-specific rather than transferable skills
which narrows who can work on the platform
Budget pressure at renewal
which is the moment the total lands on a finance director's desk
A post-Oryx storefront decision
with the composable Oryx framework archived in September 2025, a modern headless frontend is a funded custom build on Glue either way
Migration runs in three phases: catalogue and B2B data export, storefront rebuild, then integration cutover. We scope the effort against what is actually in production rather than quoting a band.
Moving off Spryker?
Export catalogue, business-unit and price data from Zed, rebuild the Yves storefront on the GraphQL API, and remap Glue integrations. Migration guides are being written; the hub has what exists today.
Teams building complex commerce with Vendure
Vendure and Spryker, answered
Yes, when the marketplace never launched and the approval chains are simpler than the licence assumes. If you are operating a genuine marketplace with third-party sellers, Spryker's merchant portal, offers and split orders are real advantages, and Spryker is the better answer.
Company accounts, quotes, lists, quick order and store credit from Starter. Organization hierarchy, managed lists, packaging, gift cards and global search at Growth. Contract pricing, order approvals, the audit log, single sign-on, search analytics and the Next.js B2B storefront at Scale. Negotiation, access policy, advanced approvals, audit governance, Configurator and PunchOut at Enterprise. They are licensed capabilities rather than services you commission.
Vendure Core is free under GPLv3. Four cumulative paid plans sit on top: Starter at €199, Growth at €599 and Scale at €2,499 a month on a 12-month term, with Enterprise from €60,000 a year. Each plan inherits the one below, and there is no GMV charge, per-order surcharge or per-user fee, so growing revenue does not reprice the platform.
Yes. Vendure Core is a complete open-source commerce framework under GPLv3, written in TypeScript on Node.js with GraphQL Shop and Admin APIs. It is free to run and self-host, and the licence cannot be revoked or discontinued for you. The commercial B2B capabilities are separately licensed plugins layered on top of that core. Every paid plan also includes a commercial licence for Vendure Core for your project, as an alternative to GPLv3.
Yes, on any cloud or on-premises, in any region, with your data in your own SQL database. That is what makes EU-mandated and otherwise regulated deployments possible today. Vendure Cloud, our managed hosting, opens as a closed beta for paid plans, with general availability planned for Q1 2027. Each paid plan will include a base set of Cloud resources, and usage above that is billed on top.
Vendure is TypeScript end to end on NestJS with GraphQL APIs, so a strong TypeScript team starts on familiar ground. There is no proprietary language or framework convention to learn first, and the same skills transfer to any other Node project your organisation runs.
Sources (9) · claims last checked 2026
- About Spryker: more than 750 modules, and the Yves, Zed and Glue application layers · docs.spryker.com
- Spryker Code Upgrader: shipped with PaaS+ in the EU and US regions · docs.spryker.com
- Spryker on AWS: the managed PaaS runs on AWS · spryker.com/partners/aws
- Spryker documentation: B2B and marketplace packaged business capabilities · docs.spryker.com
- Spryker evaluation licence: free use is limited to a 45-day evaluation, and a productive live system needs a paid licence · github.com/spryker/spryker-core
- Spryker pricing page: password-protected, with no public price list · spryker.com/pricing
- Spryker Oryx: archived in September 2025 · github.com/spryker/oryx
- Spryker customer stories: published enterprise references in manufacturing, wholesale and B2B marketplaces · spryker.com/customer-stories
- Vendure pricing and plans · vendure.io/pricing
