Visual architecture map
See projects, environments, and resources in one live view. Use it as the shared reference during reviews, debugging, and handoffs.
Cloud infrastructure,organized in one workspace
Deploy and operate cloud resources inside your own AWS, Azure, or Google Cloud account.
- Native cloud resources
- Ship from Git, Docker, ZIP, CLI, or IDE
- Your cloud, your billing
Works with
Architecture
Your stack, mapped live
Cloud control
Deploy, scale, and track
A visual workspace for cloud infrastructureDesign, connect, and operate resources across providers.
Use Gateways to keep architecture, environments, resource status, and team activity in one place while still working with the cloud providers your infrastructure runs on.
Map your stack in one canvas
Create and connect the resource types your application depends on, from servers and databases to DNS, cache, storage, and functions. Keep live status visible in the same workspace.
Broad resource catalog
Visual connections
Live status
Gateways
Work across supported clouds
Connect AWS, Azure, or Google Cloud and manage common workflows from Gateways. Keep provider context available without moving through separate console paths for every task.
AWS, Azure, or Google Cloud
Provider-aware workflows
Fewer console switches
Gateways
Configure scaling in one workflow
Set up server scaling for the provider your workload runs on. Use a consistent workflow while Gateways keeps the cloud-specific configuration organized.
AWS, Azure, and GCP support
Server auto-scaling
Consistent setup
Gateways
Cloud complexityAWS Console
EC2
Auto Scaling
Launch Config
Metrics
Alarms
Vendor UIs differ
Auto-scale servers
AWSAzureGCPNo console. No complexity.
Track infrastructure activity
Review workspace activity in one feed, including resource changes, connections, and actions by team members. Filter by resource type, action, or environment.
Activity feed
Resource and action filters
Environment context
Gateways
Activity
View all user activities and actions
Alex ChenConnecteddns#Dns
2 hours agoJan 31, 2026, 6:25 PM
webappmaster
Jordan LeeCreateddns#Dns
2 hours agoJan 31, 2026, 6:24 PM
webappmaster
Sam RiveraCreatedfunction#function-4
1 day agoJan 30, 2026, 4:53 AM
webappmaster
Alex ChenCreatedfunction#function-31
1 day agoJan 30, 2026, 3:28 AM
webappmaster
Organize environments consistently
Lay out development, test, and production environments in a consistent view. Teams can review the same structure whether resources live in one account or across several.
Dev, test, and prod in view
Consistent resource model
Clearer handoffs
Gateways
One place for every resource
Create and manage servers, databases, DNS, storage, containers, and more across the cloud providers you connect. Explore supported resources in the docs.
Terminal
Server
Database
Cache Server
DNS
Firewall
Static Website
Storage Bucket
Docker
Serverless
Terminal
Server
Database
Cache Server
DNS
Firewall
Static Website
Storage Bucket
Docker
Serverless
Firewall
Static Website
Storage Bucket
Docker
Serverless
Terminal
Server
Database
Cache Server
DNS
Firewall
Static Website
Storage Bucket
Docker
Serverless
Terminal
Server
Database
Cache Server
DNS
Built for cloud teams
Manage infrastructure with more context
Gateways gives your team a shared view of architecture, provider workflows, and plan limits, making infrastructure easier to review, operate, and scale.
Guided cloud operations
Run common tasks such as DNS, scaling, and configuration from Gateways while keeping provider context close at hand.
Clear usage boundaries
Compare plan limits, included features, and billing terms clearly, so upgrades are based on capacity needs rather than guesswork.
Questions
Frequently asked questions
How Gateways works with your cloud accounts, what it deploys, and what happens to your infrastructure over time.
Does Gateways run in my own AWS account?
Yes. You connect your own AWS, Azure, or Google Cloud account with an IAM role, and Gateways creates every resource inside that account. Compute, data, networking, and cloud spend stay under your organization, billed directly by your provider.
Do I need to know Kubernetes or Terraform?
No. Gateways provisions native cloud resources through the provider APIs, so there are no Kubernetes clusters to run and no Terraform state to maintain. You design infrastructure on a visual canvas and Gateways calls AWS, Azure, or Google Cloud for you.
What happens to my infrastructure if I stop using Gateways?
It keeps running. Because every resource lives in your own cloud account, you can inspect, SSH into, and operate all of it directly from the provider console if you stop using Gateways or the console is unavailable. There is no proprietary runtime to migrate off.
Which cloud providers does Gateways support?
AWS, Microsoft Azure, and Google Cloud. You can connect more than one provider and manage them from the same workspace, with each project mapped to the account and region you choose.
What can I deploy with Gateways?
Servers, autoscaling servers, managed databases, cache servers, storage buckets, static websites, CDNs, DNS records, firewalls, load balancers, and serverless functions. Functions support Node.js 18, 20, and 22, Python 3.11, Go 1.21, Java 11, 17, and 21, and .NET 6.
How do I deploy an application?
Several ways, and none of them require a command. From the console you can connect a GitHub, GitLab, or Bitbucket repository, deploy a Docker image, or upload a zip or folder of build output. You can also edit files directly on the server through the built-in browser IDE and terminal, or push from your own terminal or a CI pipeline using the Gateways CLI. Environment variables are set in the same panel either way.
Is there a free plan?
Yes. The Free plan includes one project, one environment, and five resources so you can map a first cloud setup at no cost. Paid plans raise the limits on projects, environments, resources, cloud connections, and workspace members, and are billed monthly or yearly.
How is Gateways different from Vercel, Render, or Railway?
Those platforms run your application on infrastructure they own and manage. Gateways operates infrastructure that you own: the boundary is your AWS, Azure, or Google Cloud account, and the scope covers servers, databases, DNS, storage, and the connections between them rather than app deployments alone.
More detail in the documentation and the platform comparisons.