Get started

An honest assessment

Pros & cons

Dwell brings local infrastructure together, but it will not suit every workflow. These requirements and limitations can help you decide whether it will reduce setup work for your project.

Get startedDocumentation

A good fit if …

Dwell can help when these needs match the way you work.

  • you work with Docker

    You already use Docker or want to run your local services in containers. A running Docker environment is required.

  • you want local domains and HTTPS

    You want .localhost addresses and a shared gateway. Optional HTTPS requires mkcert, available ports and certificate trust.

  • you want to repeat and share setups

    You want to describe services and settings in the project so others can understand and rebuild the setup.

  • you want to test on other devices

    You occasionally need local-network access, for example from a phone. Availability also depends on your network.

  • you are comfortable with the command line

    You want to control the environment through commands and are willing to understand and maintain its configuration.

  • you want strong defaults and a maintained catalog

    Clear defaults, fewer Managed variants and controlled stack support keep the standard path and long-term maintenance contract small and explicit.

Less suitable if …

In these situations, check whether another approach better meets your requirements.

  • you expect a complete graphical interface

    Dwell is controlled through the command line and configuration files. A comprehensive GUI is not part of the described feature set.

  • you want to run a production environment

    Dwell is intended for local development. Deployment, public access and secure production operation are separate responsibilities.

  • you only need a small, one-off setup

    For a single temporary project, a direct start without additional infrastructure may be simpler. Dwell has its own prerequisites.

  • you do not want to use Docker

    Dwell is built on Docker. If containers do not suit your workflow or working environment, that foundation will not fit either.

  • you expect a ready-made preset for every framework

    Not managed does not mean unusable. Custom PHP and Custom Frontend provide the generic environment; you own the application, framework versions and dependencies.

  • you want one tool for all development tasks

    Dwell organizes local infrastructure. It does not replace your editor, framework, application logic, tests or debugging.

dwell plan up

Check first, then start.

Review planned startup operations, requirements and detectable blockers. The plan itself changes no project files and starts no services; it does not guarantee a successful later start.