Object Storage, Agent Deployments, and Policy Automation

added

June 8, 2026

Deployments now support object storage across cloud providers, Hyphen Agent can inspect and run project environment deployments from chat, and organizations can control stale feature flag cleanup with recurring Agent task policies.

Object Storage for Deployments

You can now add object storage to the deployment settings of your project environments. During deployment setup, choose an object storage provider, optionally provide an existing bucket or container name, and Hyphen will include object storage as part of the deployment resource model.

Easily switch providers by modifying the project environment deployment settings

Object storage support includes:

AWS, Azure, and Google Cloud targets - Configure object storage against connected AWS, Azure, or Google Cloud integrations.
Easy provider switching - Change the object storage provider or bucket in deployment settings, and Hyphen will queue the new storage target on the next deployment.
Optional bucket naming - Use an existing bucket or container name, or let Hyphen derive one from the project and environment.
Deployment resource visibility - Object storage now appears in the project environment resource diagram alongside apps, targets, and ingress resources.
Automatic credential injection - When object storage is configured for a deployment, Hyphen creates the necessary cloud resources and injects credentials into your application, with no manual bucket creation or credential management required.
Automatic cleanup - Buckets and storage resources that are no longer used by deployment settings are marked for cleanup automatically.
Drift detection - Deployment settings drift alerts now include object storage differences between current settings and the latest deployment run.

Learn more in the Object Storage in Deploy documentation.

Agent Deployment Controls

Tell Hyphen Agent to deploy your project environment from Slack

Hyphen Agent can now answer deployment readiness questions and help run deployments from chat. Ask what is configured for a project environment, whether it is ready to deploy, which apps and cloud targets are included, or what the latest non-preview run looked like.

You can also ask the agent to run a configured deployment. The agent checks readiness first, prepares the deployment or preview deployment, and asks for confirmation before creating the deployment run. If you do not specify builds, Hyphen defaults to the latest build for normal deployments and the latest preview build for preview deployments.

Follow-up deployment requests now preserve the prior deployment target, including preview deployments, so requests like "deploy again" can use the last confirmed context without restating the project and environment.

Stale Feature Flag Cleanup Policies

Set your organization's stale feature flag policy from the organization settings

Stale feature flag cleanup is now managed through organization Agent task policies. Admins can enable or disable the cleanup policy and choose how often it runs:

Manual only
Every day
Every week
Every month
Every quarter

Teams can still manually ask Hyphen Agent to clean up stale feature flags at any time, including when the organization policy is set to manual only.

Hyphen distributes scheduled run times across the hour so recurring cleanup work does not pile up at the same minute for every organization.

Deployment UX Improvements

Live deployment run updates - Deployment run socket events now refresh project environment deployment views as runs change.
Queued run display - Queued deployment runs now show queued... instead of rendering an invalid date before the run has a start time.
Object storage form polish - Object storage provider dropdowns and deployment-resource flows now handle changing target selections more reliably.

Things to Know

Agent-run deployments still require confirmation. The agent will not create a deployment run until the confirmation step is approved.
Readiness blockers still apply. If the configured deployment is missing required settings or cloud resources, the agent reports the blockers instead of starting the run.
Object storage requires a connected cloud provider. The deployment form only enables object storage when a compatible cloud integration is available for the environment.
Provider changes are handled as deployment changes. Switching object storage providers takes effect through the next deployment run, and the old storage target is cleaned up when it is no longer used.
Policy controls require policy permissions. Users without policy management access can view the current stale feature flag cleanup policy but cannot change it. Create feature flags from the Toggle quickstart before using stale feature flag cleanup policies.

Under the Hood

nfabric orchestration is the provisioning layer Hyphen uses to create, adopt, and ensure resources across cloud providers. This release wires object storage provisioning through nfabric-backed connection workflows.
Object storage credentials are packaged into a Hyphen-managed HYPHEN_OBJECT_STORAGE_CONFIG environment variable for deployed cloud-native containers.
Unused storage cleanup is scheduled through the deployment cleanup step when storage settings archive a bucket or provider target.
Deployment Agent tools now read project environment deployment settings and prepare confirmed deployment runs through managed chat input requests.
Agent task policies reconcile recurring stale feature flag cleanup schedules through Temporal.