> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Vortex Apps Comparison Matrix > Side by side comparison of all seven Vortex Apps. Platform support, capability, plan tier reference, ideal team fit. StagingPro, RollbackPro, Vortex Staging, Vortex Backup, DryRunPro, CloudHub, App Builder compared in one matrix. 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](/vortex-apps/concepts/when-to-use). ## At a glance | App | Platform support | Primary capability | Plan tier | Team fit | | --------------------------------------------- | --------------------------------------------------- | ---------------------------------------- | ---------- | --------------------------------------- | | [StagingPro](/vortex-apps/staging-pro) | BigCommerce | Storefront staging | Paid plans | Developer / ops | | [RollbackPro](/vortex-apps/rollback-pro) | BigCommerce | Continuous backup + rollback | Paid plans | Ops / merchandiser | | [Vortex Staging](/vortex-apps/vortex-staging) | Shopify | Storefront staging | Paid plans | Developer / ops | | [Vortex Backup](/vortex-apps/vortex-backup) | Shopify | Continuous backup + rollback | Paid plans | Ops / merchandiser | | [DryRunPro](/vortex-apps/dryrunpro) | Adobe Commerce / Magento Cloud | Multi-project staging + backup | Paid plans | Developer / agency | | [CloudHub](/vortex-apps/cloudhub) | Multichannel (Amazon, eBay, Walmart, OnBuy, others) | Multichannel inventory + OMS + repricing | Paid plans | Ops / merchandiser / finance | | [App Builder](/vortex-apps/app-builder) | Cross-platform | AI-agent-built custom apps | Paid plans | Ops / 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. | App | BigCommerce | Shopify | Adobe Commerce | Magento Open Source | Amazon | eBay | Walmart | OnBuy / Cdiscount / FNAC / Rakuten | Custom storefront | | -------------- | ---------------- | ---------------- | ---------------- | ------------------- | ------------------ | ------------------ | ------------------ | ---------------------------------- | -------------------------- | | StagingPro | yes | -- | -- | -- | -- | -- | -- | -- | -- | | RollbackPro | yes | -- | -- | -- | -- | -- | -- | -- | -- | | Vortex Staging | -- | yes | -- | -- | -- | -- | -- | -- | -- | | Vortex Backup | -- | yes | -- | -- | -- | -- | -- | -- | -- | | DryRunPro | -- | -- | yes (Cloud) | -- | -- | -- | -- | -- | -- | | CloudHub | yes (channel) | yes (channel) | -- | -- | yes | yes | yes | yes (and others) | -- | | App Builder | yes (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. | Capability | StagingPro | RollbackPro | Vortex Staging | Vortex Backup | DryRunPro | CloudHub | App Builder | | ------------------------------------------- | ---------- | ----------- | -------------- | ------------- | --------------- | -------- | ---------------------- | | Spin up a staging environment | yes | -- | yes | -- | yes | -- | -- | | Continuous full-store backup | -- | yes | -- | yes | yes (snapshot) | -- | -- | | One-click rollback | -- | yes | -- | yes | yes | -- | -- | | Point-in-time restore | -- | yes | -- | yes | yes | -- | -- | | Multi-project staging | -- | -- | -- | -- | yes | -- | -- | | On-demand environment fleet | -- | -- | -- | -- | yes | -- | -- | | Master SKU + multichannel sync | -- | -- | -- | -- | -- | yes | -- | | Pending order workflow (scan / pack / ship) | -- | -- | -- | -- | -- | yes | -- | | Repricing automation | -- | -- | -- | -- | -- | yes | -- | | Warehouse management | -- | -- | -- | -- | -- | yes | -- | | Multi-account / VendorDB | -- | -- | -- | -- | -- (team scope) | yes | -- (workspace scope) | | Build custom workflows from a prompt | -- | -- | -- | -- | -- | -- | yes | | Run scheduled or event-triggered jobs | -- | -- | -- | -- | -- | -- | yes | | Read across every connected source | -- | -- | -- | -- | -- | -- | yes | | Write to Slack / Teams / email / Jira | -- | -- | -- | -- | -- | -- | yes | | Integrate Ask Viq Q\&A as a tool | -- | -- | -- | -- | -- | -- | yes | | Subscribe to Vortex Mind findings | -- | -- | -- | -- | -- | -- | yes | | SWAT report and code audit | -- | -- | -- | -- | yes | -- | -- | | Docker / Warden package output | -- | -- | -- | -- | yes | -- | -- | | FBA inventory visibility | -- | -- | -- | -- | -- | yes | -- (read via CloudHub) | | Buy-box analysis | -- | -- | -- | -- | -- | yes | -- (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: | App | Typical plan inclusion | | -------------- | --------------------------------------------------------------------------------------------------------------- | | StagingPro | Included on BigCommerce-focused paid plans | | RollbackPro | Included on BigCommerce-focused paid plans | | Vortex Staging | Included on Shopify-focused paid plans | | Vortex Backup | Included on Shopify-focused paid plans | | DryRunPro | Included on Adobe-focused or enterprise paid plans | | CloudHub | Included on multichannel-focused or enterprise paid plans (often a separate add-on given its operational scale) | | App Builder | Included 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. | Role | StagingPro | RollbackPro | Vortex Staging | Vortex Backup | DryRunPro | CloudHub | App Builder | | ------------------------------- | ---------- | ----------- | -------------- | ------------- | --------- | --------------------------------------------- | ----------- | | Developer / engineer | primary | secondary | primary | secondary | primary | -- | secondary | | Operations lead | secondary | primary | secondary | primary | secondary | primary | primary | | Merchandiser | -- | primary | -- | primary | -- | primary | primary | | Marketer | -- | -- | -- | -- | -- | -- | primary | | Finance | -- | secondary | -- | secondary | -- | primary | secondary | | Customer service | -- | -- | -- | -- | -- | secondary (CloudHub Customer Services module) | primary | | QA / release manager | secondary | -- | secondary | -- | primary | -- | -- | | Founder / small team owner | varies | varies | varies | varies | -- | varies | primary | | Adobe agency / solution partner | -- | -- | -- | -- | primary | -- | secondary | 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... | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------- | | StagingPro | RollbackPro (the staging plus rollback safety pair) | | Vortex Staging | Vortex Backup (Shopify staging plus backup pair) | | DryRunPro | App Builder (orchestrate dryrun lifecycle from prompts) | | CloudHub | App Builder (ops automation across the multichannel data) | | App Builder | Whichever 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. ## Cross-links * Decision tree by scenario on [When to use which Vortex App](/vortex-apps/concepts/when-to-use). * Common pairings explained on [Multi-app workflows](/vortex-apps/concepts/multi-app-workflows). * Each app's own deep-dive landing page is reachable from the [Vortex Apps index](/vortex-apps/overview). ## 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](/vortex-apps/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.