Hosting on Vercel

Evolve can run its entire stack on Vercel: the Next.js storefront, the GraphQL gateway, and the domain services, all in a single Vercel project. This is one of Evolve’s supported deployment targets, alongside the multi-cloud deployment on AWS, GCP, and Azure, and it brings Vercel’s developer experience to the whole platform rather than the storefront alone.

Architecture

On Vercel the stack maps to Vercel Services within one project:

Storefront: the Next.js frontend runs natively on Vercel.
Domain services: the domain services such as catalog, checkout, account, order, content, and quotes run as Vercel Functions on Fluid Compute.
GraphQL gateway: the Federation gateway composes the domain services into one supergraph.

Services reach each other over private Vercel service bindings. Only the storefront and the /graphql endpoint are exposed publicly through rewrites; the domain services are private by default and reachable only through the gateway.

graph TD;
    client["Browser, apps, AI agents"]-->site["Storefront (Next.js)"]
    client-->gateway["GraphQL gateway (/graphql)"]
    site-->gateway
    gateway-->account["account"]
    gateway-->catalog["catalog"]
    gateway-->checkout["checkout"]
    gateway-->order["order"]
    gateway-->content["content"]
    gateway-->quotes["quotes"]

What Vercel brings

Because the whole stack lives in one Vercel project, the platform inherits Vercel’s workflow:

Preview deployments: every pull request gets its own URL running the full stack, storefront, gateway, and services, wired to itself, so a change can be reviewed end to end in isolation.
Instant rollbacks: deployments are atomic and immutable, so reverting to a previous version is instant.
Region pinning: compute runs in the region closest to your data.
Fluid Compute: the domain services scale to zero when idle and reuse instances across requests.
Environment management: configuration and secrets are managed through the Vercel CLI and dashboard.
Observability: per-service logs are filterable in the dashboard, and traces are exported through OpenTelemetry.

Deploying

The whole stack deploys with a single command. See Deploying to Vercel for the one-time setup and the deploy steps.

Alongside multi-cloud

Vercel is additive. The Terraform-based multi-cloud path on AWS, GCP, and Azure remains fully supported, and a service can target both. Choosing Vercel or multi-cloud is a deployment decision, not a change to the application code.