Pantheon Multidev

Pantheon Multidev is a feature of the Pantheon hosting platform that creates an ephemeral, fully-isolated environment per git branch — letting engineering teams preview feature branches, review code changes, and run QA against production-like infrastructure without touching dev, test, or live.

How it fits into a real engineering workflow

• Engineer opens a pull request; CI provisions a Multidev with that branch’s code.
• The PR description links to the live Multidev URL for reviewers, QA, and stakeholders.
• Sign-off happens against the same WordPress version, database content, and Pantheon edge configuration that runs production.
• Merging deploys to dev → test → live via Pantheon’s documented promotion model.

Why mission-driven orgs find it useful

Nonprofits and B Corps typically run lean engineering teams with non-technical reviewers — a comms director, a development director, a board member. Multidev lets non-engineers preview substantive changes on a real URL before code lands in dev or test. That collapses the review cycle from “explain in a meeting” to “open this link.”

Trade-offs

• Plan-level limit on concurrent Multidev environments; not every branch can hold one.
• Database content needs to be cloned in from live (or seeded) before each Multidev is useful for review.
• Editorial changes made in a Multidev don’t merge back to live the way code does — content stays in whichever DB it was created on.