Tokaido
tokaido.io
- Free plan
- Windows
- macOS
- Linux
What Tokaido is
Tokaido is a free, open-source tool for creating local Drupal development environments with Docker and its `tok` command-line interface. Its environments run components such as PHP, Nginx, and MySQL in containers, with optional services including Solr, Memcache, Mailhog, and Adminer. The `tok up` command starts an environment and sets up HTTPS for local development. Project settings can be kept in `.tok/config.yml` in the Git repository so teammates can share a configuration. An SSH endpoint provides access to tools such as Drush, Composer, Gulp, Yarn, and Npm. Tokaido lists Linux, macOS, and Windows support, though its Windows build is described as beta and experimental. Its local environment is ephemeral: the database resets when it restarts, and files outside `/tokaido/site` are lost. Drupal multisite is supported, but `tok snapshot` and `tok test` do not account for multisite databases. Windows users need the `winpty` prefix for `docker-compose exec`. The maker says Tokaido and its Docker containers can be forked and modified.
Who it suits
Tokaido suits Drupal developers who want a shared, Docker-based local environment and command-line tooling. It may fit teams that keep project configuration in Git and can account for its temporary local data behavior.
Good to know, and what to watch
- Free and open source.
- Runs Drupal components in Docker containers.
- Shared settings can live in the project Git repository.
- Includes an SSH endpoint for developer tools.
- Supports Linux, macOS, and Windows.
- Database resets when the environment restarts.
- Files outside `/tokaido/site` are lost.
- Windows build is beta and experimental.
- Multisite databases are not handled by `tok snapshot` or `tok test`.
Plans
Every plan and priceTokaido
Free plan
Getting started
- Install Docker and Docker Compose
- Meet the listed Drupal, PHP, and Git project requirements
- Install the Tokaido command-line tool
- Place the project configuration in `.tok/config.yml`
- Run `tok up` to start the environment and set up HTTPS
- Use the SSH endpoint for Drupal and development tools
Limits to check
The local environment is ephemeral: restarting resets its database, and files outside `/tokaido/site` disappear. On Windows, the build is experimental and `docker-compose exec` requires the `winpty` prefix; multisite databases are not handled by `tok snapshot` or `tok test`.
The Club's review
Tokaido is a free, open-source Docker environment focused on local Drupal work. It is strongest for Drupal teams that want one versioned setup for every contributor, while its disposable local data and uneven Windows support make it unsuitable for projects that need durable local databases or a polished cross-platform workflow.
Overview
Tokaido assembles PHP, Nginx and MySQL containers into a local Drupal environment, with optional Solr, Memcache, Mailhog and Adminer services. Running tok up starts the stack and configures HTTPS, removing much of the repeated service wiring from a Drupal project.
Configuration is stored in .tok/config.yml within the project Git repository. That turns environment settings into shared project code, so teammates can work from the same baseline rather than reproducing setup manually. The project is fully open source, and its Docker containers can be forked and changed. Ironstar builds and primarily maintains it.
Key features
Drupal-focused container stack
The SSH endpoint provides Drush, Composer, Gulp, Yarn and Npm, covering common Drupal and frontend command-line work inside the environment. This is a practical advantage for teams that want consistent tooling alongside consistent services. Tokaido also advertises security defaults including X-Frame-Options, X-XSS-Protection and Referrer-Policy headers.
Team configuration
Keeping settings in Git makes onboarding and project handoffs more predictable. Drupal multisite is supported, but tok snapshot and tok test do not understand multisite databases, so those commands cannot be relied on for complete multisite workflows.
Ephemeral storage
The central limitation is data behavior: the local database resets when the environment restarts, and files outside /tokaido/site are lost. That can be useful for deliberately clean, repeatable environments, but it rules out workflows that depend on retaining local content or database changes between sessions.
Telemetry and support
Usage reporting is opt-in. When enabled, Tokaido says it does not sell or license the data, and its privacy policy says telemetry API data does not retain IP addresses. Documentation, a Help & Support page and GitHub pull-request issue handling provide the stated support routes.
Pricing
| Plan | Price | Includes |
|---|---|---|
| Tokaido | Free | Open-source local Drupal development environment; runs with Docker |
There are no paid tiers, seat charges or published usage quotas. The free plan fits individual Drupal developers and teams that can supply Docker and accept the storage model. Its price does not change the operational trade-off: teams needing persistent local state must provide another workflow for that data.
Platforms
Tokaido supports Linux, macOS and Windows. Linux setup requires Docker, Docker Compose, Unison, ocaml and fsmonitor, with some manual configuration. Windows support is beta and experimental, requires Windows 10 Pro or Enterprise, and needs the winpty prefix when running docker-compose exec to handle TTY compatibility. Drupal 7 or Drupal 8, PHP 7.1 and a Git repository are listed requirements; unsupported project layouts may not receive support.
Who it's for
Choose Tokaido when your work is Drupal-centered, your team benefits from committing environment settings with the code, and a Docker-based local stack with built-in command-line tools matches your process. It is also appealing when open-source containers that can be modified matter more than a commercial support contract.
Look elsewhere if local databases must survive restarts, if you rely heavily on multisite snapshot or test commands, or if Windows users need a stable, low-friction installation. Linux users should budget time for the additional dependencies and manual setup.
Pros and cons
- Pro: Project configuration in .tok/config.yml gives a team a shared, version-controlled environment.
- Pro: PHP, Nginx, MySQL and optional Drupal services are bundled in Docker, while tok up handles startup and local HTTPS.
- Pro: The SSH endpoint includes Drush, Composer, Gulp, Yarn and Npm.
- Pro: The stack and containers are open source and forkable.
- Con: Database resets and out-of-site file loss make persistent local development impractical.
- Con: Multisite support does not extend to snapshot and test database awareness.
- Con: Windows remains experimental and requires a TTY workaround.
- Con: Linux installation has several prerequisites and manual steps.
Alternatives
For a broader directory of options, see Container Development Environments.
- Kool is the better fit when you want a freemium tool spanning Linux, macOS, web and Windows, with a free BYOC tier limited to one cluster, node, environment and app, plus a $5.00-per-month managed micro plan.
- OrbStack suits macOS users seeking a personal free tier for containers and Linux machines, with Pro at $8 a month billed annually at $96.
- Docker Desktop is preferable when you need a general Docker and Kubernetes desktop bundle across Linux, macOS, web and Windows; its Personal plan is free and Pro is $9 a month.
- Garden fits teams wanting build-cache controls and an Enterprise option with secrets management, RBAC and self-hosting.
- Devilbox is another free option for Linux, macOS, self-hosted, web and Windows.
- DevPod is a client-only, 100% free and open-source alternative for Linux, macOS and Windows.
- Testcontainers Desktop may suit individual developers who can work within 300 cloud-runtime minutes per month on its free plan.
- DevKinsta is a free-forever choice for local WordPress development on macOS, Windows and Ubuntu.
Verdict
Tokaido is a strong choice for Drupal teams that value a Git-shared Docker setup, integrated Drupal tooling and the ability to modify an open-source stack. Choose something else when persistent local data, dependable multisite automation or mature Windows support is a primary requirement.
The verdict
Tokaido offers a configurable local Drupal setup with Docker and shared project settings. Its ephemeral data behavior and experimental Windows build are important constraints to weigh before adopting it.
Questions people ask
Is Tokaido free and open source?
Yes. The Tokaido plan is free, and the maker describes Tokaido and its Docker containers as fully open source.
Which desktop systems are supported?
Tokaido supports macOS, Linux, and Windows. The Windows build is described as beta and experimental.
What does it run in Docker?
Its environments can run PHP, Nginx, and MySQL. Optional services include Solr, Memcache, Mailhog, and Adminer.
How is team configuration shared?
Project settings can be stored in `.tok/config.yml` in the project Git repository so teammates use the same configuration.
What happens to local data after a restart?
The database resets when the environment restarts, and files outside `/tokaido/site` are lost.
Who maintains Tokaido?
Tokaido is built and primarily maintained by Ironstar. The project was founded in 2016 and is headquartered in Melbourne, Australia.
What the maker publishes
- Configuration
- Project settings can be stored in `.tok/config.yml` and shared with teammates through the Git repository. source
- Core stack
- Its environments run components such as PHP, Nginx, and MySQL in Docker containers. source
- Data persistence
- The introduction warns that the local environment is ephemeral: its database resets on restart, and files outside `/tokaido/site` are lost. source
- Data persistence
- The usage guide says the database survives `tok stop` and `tok up`, while destroying the environment also preserves the MySQL database. source
- Developer tools
- The environment includes an SSH endpoint for running tools such as Drush, Composer, and Gulp. source
- Drupal multisite
- Drupal multisite is supported, but the documentation says `tok snapshot` and `tok test` are not aware of multisite databases. source
- Drupal requirements
- The installation guide lists Drupal 7 or Drupal 8, PHP 7.1, and a Git repository as requirements; it says unsupported project layouts may not receive support. source
- Founded
- 2016 source
- Headquarters
- Melbourne, Australia source
- Linux setup
- Linux installation requires Docker, Docker Compose, Unison, ocaml, and fsmonitor, with some manual setup described. source
- Maintainer
- Tokaido is built and primarily maintained by Ironstar. source
- Open source
- The maker describes Tokaido and its Docker containers as fully open source and says they can be forked and modified. source
- Optional services
- Optional helper services include Solr, Memcache, and Mailhog; the product site also names Adminer. source
- Optional services
- The configuration can enable services including Solr, Adminer, and Mailhog. source
- Other tools
- The SSH environment includes tools such as Drush, Yarn, and Npm. source
- Platforms
- The documentation provides installation instructions for macOS, Linux, and Windows; it describes the Windows build as experimental. source
- Purpose
- Tokaido is an open source tool for creating local Drupal development environments with Docker and its `tok` command line interface. source
- Purpose
- Tokaido is a command-line tool and collection of Docker containers for running local Drupal development environments. source
- Security defaults
- Tokaido says its defaults include security headers such as X-Frame-Options, X-XSS-Protection, and Referrer-Policy. source
- Security defaults
- The documentation says Tokaido sets security-related headers including HSTS, Referrer-Policy, and X-Frame-Options by default. source
- Startup
- The `tok up` command starts an environment and sets up HTTPS for local development. source
- Startup
- A Drupal environment can be started from its Git repository with the `tok up` command. source
- Support
- The site links to documentation and a Help & Support page, and the documentation invites users to submit issues as GitHub pull requests. source
- Support
- The FAQ invites users to contact the maintainers when documentation does not resolve an issue. source
Checked against the maker's pages on 8 Oct 2026.