These steps assume installation and setup are
complete.
Start the stack
Missing images are built automatically. Force a rebuild after source or
dependency changes:Open the configured dashboard URL, which defaults to:On the first successful start, the CLI displays the initial administrator
credentials after confirming that the account was persisted. Change the
password after signing in.A fresh deployment opens on the campaigns list with no campaigns yet. Verify the deployment
Do not prepare a campaign until the required control-plane services are
healthy and doctor reports no failures. Prepare campaign resources
Create and review the reusable resources in this order:
- target list;
- landing page;
- for a Complete campaign, an email template and SMTP profile;
- optional plugins and modules;
- campaign.
Choose Complete for a scheduled email-delivery window. Choose Standalone for
an immediate, non-scheduled campaign without email or SMTP delivery resources.Use only approved test recipients and infrastructure. The
campaign guide explains the wizard and lifecycle. Stop the complete runtime
This is a terminal shutdown: active, paused, and scheduled campaigns are marked
completed, and all app-owned campaign, browser, and egress containers are
removed. Running up later starts only the control plane; it does not resume
those campaigns.
Last modified on August 28, 2026