Deployment-filter explorer
Paste a Blueprint and push details to see which services pass the declared deployment filters and why.
This uses declared settings and creation defaults from a pinned Bex source revision. Existing service settings, deploy-request overrides, repository matching, billing, capacity and build success are outside this check.
rootDir and buildFilter inspect the changed paths independently, so different files can satisfy them. Missing changed-path data passes both path gates. A literal rootDir of “.” is not the same as omitting it.
These tools run entirely in your browser. Nothing you paste or drop is uploaded, stored, or sent to analytics.
Git services need an explicit repo for this check. The whole Blueprint is not validated. Ctrl/⌘ + Enter checks immediately.
One added, modified or removed path per line. Leave this empty only to model a webhook with no changed-path data; it passes the path gates.
Use the branch name, such as main, without refs/heads/. An empty value models a missing branch and passes the branch gate.
The head commit is checked for [skip render] and [render skip], ignoring letter case.
Limits: 256 KiB Blueprint, 100 services, 2,000 changed paths within 128 KiB, 64 KiB commit message and bounded matching work. Oversized or unsupported input stays unresolved.
Choose a scenario or paste a Blueprint to explore each service’s deployment gates.