How Gantry Works
Stop juggling deployment tools. Deploy your entire stack in one place with private networking, shared resources, and complete control.
The Traditional Way: A Deployment Nightmare
Deploying a typical SaaS application today means juggling multiple tools, each with its own limitations.
Multiple Tools Required
Vapor for Laravel, Vercel for Next.js, separate WordPress hosting, manual worker setup. Each tool does one thing well but can't help with the rest of your stack.
No Secure Communication
Services can't securely talk to each other. Everything is exposed publicly or requires complex VPN setup. No private networking between your applications.
Scattered Infrastructure
Different providers, different dashboards, different billing. No unified view of your entire application stack.
Vendor Lock-in
Each platform owns your infrastructure. Migration is painful and expensive. You're stuck with their pricing and limitations.
Wasteful Resources
Each tool provisions separate databases, load balancers, and infrastructure, even for low-traffic apps. No way to share resources means paying 3x the cost.
You end up with services that can't communicate, infrastructure you don't control, and costs that spiral out of control.
The Gantry Way: One Platform, Complete Control
Let's follow Acme SaaS as they deploy their whole stack stack. A headless Next.js frontend, WordPress CMS, internal Laravel business application, and background workers, all on Gantry.
Connect Your Cloud
Link your cloud provider account with scoped credentials. Gantry manages infrastructure on your behalf, but it runs in YOUR account. You own it, control it, and can walk away with it anytime. No vendor lock-in.
Create a Network
Define a private network in your preferred region. Gantry sets up the VPC, subnets, and security groups automatically. All services can communicate privately within this network. No required public internet exposure between your applications.
Provision Shared Infrastructure
Acme sets up resources that multiple lower traffic applications will share, significantly reducing costs.
Shared Database (MySQL)
One MySQL server for both WordPress and Laravel. Each app gets its own database, but shares the same server. This reducing costs compared to separate database servers per app.
Shared Cache (Redis)
Used by WordPress and Laravel for caching and sessions. Single Redis instance serves multiple applications.
Load Balancers
Configure load balancers with flexible access rules. The Next.js frontend gets its own public-facing load balancer, while WordPress and Laravel share a load balancer restricted to the internal business network. Includes automatic SSL certificates, health checks, and zero-downtime deployments.
Key Advantage
Traditional deployment tools force separate infrastructure per app. Gantry lets you share resources where it makes sense, significantly reducing costs for lower-traffic applications.
Deploy Your Applications
Acme deploys their complete application stack by running gantry deploy from each project directory (with a Dockerfile).
Next.js Frontend (Headless)
Serverless- Fetches content from WordPress CMS over private network
- Calls Laravel API over private network
- Public-facing with its own load balancer and custom domain
WordPress CMS
Container- Deployed with always-on container configuration
- Powers the Next.js frontend as a headless CMS
- Shares database server and Redis with Laravel
- Access restricted to internal business network via shared load balancer
Laravel Business App
Container- Internal business-facing application for managing operations
- Exposes API to Next.js frontend over private network
- Shares database server and Redis with WordPress
- Access restricted to internal business network via shared load balancer
Background Workers
Event-driven- Deploy queue processors that scale based on queue depth
- Cron jobs run on schedule
- All within the same private network
Why Teams Choose Gantry
The platform built for modern development teams who want control without complexity.
Any Framework, One Workflow
- Deploy Laravel, Next.js, WordPress, Django, Rails
- No more learning different tools for each framework
- Consistent deployment process across your entire stack
Your Infrastructure, Your Control
- Runs in your AWS/GCP/Azure account
- Full ownership and access
- Export infrastructure definitions anytime
- No vendor lock-in
Private by Default
- Services communicate over private network
- No public internet exposure between services
- Enterprise-grade security built in
- Encrypted secrets management
Share Resources, Reduce Costs
- One database server for multiple applications
- Shared load balancers, Redis, Elasticsearch
- Traditional tools force separate infrastructure per app
- Optimize costs by sharing where it makes sense
Gantry vs Traditional Deployment
See how Gantry compares to using multiple single-purpose deployment tools.
| Feature | Traditional Tools | Gantry |
|---|---|---|
| Deployment Tools | Multiple tools required | |
| Infrastructure | Fragmented across platforms | |
| Service Communication | Public or complex VPN | |
| Infrastructure Ownership | Vendor-owned | |
| Resource Sharing | Duplicate resources | |
| Private Networking |
Ready to simplify your deployments?
Gantry is currently in private beta. Contact us to learn more and request early access.