Skip to main content
This page is the side-by-side feature matrix for all seven Vortex Apps. Use it when you want to compare the apps on a single dimension (which platforms each supports, which capability is unique to which app, which team is the typical primary user). For decision-tree guidance by scenario, see When to use which Vortex App.

At a glance

AppPlatform supportPrimary capabilityPlan tierTeam fit
StagingProBigCommerceStorefront stagingPaid plansDeveloper / ops
RollbackProBigCommerceContinuous backup + rollbackPaid plansOps / merchandiser
Vortex StagingShopifyStorefront stagingPaid plansDeveloper / ops
Vortex BackupShopifyContinuous backup + rollbackPaid plansOps / merchandiser
DryRunProAdobe Commerce / Magento CloudMulti-project staging + backupPaid plansDeveloper / agency
CloudHubMultichannel (Amazon, eBay, Walmart, OnBuy, others)Multichannel inventory + OMS + repricingPaid plansOps / merchandiser / finance
App BuilderCross-platformAI-agent-built custom appsPaid plansOps / merchandiser / marketer / founder

Platform support matrix

A check means the app fully supports the platform. A dash means the app does not support that platform. A small note explains nuances.
AppBigCommerceShopifyAdobe CommerceMagento Open SourceAmazoneBayWalmartOnBuy / Cdiscount / FNAC / RakutenCustom storefront
StagingProyes
RollbackProyes
Vortex Stagingyes
Vortex Backupyes
DryRunProyes (Cloud)
CloudHubyes (channel)yes (channel)yesyesyesyes (and others)
App Builderyes (read+write)yes (read+write)yes (read+write)yes (read+write)yes (via CloudHub)yes (via CloudHub)yes (via CloudHub)yes (via CloudHub)partial (via webhook tool)
Notes:
  • StagingPro / RollbackPro / Vortex Staging / Vortex Backup are platform-bound by design. The internals of staging and backup require platform-specific hooks that do not abstract.
  • DryRunPro supports Adobe Commerce Cloud (the SaaS edition, also called Magento Cloud). It does not support Magento Open Source or self-hosted Adobe Commerce on-premise.
  • CloudHub integrates with Shopify and BigCommerce as channels (one of many destinations for the master SKU), not as the primary storefront platform. If you only sell through one Shopify or BigCommerce store, CloudHub is overkill.
  • App Builder is platform-agnostic. It reads from any connector authenticated in the workspace and writes through whatever channels are wired up.

Capability matrix

The capability matrix shows which app does what. Some capabilities are unique to one app; others appear in multiple apps with platform-specific implementations.
CapabilityStagingProRollbackProVortex StagingVortex BackupDryRunProCloudHubApp Builder
Spin up a staging environmentyesyesyes
Continuous full-store backupyesyesyes (snapshot)
One-click rollbackyesyesyes
Point-in-time restoreyesyesyes
Multi-project stagingyes
On-demand environment fleetyes
Master SKU + multichannel syncyes
Pending order workflow (scan / pack / ship)yes
Repricing automationyes
Warehouse managementyes
Multi-account / VendorDB— (team scope)yes— (workspace scope)
Build custom workflows from a promptyes
Run scheduled or event-triggered jobsyes
Read across every connected sourceyes
Write to Slack / Teams / email / Jirayes
Integrate Ask Viq Q&A as a toolyes
Subscribe to Vortex Mind findingsyes
SWAT report and code audityes
Docker / Warden package outputyes
FBA inventory visibilityyes— (read via CloudHub)
Buy-box analysisyes— (read via CloudHub)

Plan tier reference

Vortex Apps are available on paid plans. The exact apps included on each plan tier vary; this matrix is plan-agnostic and indicates the typical inclusion pattern at general availability:
AppTypical plan inclusion
StagingProIncluded on BigCommerce-focused paid plans
RollbackProIncluded on BigCommerce-focused paid plans
Vortex StagingIncluded on Shopify-focused paid plans
Vortex BackupIncluded on Shopify-focused paid plans
DryRunProIncluded on Adobe-focused or enterprise paid plans
CloudHubIncluded on multichannel-focused or enterprise paid plans (often a separate add-on given its operational scale)
App BuilderIncluded on most paid plans, with run-volume allowances scaling by tier
For specific tier inclusions and pricing, see your account’s plan documentation or contact your account manager.

Team-fit matrix

The “ideal user” for each app, based on what the app does and who tends to operate it day to day.
RoleStagingProRollbackProVortex StagingVortex BackupDryRunProCloudHubApp Builder
Developer / engineerprimarysecondaryprimarysecondaryprimarysecondary
Operations leadsecondaryprimarysecondaryprimarysecondaryprimaryprimary
Merchandiserprimaryprimaryprimaryprimary
Marketerprimary
Financesecondarysecondaryprimarysecondary
Customer servicesecondary (CloudHub Customer Services module)primary
QA / release managersecondarysecondaryprimary
Founder / small team ownervariesvariesvariesvariesvariesprimary
Adobe agency / solution partnerprimarysecondary
A “primary” user is the team that will spend most of their day in the app. A “secondary” user touches the app weekly or for specific tasks but is not the daily owner. A dash means the app is rarely used by that role.

Cross-app dependencies

Some apps are stronger when paired. The matrix shows recommended pairings.
If you use this app…Strongly consider also using…
StagingProRollbackPro (the staging plus rollback safety pair)
Vortex StagingVortex Backup (Shopify staging plus backup pair)
DryRunProApp Builder (orchestrate dryrun lifecycle from prompts)
CloudHubApp Builder (ops automation across the multichannel data)
App BuilderWhichever staging or backup app fits your platform, so app builder workflows that write to the storefront have a safety net
The pairings are not enforced; nothing in the platform prevents using one app without the other. They are the patterns most merchants converge on after a few months of operation.

Frequently asked questions

Can I use a Vortex App without authenticating any connectors? Most apps require at least one connector. Staging and backup apps need the storefront connector for the platform they target. CloudHub needs at least one marketplace connector. App Builder is the most flexible: you can build very simple apps with just one source, but you cannot build anything without at least one source. Are these apps standalone, or are they all built on the same engine? The engines are app-specific. StagingPro and RollbackPro share architecture under the hood (BigCommerce platform internals); Vortex Staging and Vortex Backup share Shopify-internal architecture; DryRunPro is Adobe-specific; CloudHub has its own multichannel engine. App Builder is the agent framework. The shared layer across all of them is the connector and credential model and the workspace tenancy. Will buying one app help me get a discount on another? Pricing structure depends on plan tier. The most common bundle is the platform-pair bundle (StagingPro + RollbackPro on BigCommerce, Vortex Staging + Vortex Backup on Shopify) where the two apps are sold together because they cover complementary safety nets. Contact sales for current bundle pricing. Are Vortex Apps available standalone, outside of the wider Vortex IQ platform? The apps run inside the Vortex IQ workspace. The workspace ties together connectors, credentials, monitoring, alerts, and the rest of the AI OS. Some apps (CloudHub in particular) have a long history as standalone products and continue to support a standalone mode for legacy customers. New customers typically run them inside the wider workspace. Which app is most popular? Across the merchant base, App Builder sees the highest weekly active usage (because it spans every department) and CloudHub has the highest seat-count per merchant (because multichannel ops involves many roles). The staging and backup apps have the highest per-merchant satisfaction (because they prevent the most expensive failure modes). All have their place.