The deployment workflow
Before anything is built, The Deployer shows you a map of everything it's going to do — the whole deployment laid out as a visual diagram of connected boxes. This is the Workflow step. It's a preview and a chance to fine-tune, not a place where anything happens yet.
What you're looking at
The Workflow tab shows your deployment pipeline as a node-graph: each box (a node) is one piece of the process, and the lines between them show how they connect. It reflects the architecture you chose, so every project's map looks a little different. You can drag the boxes to rearrange them and drag the empty space to pan around — purely for your own clarity.
What the nodes are
Nodes are grouped by what they do. You'll typically see some of these:
| Node type | What it does |
|---|---|
| Source | Pulls your code from your repository |
| Build (CI) | Packages your app so it's ready to run |
| Registry | Stores the packaged app |
| Deploy | Puts your app onto its servers or managed hosting |
| App | Your running application |
| Database / Cache | Data storage and speed-up services, if your app needs them |
| Proxy | Routes web traffic to your app and handles HTTPS |
| Monitoring / Logging / Alerts / Uptime | Keeps an eye on your app and warns you if something's wrong |
| Backups | Keeps safe copies of your data |
Reviewing and tweaking
Most people can simply glance at the map and continue — the defaults are sensible. But if you want to adjust something, click any node to open a side panel where you can:
- Read what it does in plain language.
- Swap the implementation — some nodes offer alternatives (for example, a choice between monitoring tools). Pick the one you prefer.
- Remove or restore optional nodes. Nodes marked optional can be removed if you don't want them; click Restore to bring one back.
Some nodes are marked mandatory with a small lock — these can't be removed because your app couldn't deploy or stay reachable without them.
There's also a chat panel right here if you'd like to ask questions or request changes to the pipeline in plain English.
It's a preview of Launch
Nothing in the Workflow step creates resources or runs anything — it's the blueprint. When you're happy with the map, it becomes the exact plan that the Launch step will carry out, step by step. Think of it as reviewing the recipe before you start cooking.
When you're ready, click Continue to domains to (optionally) connect a custom domain, or continue on to launch.