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.

Developer Tools United States 2026.11.19
4pts

Detailed Notes

Pros 5 items

Declares services, tooling and proxying in 1 .lando.yml so teammates just run lando start
Ships 20+ recipes covering LAMP, LEMP, WordPress, Drupal, Laravel and Node
Provides tooling that wraps frequent commands as lando subcommands, replacing 1 class of docker exec calls
Combines 3+ database and cache services freely and mounts custom service definitions
Handles 2 setup steps - local domains and HTTPS certificates - avoiding manual hosts edits

Cons 4 items

Requires Docker, costing more resources and first-build time than native stacks
Custom services demand Docker Compose knowledge and Lando overrides
Community activity is lower than DDEV, with some recipes updating slowly
Complex networking and proxy scenarios are costly to troubleshoot

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

Visit Lando Website → https://lando.dev/
Visit Website ↗