Deployment Drift Alerts and Smarter Optimizer Controls

Hyphen now tells you when your deployment settings have drifted from what's actually running, before you waste a run. The optimizer also gets smarter guardrails: it can now recommend scaling above your SLA floor and adjust your instance bucket, while still protecting you from going below it.

Deployment Settings Drift Detection

When you or one of your teammates changes your deployment configuration after the last deployment run, Hyphen now surfaces a drift alert directly on the project overview, above the resource diagram for the selected environment.

The alert shows exactly which apps changed and exactly what changed, the value from the last run snapshot alongside your current setting for every editable dimension: targets, availability, scale, traffic regions, hostname, domain, and path. A link to the latest scoped run is included so you can review or re-run immediately. If everything is already in sync, the alert stays out of your way.

Optimizer: Scale Above Your SLA Floor

The Agent optimizer tool can now recommend scaling your traffic regions above your SLA floor and adjust your instance bucket when the data warrants it.

Previously the optimizer was bound to your original SLA envelope. Now it has a single source of truth for min/max region bounds and instance bucket constraints. The optimizer still cannot go below your SLA floor — that boundary is enforced in the tool layer and cannot be overridden. Any recommendation that touches scale is automatically flagged for your approval before anything changes.

AWS Integration Without SSO

Connecting an AWS account no longer requires SSO to be configured. The integration flow now accepts non-SSO credentials and handles misconfigurations with clear, specific error messages rather than generic failures.

Things to Know

• Drift alerts are informational. Seeing a drift alert doesn't mean something is broken — it means your current settings differ from the last run snapshot. You decide whether to re-run the optimizer or leave the configuration as-is.
• Availability is user-owned. The optimizer cannot change your SLA availability tier. That boundary remains exclusively yours to set.
• Scaling above the SLA floor requires your approval. Any optimizer recommendation that touches scale is automatically held for review before anything is applied. It will never self-approve.
• Existing SSO-based AWS connections are unaffected. Removing the SSO requirement only changes what's needed to create a new connection — existing integrations continue to work as before.