BigCommerce Catalyst Native Hosting on Cloudflare: What Composable Commerce Teams Need to Know

Catalyst is BigCommerce's headless storefront framework, built on Next.js, and until this announcement the hosting story was the same as every other composable storefront: bring your own Vercel, Netlify, or Cloudflare Pages account, wire up your own CI, and own the operational surface yourself. That is a fine answer for a team that already has frontend infrastructure opinions. It is a worse answer for a merchant or agency that chose Catalyst for the commerce logic and does not want hosting to become a second platform decision. BigCommerce's Native Hosting answer, announced at Commerce Live 2026 on April 30, closes that gap directly by putting Catalyst on Cloudflare's network with BigCommerce managing the operational layer.

What Native Hosting on Cloudflare actually adds

The headline mechanics are a CLI for managing deployments, log retention included in the hosting itself rather than bolted on through a third party observability tool, and custom domain support, all at no additional cost according to the announcement. For a team evaluating total cost of ownership on a Catalyst build, that is a real number to remove from the spreadsheet: log aggregation and custom domain routing are two of the quieter line items that show up on a Vercel or Cloudflare Pages bill once a storefront moves past a demo and into production traffic. Running Catalyst on Cloudflare's own edge network also means the storefront inherits Cloudflare's global point of presence footprint without the team configuring a CDN layer on top of a separately hosted Next.js app, which is the architecture most composable storefronts have been assembling by hand up to this point.

This is a different move than Shopify's Hydrogen and Oxygen story

Shopify went through its own version of this host versus bring your own infrastructure decision with Hydrogen, where Oxygen was the first party hosting layer and the broader ecosystem eventually pushed for portability to Vercel and Cloudflare directly. BigCommerce is running that sequence in reverse: Catalyst already supported bring your own hosting, and Native Hosting is the first party option arriving after the framework was already in the wild. The practical effect is similar either way. A merchant gets to choose between a platform managed hosting path with fewer moving parts and a bring your own infrastructure path with more control, and the right choice depends on whether the team already has frontend DevOps capacity or would rather not build it.

Where this sits against the rest of the composable stack

Cloudflare Workers already competes directly with Vercel's edge functions on cost and cold start behavior for general purpose edge compute, and BigCommerce choosing Cloudflare specifically, rather than building a hosting layer on its own infrastructure or partnering with Vercel, is consistent with Cloudflare's broader push into becoming the default landing spot for headless storefronts. For a BigCommerce specific build this mostly simplifies vendor count: commerce logic on BigCommerce, storefront hosting also effectively on BigCommerce's negotiated Cloudflare relationship, rather than three separate vendor relationships for commerce, hosting, and CDN.

What is still unclear until the open beta ships

An open beta announced for summer 2026 is not the same as a generally available, SLA backed hosting product, and the April announcement does not specify pricing beyond "no additional cost" for log retention and custom domains, which leaves the actual Native Hosting base price undefined publicly as of this writing. Teams planning a Catalyst build timed around this feature should treat the summer 2026 beta date as a planning input, not a commitment, and keep a bring your own hosting fallback in the architecture until general availability and a published SLA exist. The B2B and B2C unification on one control panel and one storefront API layer mentioned in the same announcement is explicitly a roadmap item, not something to build against today.

When this applies to your stack

If you are scoping a new Catalyst build and your team does not already have strong opinions about edge hosting, waiting for or joining the Native Hosting open beta removes a real infrastructure decision and its ongoing operational cost from your plate, with the caveat that beta software is beta software and a production launch date should have a fallback plan. If your team already runs a mature Cloudflare or Vercel deployment pipeline for other properties, bring your own hosting likely still gives you more control over caching rules and deployment gates than a managed layer will in its first beta cycle. Contra Collective helps commerce teams make this exact infrastructure call on Catalyst, Hydrogen, and other composable storefront builds before the architecture is locked in.

FAQ

Is BigCommerce Native Hosting for Catalyst available now? No. As of the April 30, 2026 announcement, it is planned to reach open beta in summer 2026, not general availability.

Does Native Hosting replace the option to self host Catalyst? Nothing in the announcement suggests self hosting is being removed. Native Hosting is presented as an additional, managed path, not a replacement for bring your own infrastructure.

What does Native Hosting cost? The announcement states that log retention and custom domain support are included at no additional cost, but it does not publish a base price for the hosting product itself.

Is this the same infrastructure Shopify uses for Hydrogen storefronts? No. Shopify's first party hosting for Hydrogen is Oxygen, a separate product from a separate company. BigCommerce's Native Hosting runs on Cloudflare's network under a direct BigCommerce and Cloudflare arrangement.