Every box on the diagram has a reason.
Services are chosen from the cloud's own catalog for the workload Anneal measured, drawn with the official icons and numbered in the order requests flow. Each one carries its price and the decision behind it.
Anneal reads your code and your company’s rules, measures what your app really needs, picks services from live price lists and deploys them. Then it keeps watching — when traffic, prices or your code change, it updates the architecture with you.
Designs and prices on
Most tools design for a blank page. Anneal starts from the way your company already works — and treats your policies as requirements, not suggestions.
Ask in plain words. Anneal tests and measures your app, chooses and prices every service, draws and reviews the design, writes the infrastructure and deploys it — and you watch every step.
Services are chosen from the cloud's own catalog for the workload Anneal measured, drawn with the official icons and numbered in the order requests flow. Each one carries its price and the decision behind it.

Each cost line shows the unit price, the quantity behind it and the exact price-list entry it came from. Drag the assumptions to see how the bill grows, and compare the plan with what the cloud actually billed.

The deploy runbook lives in your own cloud account. Checks run by themselves, every change waits for you to press Run, and the assistant beside it reads each result and fixes a step that failed.
How deployment works →
Your traffic changes, prices change, your team ships features. Anneal watches the live system and your code and keeps the architecture right — with you approving every change.

Anneal knows which files changed since each decision was made, and re-runs only the work they affect.
Each step leaves evidence you can open, so the next pass starts from what is already known — and only redoes what changed.
Reads your policies, governance documents, existing infrastructure and past architectures.
Reads the code, runs your tests and the real UI, and load-tests the route people actually use.
Picks services from the live catalog for what was measured, within your rules, priced line by line.
Draws the architecture, reviews it independently and writes Terraform that validates.
From your machine in your account, one approved step at a time — or as a pull request for your CI.
Follows the live system and your code, and brings the next change back for you to approve. Then again.
Files, commands, tests and the conversation stay on your computer. The service that thinks for Anneal keeps nothing.
Keys and passwords are replaced before anything leaves your machine — <REDACTED_DB_URL> — and filled back in only where they're used.
Bring your own model key. Anneal never applies, pushes or deploys on its own: changes to your cloud wait for you.
Open a project, ask one question, and get an architecture you can defend — today and after every release.