Gantry

A multi-cloud infrastructure platform that lets developers deploy any framework using a single, consistent workflow. Stop juggling Vercel, Vapor, Ymir, and dozens of other deployment tools. Define your infrastructure once and deploy anywhere.

If you have a container, we can lift it into place.

The Problem

Modern development teams face a fragmented deployment landscape:

Single-framework deployment tools: Vapor only deploys Laravel. Vercel is optimized for Next.js. Ymir only handles WordPress. Each tool does one thing well but can't help with the rest of your stack.
No unified architecture: Larger applications use multiple frameworks: a Laravel API, a Next.js frontend, a WordPress marketing site. Current tools force you to deploy each piece separately with no shared infrastructure.
Scattered infrastructure: Services spread across different providers with no unified networking
Security gaps: No easy way to create private networks between services deployed on different platforms
Vendor dependency: Each platform owns your infrastructure, making migration painful
Inconsistent workflows: Every framework deploys differently, requiring specialized knowledge for each

You end up with services that can't securely communicate, infrastructure you don't control, and a deployment process that requires expertise in a dozen different tools.

The Solution

Gantry provides a unified layer for deploying any application to any cloud, with proper networking, security, and scalability built in.

One workflow. Any framework. Any cloud. Your infrastructure.

Core Concepts

Clouds

Connect your cloud provider accounts (AWS, Google Cloud, Azure) to the platform. Your infrastructure runs in your accounts. We orchestrate it, you own it.

Networks

Create isolated virtual networks within a cloud region. All services deployed to a network can communicate securely over private IPs, regardless of framework or deployment type.

Network: "production-us-east"
├── Laravel API (serverless)
├── Next.js Frontend (serverless)
├── WordPress Marketing Site (container)
└── Redis Cache (managed service)

All communicating privately, no public internet exposure between services.

Clusters

Optional compute clusters for services that need dedicated capacity. Run containers on managed Kubernetes or container orchestration platforms when serverless isn't the right fit.

Projects

Logical groupings of related services. A project might be a single application or a collection of microservices that make up a product.

Environments

Each project supports multiple environments (development, staging, production) with isolated resources and configuration. Promote deployments through your pipeline with confidence.

Tasks

The actual workloads you deploy. A task can be:

A web application (Laravel, Next.js, Django, Rails, etc.)
A background worker (queue processors, cron jobs)
An API service (REST, GraphQL, gRPC)
A static site (with global CDN distribution)

Deployment Modes

Every task can be configured with the deployment mode that fits its requirements:

Serverless

Scale to zero when idle, scale up instantly under load. Pay only for what you use.

Best for: Variable traffic, cost optimization, APIs, web applications
Scaling: Automatic, based on concurrent requests
Cold starts: Optimized runtimes minimize startup latency

Container (Always-On)

Run in a cluster with dedicated capacity. Consistent performance with no cold starts.

Best for: Latency-sensitive workloads, stateful services, predictable traffic
Scaling: Horizontal auto-scaling based on CPU, memory, or custom metrics
Availability: Multi-AZ deployment for high availability

Event-Driven

Execute in response to events: queue messages, schedules, file uploads, database changes.

Best for: Background processing, ETL pipelines, async workflows
Triggers: Queues, cron schedules, webhooks, cloud events
Scaling: Automatic based on queue depth or event volume

Hybrid

Combine modes for complex workloads. Run a web tier serverlessly while keeping workers always-on.

Framework Support

Many deployment tools only support a single framework... Vapor for Laravel, Vercel for Next.js, Ymir for WordPress. This forces teams to use separate tools for each part of their stack, with no way to connect them.

Gantry is framework agnostic, it deploys containers, without looking inside.

How It Works

1. Connect Your Cloud

Link your AWS, Google Cloud, or Azure account. Gantry uses scoped credentials to manage infrastructure on your behalf.

2. Create a Network

Define a network in your preferred region. This creates the foundational VPC, subnets, and security groups.

3. Define Your Project

Create a project and configure your environments. Each environment gets isolated resources.

4. Deploy Your Tasks

Add tasks for each service in your application. Configure the framework, deployment mode, and scaling rules.

5. Ship

Push your code. Gantry builds, deploys, and manages your infrastructure automatically.

Example: Full-Stack SaaS Application

A typical SaaS application deployed on Gantry:

Network: production-us-east-1 (AWS)
│
├── Cluster: main
│   └── PostgreSQL (RDS)
│   └── Redis (ElastiCache)
│
└── Project: acme-saas
    │
    ├── Environment: production
    │   ├── api (Laravel, serverless)
    │   │   └── Scales 0-100 based on requests
    │   │
    │   ├── frontend (Next.js, serverless)
    │   │   └── Scales 0-50 based on requests
    │   │
    │   ├── admin (WordPress, container)
    │   │   └── 2 instances, always on
    │   │
    │   ├── queue-worker (Laravel, container)
    │   │   └── Scales 1-20 based on queue depth
    │   │
    │   └── scheduler (Laravel, event-driven)
    │       └── Runs cron jobs
    │
    └── Environment: staging
        └── (mirrors production at smaller scale)

All services communicate privately. The Laravel API calls Redis directly over the internal network. The Next.js frontend calls the API over a private endpoint. Nothing is exposed except what you explicitly make public.

Comparison

Capability	Gantry	Vapor	Vercel	Ymir	Traditional VPS
Frameworks supported	Any	Laravel only	JS-focused	WordPress only	Any
Multi-cloud	✓	AWS only	Vercel infra	AWS only	Manual
Private networking	✓	Limited	✗	Limited	Manual
You own infrastructure	✓	✓	✗	✓	✓
Serverless option	✓	✓	✓	✓	✗
Container option	✓	✗	✗	✗	✓
Unified deployment	✓	✗	✗	✗	Manual

Getting Started

Create an account at [gantrydeploy.com]
Connect a cloud provider using our guided setup
Create your first network in your preferred region
Deploy a project using our CLI, console, or CI/CD integration

Architecture Principles

You Own Your Infrastructure

Everything runs in your cloud accounts. Gantry orchestrates and manages it, but you retain full ownership and access. Export your infrastructure definitions at any time.

Security by Default

Private networking, encrypted secrets, least-privilege access. Services are isolated by default and only communicate when explicitly configured.

Framework Agnostic

Gantry optimizes for popular frameworks but supports any containerized application. If it runs in Docker, it runs on Gantry.

Cloud Agnostic

The same workflow works across AWS, Google Cloud, and Azure. Migrate between clouds or run multi-cloud architectures without changing your deployment process.

Cost Efficient

Serverless-first architecture means you pay for what you use. Scale to zero during off-hours. Right-size container workloads automatically.

Use Cases

SaaS Applications

Deploy your entire stack API, frontend, workers, admin panels with unified networking and scaling.

Agency

Manage multiple client projects across different frameworks and clouds from a single console.

Enterprise

Use your own infrastructure. Run Gantry in your own cloud accounts with your own compliance requirements.

Migration

Move off vendor-specific platforms like Vapor or Vercel incrementally. Run Gantry alongside existing infrastructure during transition.