PROVIDER - Declarative local development orchestration
Lando
Lando declares services, tooling and proxying in 1 .lando.yml with 20+ recipes for WordPress, Drupal, Laravel and Node, wrapping frequent commands as subcommands; the costs are the Docker dependency, Compose knowledge for custom services and lower community activity.
4pts
Detailed Notes
Pros 5 items
Cons 4 items
Service Overview
Lando is a Docker-based local development orchestration tool that describes services, tooling and proxying in declarative configuration. Its goal is simple: every teammate gets the same environment from one command.
In the development tools category it is declarative local environments: unlike bundles with fixed component sets, Lando lets configuration stack services freely.
Key Strengths
- Declarative configuration: 1 YAML file describes the stack
- Rich recipes: 20+ predefined setups
- Tooling wrappers: frequent commands become lando subcommands
- Free service mix: 3+ databases and caches to combine
- Automatic domains: local domains and certificates handled
Product Ecosystem
Platform capabilities
Service orchestration, recipe initialisation, tooling definitions, proxying and domains, certificate management, service overrides and log inspection.
Integrations
Works with Docker Compose, Composer, WP-CLI, Drush, Node.js, Redis and mainstream IDEs.
Typical scenarios
WordPress and Drupal development, Laravel projects, teaching environments and multi-service verification.
Limitations
- Docker dependency: higher resource and build cost
- Customisation threshold: overrides need Compose knowledge
- Smaller community: less active than DDEV
- Troubleshooting cost: proxy and network issues are harder to isolate
Use Cases
- WordPress and Drupal work (★★★★☆): recipe coverage is complete
- Multi-service verification (★★★★☆): declarative stacking is flexible
- Team environment alignment (★★★★☆): config travels with the repo
- Minimal footprint needs (★★★☆☆): native environments use fewer resources
Pricing
| Item | Price | Notes |
|---|---|---|
| Lando itself | $0 | MIT open source, commercial use allowed |
| Docker Desktop | Free tier available | Large enterprises should review licensing |
| Commercial support | Community and sponsors | Help available through community channels |
FAQ
Should I choose Lando or DDEV?
Teams focused on WordPress or Drupal can start quickly with Lando recipes; DDEV is steadier for documentation quality and cross-framework consistency.
Can I define custom services?
Yes, override the services section or reference Compose files to extend the stack.
Is HTTPS supported?
Yes, Lando generates local certificates that can be trusted to enable HTTPS.
How does it run in CI?
Install Lando in CI and run lando start plus test commands, with Docker available beforehand.
Code Examples
# .lando.yml
name: demo
recipe: wordpress
config:
php: "8.3"
via: nginx
database: mariadb:10.11
webroot: web
services:
appserver:
overrides:
environment:
WP_ENV: local
tooling:
wp:
service: appserver
cmd: wp
# Start the environment and use wrapped commands
lando start
lando wp plugin list
lando info
lando stop
Community & Resources
- Website: https://lando.dev/
- Source repository: https://github.com/lando/lando
- Documentation: https://docs.lando.dev/
Articles
- 01 GitLab CI/CD Best Practices: From Beginner to Production-Grade Pipelines 07-18
- 02 Prometheus Monitoring System Setup: From Metric Collection to Alert Notifications 07-18
- 03 Ansible Automation Ops Guide: From Configuration Management to Application Deployment 07-18
- 04 Docker Beginner Tutorial: From Installation to Containerized Web Deployment 07-18
- 05 API Integration Guide: REST vs GraphQL Comparison and Selection 07-18
- 06 GitHub Actions CI/CD Tutorial: Automated Build, Test, and Deployment 07-18
- 07 Docker Compose Multi-Container Deployment: Building Complete Application Orchestration 07-18
- 08 Kubernetes Deployment Guide for Beginners: Building a K8s Cluster from Scratch 07-18
- 09 Best VS Code Extensions 2026: Boost Your Development Productivity 07-18
- 10 Frontend Toolchain 2026: Vite / Next.js / Tailwind CSS Ecosystem 07-18