Gateways

The buyer Gateways is aimed at is a small engineering or platform group that has already committed to a hyperscaler but does not want to staff a full infrastructure-as-code practice. On its comparison pages Gateways positions against Vercel, Netlify, Render, Fly.io, Heroku, and Railway by pointing out that those platforms run applications on infrastructure the vendor owns, while Gateways operates infrastructure the customer owns and covers networking and data resources rather than application deployments alone.

A working session in Gateways begins with a project, then environments such as development, test, and production, then the resources inside them. The Gateways canvas renders those resources and their connections with live status, and an activity feed logs resource changes, connections, and teammate actions with filters for resource type, action, and environment. Gateways also ships a browser terminal, SSH access, and a built-in browser IDE for editing files on a running server.

Deployment in Gateways is console-first by design. The vendor llms.txt states that no commands are required: a team can connect a GitHub, GitLab, or Bitbucket repository, deploy a Docker image, or upload a zip or folder of build output, with environment variables set in the same panel. Teams that prefer terminals or pipelines can use the Gateways CLI and its `gateways push` command, and Gateways publishes a REST API reference alongside its resource documentation.

The resource catalog Gateways lists covers servers, autoscaling servers, managed databases, cache servers, storage buckets, static websites, CDNs, DNS records, firewalls, load balancers, and serverless functions. Function runtimes named by Gateways are Node.js 18, 20, and 22, Python 3.11, Go 1.21, Java 11, 17, and 21, and .NET 6. Gateways also markets a single scaling workflow that hides the differing autoscaling configuration screens of AWS, Azure, and Google Cloud behind one setup path.

Packaging in Gateways is capacity-based rather than usage-based, because the compute bill goes to the cloud provider instead of to Gateways. The Free plan in Gateways allows one project, one environment, five total resources, one cloud connection, and one workspace member with community support. Starter, Pro, and Ultimate raise those ceilings to 3/3/15, 15/15/100, and unlimited respectively, and the Gateways pricing page advertises two months free when billed yearly at $99.99, $499.99, and $1,999.90 per year.

The limitation worth weighing before adopting Gateways is scope of control. Gateways supports AWS, Azure, and Google Cloud only, so shops on Oracle Cloud, DigitalOcean, Hetzner, or on-premises hardware get no coverage, and Gateways documents no path for importing existing Terraform state into its canvas. The Gateways terms of service also declare the Service is provided "as is" and disclaim liability for cloud infrastructure costs incurred through use of the Service, which leaves spend governance entirely with the customer.

Compared with category peers, Gateways occupies the middle ground between a raw provider console and a fully managed platform. Where Render or Railway trade control for simplicity and where Terraform or Pulumi trade simplicity for reviewable code, Gateways offers a visual workspace over native provider resources with an explicit exit story: because everything runs in the customer account, work continues in the provider console if the Gateways subscription ends.