You build the ecommerce experience. We run the platform underneath.
Connect your Git repository and Vendure Cloud handles deployments, environments, databases, backups, recovery, and scaling. Every paid plan can join the beta when it opens. General availability is planned for Q1 2027.
Environments
4 activeYou own the application. Vendure operates the runtime.
Vendure Cloud runs the same application, data model, APIs, and customisations your team can self-host. Moving between deployment models requires a planned operational migration, but it does not require rebuilding your ecommerce platform.
You keep ownership of your application and integrations. Vendure operates the runtime underneath: the application processes, database, queues, search, storage, caching, deployments, backups, recovery, and scaling. On a generic PaaS, that layer stays your team's job.
Git to production, with the operating model already in place
Connect a Git repository and every pull request can receive its own preview environment. Merging through your release branches promotes the application through staging and production using a controlled deployment process.
Git is the primary workflow. Teams with an established container pipeline can also supply container images, while keeping the same managed Vendure runtime.
Review application and integration changes in an isolated environment before they reach a shared staging or production deployment.
Keep development, staging, and production environments connected to the branches and release process your team already uses.
Deployments run database migrations as part of a controlled release process, with deployment health checks and recovery tooling.
Available in the beta
Cloud opens as a closed beta for paid plans. Beta customers work directly with the Vendure Cloud team through onboarding and operation. Formal production SLAs begin at general availability.
Git-based deployments
Automated deployments, persistent environments, and a preview environment for every pull request.
Managed data services
Managed database, queues, search, storage, and caching configured for a Vendure workload.
Autoscaling and monitoring
Application server and worker workloads scale with demand, with monitoring and alerting across the managed runtime.
Backups and recovery
Production databases include continuous backups and point-in-time recovery.
Selectable regions
Vendure Cloud runs in Frankfurt, Ireland and the US East region. Other regions are available on request.
Direct access to the Cloud team
Work directly with the Cloud team during onboarding and operation, helping shape the service ahead of general availability.
Planned for Q1 2027
General availability is planned for Q1 2027. The following support and deployment options depend on the full Cloud support infrastructure and are planned for GA rather than promised in the beta.
Multi-region routing
Route one Vendure project across multiple supported regions for availability and geographic performance requirements.
Bring Your Own Cloud
Run Vendure Cloud in a supported cloud account your organisation controls, while Vendure manages the Vendure-specific deployment and operations layer.
Formal operational support
Named support contacts, production availability commitments, response-time SLAs, and mature escalation paths into the Vendure engineering team.
Choose where your workload and data run
Vendure Cloud runs in Frankfurt, Ireland and the US East region. Other regions are available on request.
The application workload and associated database, storage, search, queues, and backups remain in the selected region. Exact region availability is confirmed during onboarding.
A clear cost for the runtime your team would otherwise operate
Self-hosting means owning deployments, environments, databases, queues, search, backups, monitoring, recovery, scaling, and the people and processes around them. Cloud moves those runtime responsibilities to Vendure so your team can stay focused on the ecommerce product.
Each paid plan includes a base set of Cloud resources. Usage above that is billed on top of the plan price, at prices published before you activate Cloud. During the beta, your plan price stays the same.
See pricingBilling that fits your procurement model
One vendor for plan and runtime
Your plan covers the capabilities, the support, the commercial licence, and a base set of Cloud resources. Procurement deals with Vendure for the runtime too, rather than adding a separate hosting provider.
Core stays free and self-hosted
Vendure Core stays free under GPLv3, and you can run it on your own infrastructure. Managed hosting comes with a paid plan.
Vendure owns the runtime operations, not just the infrastructure
Vendure operates deployments and managed data services, monitors the workload, handles routine maintenance, coordinates backup and recovery, and investigates runtime incidents. Your team continues to own the application and its business operations, while Vendure handles the infrastructure and DevOps work behind the managed runtime.
You contract with Vendure. Onboarding, billing, operational support, and escalation remain one customer relationship. Beta customers work directly with the Cloud team, and formal operational SLAs begin at general availability.
Teams building complex commerce with Vendure
Common questions about Vendure Cloud
Your plan decides what Vendure can do: Starter, Growth, Scale, or Enterprise, each adding B2B capabilities to the open-source Core. Cloud decides who operates it. Each paid plan includes a base set of Cloud resources, and usage above that is billed on top. You can also self-host the same plan, and self-hosting does not change the plan price.
Vendure operates and supports Vendure Cloud, and is responsible for onboarding, billing, operation and the customer relationship.
The beta is not open yet. When it opens for your project, you work directly with the Vendure Cloud team through onboarding and operation. Formal availability and response-time SLAs begin at general availability, which is planned for Q1 2027.
Each paid plan includes a base set of Cloud resources. Usage above that is billed on top of the plan price, at prices published before you activate Cloud. During the beta, your plan price stays the same.
Yes. Vendure Cloud runs in Frankfurt, Ireland and the US East region. Other regions are available on request. Workloads and their data services stay in the selected region, and residency requirements are confirmed during onboarding.
Yes. Cloud runs the same Vendure application, data model, APIs, and customisations you can self-host. Moving requires a planned data, configuration, and operational cutover, but no ecommerce-platform rebuild.
Git is the primary deployment workflow and the route we recommend. Teams with an established container pipeline can also supply container images.
Formal production SLAs, named support, multi-region routing, and Bring Your Own Cloud are planned for general availability in Q1 2027.
Get Vendure Cloud with a paid plan
Every paid plan can join the Vendure Cloud beta when it opens, ahead of general availability in Q1 2027. Talk to us about your workload, region, and onboarding window.
