Tokaido

Tokaido is a free, open-source Docker environment built for local Drupal development. It is a strong fit for Drupal teams that want to share a project setup, but less suitable when local databases must survive restarts or when a workflow depends on full multisite tooling.

Overview

Tokaido runs services such as PHP, Nginx, and MySQL in Docker containers, with optional helpers including Solr, Memcache, Mailhog, and Adminer. The tok up command starts an environment and configures HTTPS for local development, bringing the core stack together without asking each contributor to assemble those services independently.

Settings can live in .tok/config.yml within the project’s Git repository. That gives teammates a shared configuration alongside the code, a useful advantage for Drupal projects where consistency matters. The environment also provides an SSH endpoint with tools such as Drush, Composer, Gulp, Yarn, and Npm. Tokaido and its Docker containers are described as open source and can be forked and modified.

Key features

Shared project environment

Keeping settings in the repository makes a common development setup easier to carry between contributors. The stack is Drupal-focused rather than a general-purpose container workspace, so it makes the most sense for teams whose local work is organized around Drupal.

Local workflow and security defaults

HTTPS startup and an SSH endpoint for common Drupal and frontend tools make the environment useful for routine development without relying on a separate local toolchain for every task. Tokaido also says its defaults include headers such as X-Frame-Options, X-XSS-Protection, and Referrer-Policy. These are sensible defaults, though they do not remove the need for developers to assess their own application security.

Ephemeral data and multisite gaps

The database resets when the environment restarts, and files stored outside /tokaido/site are lost. That is a meaningful constraint for developers who expect local state to persist between sessions; work that needs durable data requires a workflow that accounts for these resets. Drupal multisite is supported, but tok snapshot and tok test do not understand multisite databases, so those commands are not dependable substitutes for multisite-aware workflows.

Pricing

Tokaido’s sole listed plan, Tokaido, costs free. It includes an open-source local Drupal development environment that runs with Docker. There are no paid tiers to compare, so readers get the same stated product scope without choosing between feature levels. Its free price does not change the practical costs of running Docker or the setup demands of each platform.

Platforms

Tokaido supports Linux, macOS, and Windows. Windows is explicitly beta and experimental, and the guide requires Windows 10 Pro or Enterprise. Running docker-compose exec on Windows also requires the winpty prefix for TTY compatibility, making it a less polished choice for Windows-first teams.

Linux setup requires Docker, Docker Compose, Unison, ocaml, and fsmonitor, with some manual setup. Installation guidance lists Drupal 7 or Drupal 8, PHP 7.1, and a Git repository as requirements; unsupported project layouts may not receive support. Teams should check those requirements against their existing application before committing to Tokaido.

Who it's for

Tokaido is best for Drupal developers and teams who want Docker-based local services, HTTPS startup, and project configuration shared through Git. It also suits contributors who can work within its ephemeral data model and platform-specific setup. It is a weaker fit for Windows users who need a stable, straightforward workflow, projects reliant on persistent local databases, or multisite teams that depend on snapshot and test commands.

Pros and cons

• Pro: Configuration travels with the project. Storing settings in .tok/config.yml lets teammates use a shared setup from the Git repository.
• Pro: Drupal tools and helper services are built into the workflow. The SSH endpoint includes common command-line tools, while optional services extend the local stack.
• Pro: Open source and free. The environment and containers can be forked and modified without a paid plan.
• Con: Local state is temporary. The database resets on restart, and files outside /tokaido/site are lost.
• Con: Multisite commands have gaps. Snapshot and test workflows do not account for multisite databases.
• Con: Platform setup is uneven. Windows remains experimental, while Linux requires several dependencies and manual setup.

Alternatives

For broader container workflows, compare container development environments. Docker Desktop is a better direction for readers who want a general Docker desktop product with a free Personal plan and a paid Pro tier at $9 a month. Kool may suit teams looking for a managed-cloud option or a tightly capped free BYOC setup, which includes one cluster, node, environment, and app.

Garden is worth considering for development environments centered on build minutes, cache hits, and cache retention, with an Enterprise tier that adds secrets management, RBAC, and self-hosting. kind is another free, open-source option for readers seeking a Kubernetes-focused tool. Testcontainers Desktop fits individual developers who can work within 300 minutes of cloud runtime per month on its free plan.

Tilt is a free, Apache-2.0-licensed open-source alternative. Coasts is another free local open-source option. Colima is a free MIT-licensed container runtime option for macOS and Linux.

Verdict

Choose Tokaido if your team develops Drupal and wants a shared Docker configuration, HTTPS startup, and familiar development tools at no software cost. Its project-centered setup is compelling for that audience, but persistent local data, multisite command coverage, and platform friction are real trade-offs. Look elsewhere if those constraints conflict with the way your team develops.