Get started

YOUR STACK. CLEAR DEFAULTS.

Stacks &presets

Managed means Dwell owns the integration contract: version profiles, compatibility, scaffolding, runtime integration, tests and maintenance. Custom supplies the generic local environment; you own the application and framework.

Get startedDocumentation

Managed backend & Custom PHP

Current backend types are PHP-based. Framework and PHP runtime are selected separately; Dwell validates their compatibility.

Managed frontend & Custom

Managed frontends are set up with npm. Their Node requirements can exceed those of the Dwell CLI.

What does “Custom” mean?

Not managed does not mean unusable. Joomla may fit Custom PHP; Next.js, Nuxt and Angular may fit Custom Frontend. These are examples, not officially tested framework integrations. You maintain installation, dependencies, versions and application configuration. The frontend command must honor HOST=127.0.0.1 and the allocated PORT.

A version line is not a patch version.

Version lines and defaults match the reviewed Dwell catalog. A scaffold pin is not always the installed framework patch. Preserve lockfiles; existing applications are not automatically upgraded.

Check versions in your own checkoutdwell versions list

Stack documentation on GitHub

Why only a few Managed stacks?

A new stack needs relevant demand, a clear runtime model, a fit within the existing architecture, sustainable long-term maintenance and a reproducibly testable support contract. Popularity alone is insufficient.

Read the Stack Policy

dwell versions list

See the versions on offer.

Your Dwell installation’s catalog shows version lines, pins, defaults, Dwell lifecycle, upstream support status and verification evidence. New upstream releases are not offered automatically.