Why We Built Our Default Stack Around Hydrogen, Sanity and Algolia

The principle behind the stack

The best ecommerce stack isn't the one with the most impressive technology. It's the one where every team can move independently without breaking things for each other.

Developers need a framework that's fast to build on and clean to maintain. Marketing teams need a CMS they can use without filing tickets. Merchandisers need search and discovery tools they can control without waiting for a sprint. And the whole thing needs to perform under load, scale across markets, and be structured enough for AI agents to operate on when that capability matures.

That's what drove each choice in our default stack.

Hydrogen: the frontend

We covered the Hydrogen vs Next.js comparison in detail, but the summary is this: for pure Shopify Plus commerce, Hydrogen ships faster because the commerce primitives are built in.

Cart management, product queries, collection rendering, checkout redirects: the things every Shopify store needs work out of the box. We're not writing Storefront API queries from scratch or managing cart state in custom hooks. Shopify maintains those patterns, and we build on top of them.

Oxygen hosting eliminates the infrastructure conversation entirely. Edge deployment, SSL, CDN, auto-scaling: it's handled. Our team focuses on the storefront experience, not DevOps. For stores where the Shopify Plus commerce experience is the core product, which is the majority of what we build, this removes friction that Next.js would add.

The result: we typically deliver a headless Hydrogen build 3-4 weeks faster than an equivalent Next.js build. At our rates, that's a meaningful cost saving for the client. See our headless cost breakdown for the full picture.

Sanity: the content layer

We've written extensively about why Sanity wins for ecommerce and why structured content matters for AI readiness. The practical reasons we chose it as our default come down to three things.

First, structured content that maps to commerce. Sanity thinks in typed documents and references, not pages and blocks. A promotional module has defined fields for headline, body, CTA, product references, and scheduling. Your marketing team builds campaigns by assembling these modules. The design system is enforced by the schema: they literally can't create something that breaks the design.

Second, real-time collaboration with live preview. Multiple editors can work on the same content simultaneously, and changes preview against the actual Hydrogen storefront in real time. Your team publishes with confidence instead of submitting changes and hoping they look right.

Third, GROQ queries give our developers precise control over data fetching. We request exactly the content each page needs: no over-fetching, no under-fetching. This translates directly to faster page loads and cleaner code.

Algolia: the search and discovery layer

Not every store needs Algolia. We've been clear about that in our Algolia vs Shopify Search comparison. But for stores where search is a meaningful part of the shopping experience (15%+ of sessions include a search, 200+ products), Algolia earns its place in the stack.

The real value isn't the speed (although sub-50ms results are genuinely instant). It's merchandising control. Your merchandising team can pin products to specific search queries, boost new arrivals, hide out-of-stock items, and create landing pages from search results, all through a dashboard without involving a developer.

In a headless Hydrogen build, Algolia integrates cleanly and performs exceptionally. The search experience matches the performance of the rest of the stack, and your merchandising team gets tools that Shopify's native search simply doesn't provide.

How they work together

The individual components are strong. The integration is where the real value compounds.

Sanity's content references can point to Shopify products, which Algolia indexes for search. A marketing campaign in Sanity can feature specific products that are boosted in Algolia results and rendered by Hydrogen components. All three systems share the same product data sourced from Shopify's Storefront API, so there's a single source of truth for commerce data with each layer adding its own speciality on top.

For agentic commerce, this stack is well-positioned. Every layer is API-accessible. Every piece of data is structured and typed. Shopify's MCP servers can access commerce data. Claude's Sanity connector can manage content. Algolia's API handles search. An AI agent can operate across the entire stack because every component was designed for programmatic access.

When we deviate

This is our default, not our only option. We reach for Next.js when the project has significant non-commerce functionality or the team has deep Next.js expertise. We use Prismic when budget constraints make Sanity's pricing challenging for smaller projects (we've built several stores on Prismic including Carwyn Cellars and Smash). We skip Algolia when search volume doesn't justify the cost.

The stack serves the brand, not the other way around. But after years of building headless Shopify Plus stores, Hydrogen + Sanity + Algolia is where we start the conversation. It's earned that position. Talk to our team about whether it's right for your brand.