dqxEvery project, running locally on Docker

Declare a project once. dqx builds its stack, serves it beside every other project on trusted https, shows the whole machine in a dashboard, gives each task - or each agent - its own copy, and has Claude review its pull requests.

What dqx is

Install it

One declaration, a generated stack

A project declares its sites, services, database and PHP version in .dq/config.yml, and dqx generates the docker stack from it. Disposable, and identical for everyone.

How docker is generated

Every project at once

A shared reverse proxy serves every project on 80 and 443 together, each on its own domain with a certificate your browser already trusts.

The daily commands

The whole machine in a dashboard

dqx dashboard shows every project - what runs, what is broken, how much memory it holds - and starts, stops, tests, copies and configures it with a click.

The dashboard

A copy per task

dqx clone and dqx agent-env put a second copy of a project beside the first, on its own URLs and its own database, while the original keeps running.

Copies and environments

Built for agents

An MCP server tells an AI agent where code lives, what to run and where the database is, so it asks instead of guessing - in the original or in its own copy.

AI tooling

Pull requests reviewed with Claude

dqx review has Claude read only the changed lines of a Bitbucket or GitHub pull request, in a sandbox with no shell. You pick the findings, edit them, and post them under your own name - from a terminal or a tab in the dashboard.

Reviewing a pull request

Next to Herd and Valet

dqx serves its projects on .dqx domains and can move its router to 127.0.0.2 with dqx loopback, so Herd or Valet keep 80 and 443 on 127.0.0.1 and both run at once.

dqx next to Herd, Valet or Sail

Tests and answers in the stack

dqx e2e runs Playwright against the real local site over https. dqx doctor says what is wrong and why - a schema the app cannot reach, a worker restarting in a loop.

When something is wrong

Every project on this machine, in a browser

The dqx dashboard in demo mode: seven projects, the two running ones on top with their sites, branches, databases, services and a pull request count — dqx dashboard: what exists, what is running, what is wrong, and the two buttons that matter.

What the dashboard shows · Using it · Changing a project from it · Reviewing pull requests in it

Other stacks

dqx adopts and runs projects on DDEV, Lerd and Herd as well, and dqx switch moves a project between them without touching its repository. The dashboard, dqx clone and agent environments are docker only, so a project pinned elsewhere gets the CLI and not those.


DDEV	when page speed hurts	Fastest page render of the four, and the slowest to start and stop - 8.4× docker's, felt hardest on projects with several sites
Lerd	on Linux	By far the lightest - 1.9 GB where DDEV takes 9.6 for the same projects - and the slowest to start them
Herd	fastest, least isolated	PHP on the host: nothing to beat it for one application, and no answer when two need different extensions

Compare them side by side · How to switch

Written at Dolphiq for our own fleet and for partner teams using dqx. The examples are our own container images and domains, and both are public. Start here · If you are not at Dolphiq