hyphen
Hyphen Deploy

You define the requirements. Deploy builds everything else.

Skip the Dockerfiles, Helm charts, and Terraform. Push your repo and get secure, best-practice infrastructure on AWS, Azure, or Google Cloud, verified and reversible, every run.

Get startedView docs
zero-config builds · secure by default · rollback on failure
Dashboard › AcmeShopAcmeShopproductionSettingsDeployCloudflareshop.acme.comstorefrontGoogle CloudNA1Microsoft AzureNA1Google CloudObject StorageAPPAVAILABILITYSCALETARGETstorefront99.000%smallGoogle Cloud · Azurethermapro–––AcmeShop › productionproductionDeployment settingsDEPLOY TOGoogle CloudMicrosoft AzureAmazon Web ServicesAVAILABILITY99%Standard99.9%High99.99%Very High99.999%Mission CriticalTRAFFIC REGIONSNorth AmericaEuropeAsia PacificSouth AmericastorefrontSCALESMMDLGXLHOSTNAMESubdomainshopDomainacme.comPath (optional)e.g. 'my-app/path'shop.acme.comSaveAcmeShop › Deployment runDeploy storefrontrunning◯ 0sPIPELINE STEPS0 / 27Setup NetworkGoogle CloudEnsure cloud workspaceEnsure container registryMicrosoft AzureEnsure cloud workspaceEnsure network groupDeployGoogle Cloud NA1Ensure cloud native containerDeploy container revisionMicrosoft Azure NA1Ensure cloud native containerDeploy container revisionManage Cloud IngressGoogle CloudEnsure production Cloud Load BalancerEnsure storefront PoolEnsure storefront NA1 EndpointAssign storefront Pool EndpointsAssign Cloud Load Balancer PoolsMicrosoft AzureEnsure production Cloud Load BalancerEnsure storefront PoolEnsure storefront NA1 EndpointEnsure shop.acme.com Custom DomainAssign storefront Pool EndpointsAssign Cloud Load Balancer PoolsManage Cross Cloud IngressCloudflareEnsure storefront Google Cloud EndpointEnsure storefront Azure EndpointEnsure storefront PoolEnsure production Cross Cloud Load BalancerAssign storefront Pool EndpointsAssign Cross Cloud Load Balancer PoolsManage DNSCloudflareAssign Cross Cloud Load Balancer DNS recordClean UpLOGS09:22:00 AMRun queued09:22:00 AMGenerating pipeline for deployment run
Deploy to your cloudAWSAzureGoogle Cloud
How it works

Every deployment follows the same path. Connect. Define. Generate. Ship.

  1. 01

    Connect your cloud

    Connect AWS, Azure, or Google Cloud. Deploy creates the container registry and works inside your own accounts.

  2. 02

    Define requirements

    You set the availability target, traffic locations, and expected scale. That’s the whole configuration: you never write or maintain infrastructure code again.

  3. 03

    Deploy generates everything

    It analyzes your repository, generates the buildfile, builds the container image, and provisions infrastructure aligned with security best practices.

  4. 04

    Ship, verify, repeat

    Push to deploy from the CLI or GitHub Actions. Every run is verified, every pull request gets a preview, and you can roll back in one step.

Capabilities

Ship things that used to need a platform team.

Everything between your repo and production, handled for you, the same way on every cloud.

Deployment requirementscheckout-api · productionAvailability target99.95%TrafficN. America + EuropeExpected scale1M req/dayGenerate deployment

Describe the outcome, skip the how. You set availability, traffic location, and scale. Deploy turns that into secure, best-practice infrastructure you never have to write.

Building◯ 1m 04sBuild: checkout-apiAI containerization · no DockerfileAnalyze repository12sGenerate buildfile8sBuild image41sPush to registryrunning

Containerize apps you’ve never containerized. No Dockerfile, no build expertise: Deploy scans your languages and dependencies and produces the image for you.

Deployment targetsOne workflow across providersAmazon ECSconnectedAzure Container AppsconnectedGoogle Cloud Runavailable

Change clouds without rewriting anything. The same requirements run on Amazon ECS, Azure Container Apps, or Google Cloud Run. Your deployment is portable by default.

checkout.acme.comNetworking · productionDNS recordsconfiguredSSL certificateissuedFirewall rulesapplied

Launch with DNS, SSL, and firewalls already done. No tickets, no console digging: Deploy configures them on AWS, Azure, GCP, or Cloudflare as part of the run.

Preview ready◯ 1m 47sPR #512: add gift cardsDeployment preview · checkout-apipr-512.checkout.preview.hyphen.devOwn environment, own secrets, own URL.Expires with retention policy ·3 hours after close

Review every change on a live URL. Each pull request gets its own environment automatically, and it cleans itself up when you’re done.

$ hx deploy production→ building image… done(41s)→ pushing to registry… done(12s)→ provisioning infrastructure… done(58s)→ verifying deployment… done(19s)live at https://checkout.acme.comSame command locally or in any CI.

Ship from the pipeline you already have. One hx command deploys from your laptop, GitHub Actions, or any CI. Nothing new to adopt.

Global load balancingcheckout-api · 2 regionsus-east-152%eu-west-148%Latency-routed · failover automatic

Go global without a networking project. Add regions and Deploy handles the load balancing: traffic routed by latency, failover automatic.

assets-productionObject storage · AWS S3BucketprovisionedAccess for checkout-apiwiredCredentials injected as env vars.

Add storage in a sentence, not a sprint. Deploy provisions object storage with your app and wires the credentials into its environment for you.

Environment: productionENV · end-to-end encryptedDATABASE_URL••••••••STRIPE_SECRET_KEY••••••••REDIS_URL••••••••Pulled at start · never in the image.

Stop shipping secrets by hand. ENV injects end-to-end encrypted variables at runtime, per environment, never baked into the image.

Complete◯ 0m 42sCleanup: expired previewsRetention policy · 3 hourspreview-497removedpreview-503removedpreview-512active

Never pay for forgotten infrastructure. Expired previews and orphaned build artifacts clean themselves up on the retention you set.

Every run, in view

Know exactly what you shipped. Architecture, details, and progress in one place.

You always know what’s provisioned, where it’s running, and how far along it is, without opening a cloud console.

Deploy checkout-apiproduction · AWS us-east-1Deploying◯ 0m 11sAPP DETAILSEnvironmentproductionAvailability target99.95%Scale3 × 1 vCPU / 2 GBTriggerpush to mainImagecheckout-api:9f2c1aARCHITECTUREContainer registryprovisioningApp service · 3 instancesqueuedLoad balancerqueuedDNS & SSL certificatequeuedObject storagequeuedDeployment complete · verified · rollback availablehttps://checkout.acme.com
Coverage

Your cloud accounts. One deployment workflow.

Your cloud accounts

Amazon ECS, Azure Container Apps, or Google Cloud Run. Deploy provisions inside your accounts, with your billing and your controls.

Connect a cloud

Every environment

Development, a preview for every pull request, and production, each with its own secrets, URLs, and retention.

Read about ENV

Ship your next app without the ceremony.

Connect a cloud, set your requirements, and push. You get the build, the infrastructure, and everything in between, without doing any of it.

Get startedView docs