Ways to deploy

One control plane, three workflows

Use the web, CLI, or CI/CD. Every workflow calls the same hosted control plane and deploys into the AWS account your organization connects.

Visual workflow

Web platform

Workloads run in your AWS account

Create projects, deploy applications, manage resources, and inspect operations from one workspace.

  • Guided Lambda, Fargate, and Amplify deployment
  • Environment and secret management
  • Deployment history, logs, and metrics
  • Role-based access to your AWS account
Create an account

Terminal workflow

Command-line client

Workloads run in your AWS account

Use the same projects and deployment API from a local terminal without duplicating cloud logic.

  • Authenticate with your platform account
  • Link a local directory to a project
  • Push configuration and trigger deployments
  • Stream backend-owned status and logs
Read CLI docs

Automated workflow

CI/CD

Workloads run in your AWS account

Use a scoped platform token to deploy the same project from your source workflow.

  • Backend-issued CLI token
  • Project-linked deployment configuration
  • The same API and execution path as the web
  • Optional AWS OIDC for workflow-side checks
Read deployment docs

Your AWS stays yours

Every deployment runs in the AWS account your organization connects. You retain account ownership and pay AWS directly for the resources your applications use.

Start with the right commitment

Start in the web workspace, use the CLI during development, and automate the same project through CI/CD without introducing a second deployment engine.