The Deployer documentation
Creating & deploying a project

Choosing an architecture (and its cost)

Now comes a fun decision: where and how your app will actually run. In The Deployer, an architecture is the setup that hosts your app — the kind of computers it runs on, plus the supporting pieces like a database or a content delivery network. You don't design this yourself. An AI called the Architect proposes a few ready-made options, each with a monthly price tag, and you simply pick one.

What "architecture" means here

Every app has to run somewhere. That "somewhere" can take different shapes:

  • VM-based — your app runs on one or more servers (rented cloud computers you control) that stay on around the clock. Flexible and familiar.
  • Managed / serverless — the cloud provider runs your app for you on shared, auto-scaling infrastructure (like Cloud Run, App Runner, or a static website host). Often cheaper and lower-maintenance for smaller apps.
  • Managed Kubernetes — a heavier-duty setup for apps that need to scale up significantly.

You don't need to know the differences in depth — each option explains itself in plain language.

Options tailored to your app

The Architect reads what the scan found and designs options that genuinely fit your stack and chosen cloud — not a one-size-fits-all template. A static website might be offered a low-cost CDN host; a busy backend might be offered a serverless container or a small server. You'll typically see a handful of options arranged from hobby (smallest, cheapest) up through startup, growth, and scale. One may carry a ★ Recommended badge.

Reading the monthly cost

Each option shows an estimated monthly cost as a range (for example, $12–20/month) and a one-line note on who it's best for. This is your own cloud provider's bill — The Deployer doesn't add a markup.

Click Cost breakdown & trade-offs on any option to expand the full details:

  • Cost breakdown — an itemised list (server, database, etc.) with a dollar figure for each, so you can see where the money goes.
  • Trade-offs — the honest downsides of that choice.
  • Assumptions — the usage the estimate is based on (so you know what would change the price).

Costs are estimates, not guarantees — actual charges depend on real usage, and they come straight from your own cloud provider. See costs & billing.

Picking one

  1. Compare the options and expand any you're curious about.
  2. Click Choose this on the one you want. It's highlighted as Selected, and you move on to the Workflow step.

Not sure? Start small. The Architect's own advice is to "start where you are today" — you can always move to a bigger architecture later. If none of the options feel right, click Regenerate to have the Architect design a fresh set.

Once you've chosen, continue to the deployment workflow.