Run Vendure on your own infrastructure, in the region you choose
A self-hosted ecommerce platform that runs on the stack your team already operates: a Node.js application, PostgreSQL, and your own cloud or data centre.
Why teams host it themselves
Self-hosting is usually not a preference. It is a requirement that arrived from somewhere else. A regulator wants the data held in a named country. A security review will not approve a shared runtime. A platform team has a standard that everything must fit, or a contract predates the conversation.
Vendure is a normal application, so those requirements are answerable without a special edition. You run it where you run everything else.
The database is yours, in the region you chose, under the jurisdiction you need. There is no commerce-specific storage layer holding a copy somewhere else.
If your organisation deploys to Kubernetes with a particular pipeline, observability stack and secret manager, Vendure goes through that pipeline like any other Node.js service.
Components your team already knows
A PostgreSQL database you already run
PostgreSQL, your managed instance or your own cluster. Paid plans require PostgreSQL; Vendure Core also runs on MySQL and MariaDB. No commerce-specific database and no proprietary storage layer.
Anywhere Node.js runs
A Node.js application on NestJS. Deploy on AWS, Azure, GCP, on-premise, Kubernetes, Docker or a single virtual machine. Standard Redis-compatible cache, standard S3-compatible object storage.
Scales the way your other services do
Stateless at the application layer, scaling behind any load balancer, with job processing on separate worker processes you scale independently. Munch runs more than 10,000 payment transactions a day at peak on Vendure.
Your customisations live beside the core
Extensions sit next to the core rather than inside it, so upgrading does not mean reapplying a fork. The GraphQL APIs your storefront uses are the same ones Vendure Cloud will expose.
Your plan decides what Vendure can do. Where it runs is a separate question.
Starter, Growth, Scale and Enterprise decide the capabilities: company accounts, contract pricing, approvals, the audit trail, the included storefront. Self-hosting does not remove any of them, and there is no self-hosted edition with a shorter feature list.
Vendure Cloud, planned for general availability in Q1 2027, is the other option. It opens first as a closed beta for paid plans. Each paid plan includes a base set of Cloud resources, and usage above it is billed on top. Cloud will run the same application, data model, APIs and customisations you can self-host, so moving between the two is a planned data and operational cutover rather than a rebuild.
A self-hosted Scale deployment includes exactly what Scale on Vendure Cloud will include. See the pricing page for what starts where.
Self-hosted, you pay the plan price, with no surcharge and no discount for taking the work on yourself. On Vendure Cloud, each paid plan includes a base set of Cloud resources. Usage above it is billed on top, at prices published before you activate Cloud.
Once Cloud is available, moving from self-hosted to Vendure Cloud or back requires a data, configuration and operational cutover. It does not require rebuilding the ecommerce platform.
What you are taking on
Self-hosting is a real operational commitment, and it is worth naming the whole of it before you choose: deployments, environments, databases, queues, search, backups, monitoring, recovery, scaling, and the people and processes around them.
For a team that already runs production services, that is familiar work and the marginal cost is small. For a team without that function, it is a hiring decision before it is an infrastructure decision, and the honest recommendation is to plan for Vendure Cloud, due for general availability in Q1 2027, to operate the runtime instead. We would rather say that now than after a launch.
Or start with the free open-source core
Vendure Core is the open-source framework underneath every plan, free forever under GPLv3, and you run it on your own infrastructure. It gives you the commerce backend, the GraphQL APIs, the plugin model and the Dashboard.
The paid plans add the B2B capabilities on top: company accounts, contract pricing, approvals, an audit log and the supported storefront. On Core, those are capabilities your team builds and maintains itself. Read what Core includes on Vendure Core.
What platform teams ask about self-hosting
No. The plan decides the capabilities and the deployment model decides who operates the runtime. A self-hosted Scale deployment has the same capabilities that Scale on Vendure Cloud will have. Self-hosting adds no surcharge. On Cloud, usage above the plan's base set of resources is billed on top.
A Node.js server and worker, and PostgreSQL. Add Redis and S3-compatible storage when you run several instances. Typesense is optional from Growth and needed for search analytics on Scale, which also needs ClickHouse. All of it is standard infrastructure with more than one vendor behind it.
Paid plans need outbound access to the Vendure licence service. The plugins check the licence at start and about once an hour, and keep running for up to 7 days if they cannot reach it. If your environment has no outbound access, contact us and we will arrange it. Vendure Core alone has no licence check. You will also need a route to whichever payment, tax or shipping providers your commerce flow uses, since those are external services by nature.
Only if you already operate production infrastructure and want to. The work is real: backups that have been restored at least once, an upgrade path someone owns, and an on-call rota. If your team does not have that function today, plan for Vendure Cloud, due for general availability in Q1 2027. Each paid plan includes a base set of Cloud resources, and usage above it is billed on top.
No, and the decision is not permanent. Vendure Cloud will run the same application, data model and APIs as a self-hosted deployment, so choosing one does not close the other. Plan a cutover window when you switch, and nothing about the commerce platform is rebuilt.
Work out where Vendure should run
Try Vendure for 14 days on your own infrastructure, or compare the plans to see where self-hosting and Vendure Cloud fit.
