Choosing a hosting platform
This page compares the two hosting platforms BigCommerce documents and tests for Catalyst: Native Hosting, BigCommerce’s own hosting service built on Cloudflare, and Vercel, a third-party Next.js hosting platform. Both run the same Catalyst project built with the same tooling. The difference is where your storefront runs, how you operate it, and how you’re billed.
The Catalyst CLI is generally available, but Native Hosting is currently in closed beta. There may be breaking changes to the Native Hosting APIs as we finalize them. To express interest in gaining access, fill out the Native Hosting Closed Beta Interest Form.
Platform and integration
Deployment and workflow
Custom domains and SSL
Performance and caching
Product catalog images are served and optimized through the BigCommerce CDN on both platforms. That comes from Catalyst itself, not the hosting provider.
For details on these Next.js features, see Incremental Static Regeneration, Caching, and use cache in the Next.js documentation.
Monitoring and troubleshooting
Configuration
Reliability and operations
Commercial
Recommendations
Choose Native Hosting if you want:
- A single-vendor stack integrated with BigCommerce, with no separate hosting account, invoice, or vendor relationship.
- Bundled cost and a lower total cost of ownership.
- A deployment path built for Catalyst and driven entirely by the Catalyst CLI, with native channel, domain, and storefront management.
- BigCommerce support across your storefront and hosting.
Native Hosting is the recommended path for new Catalyst storefronts.
Choose Vercel if you need:
- A hosting option while you wait for Native Hosting closed beta access.
- A general-purpose hosting platform, or you already host other projects on Vercel.
- Push-to-deploy Git automation and a preview URL for every branch.
- Dashboard-managed, team-shared environment variables.
- One-click rollback and a visual deployment history.
- Built-in performance and usage analytics.
This comparison reflects current availability. To deploy with Native Hosting, see Native Hosting: Getting Started. To deploy with Vercel, see Deploy to Vercel.