Changelog
What has actually shipped, in plain language. No version theatre — just the real build, dated.
A deployment-confidence read on every plan
Each result now leads with a computed confidence read — architecture, IaC completeness, and deployability, plus how much manual work is left — derived from the run's own validation checks, not guessed.
Least-privilege, secret-safe infrastructure code
Generated infrastructure code is now scoped to least-privilege access — no blanket Action or Resource wildcards — with secrets referenced from a managed secret store rather than inlined, checked before the plan reaches you.
Plans right-sized to your scale and budget
The architecture now scales to your stated scale, traffic, and budget — a small app gets a lean serverless design, a larger one gets the redundant stack — and every plan carries a monthly cost estimate plus a cheaper alternative, and says plainly when the honest cost is over budget.
A public page on why you can trust the plans
Added /trust: exactly how each plan is grounded, cited, validated, consistency-checked, and made reproducible — with a real, labeled example from an actual run.
Estimated energy & compute footprint
Every result now shows an estimated energy and CO₂e footprint for the compute that produced it, with the formula and sources shown — an estimate for transparency, clearly labeled, never a bare number.
Infrastructure code, generated section by section
Reworked IaC generation to name every resource up front, generate bounded sections, and assemble and consistency-check them — removing the old size ceiling that could truncate large templates.
A short survey after each plan
Added a quick 'how did we do?' survey so real feedback — did it help, did you deploy it — shapes what gets built next.
Sessions that survive a refresh
Your in-progress or most recent result now persists across a refresh or navigation, with a clear countdown to your next free run.
Validation checklist + reproducibility manifest
Each result ships a visible ✓ / ✗ quality and security checklist, and a downloadable manifest (your inputs, the docs-corpus version, model IDs, and pinned provider versions).
Grounded across AWS, Azure, and Google Cloud
Plans are grounded in the target cloud's own documentation, with inline [Source N] citations, for all three major clouds — not a lowest-common-denominator template.
infra god goes live
The first grounded, cited, cloud-agnostic deployment guide: describe your app and get an architecture, infrastructure-as-code, and step-by-step commands.