Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.gateways.app/llms.txt

Use this file to discover all available pages before exploring further.

Gateways vs Vercel

Vercel excels at frontend and full-stack deploys tied to Git, with a global edge, serverless functions, and deep Next.js integration on Vercel’s platform. Gateways targets teams that run workloads in their own AWS, Azure, or GCP accounts: VMs, databases, DNS, serverless, and more—composed on a canvas with workspaces, environments, and a unified API.
TopicGatewaysVercel
Where compute runsYour cloud accountsVercel-managed infrastructure
Best fitMulti-service architecture, compliance, existing cloud spendFast web app deploys, edge, framework-native DX
Networking & dataFull VPC-style resources per providerPlatform abstractions (routes, env, KV, etc.)
Use Vercel when your product is a web app and you want zero server ops on a single platform. Use Gateways when you need direct control over cloud resources across providers and a shared diagram of how they connect. Compare hub · API reference