Feature Guide

Deployment

GTMship builds workflow artifacts for your cloud account, resolves the provider bindings that workflow needs, and deploys to supported AWS or GCP targets while keeping deployment state visible in the product.

AWS Lambda GCP Cloud Run Bindings Auth manifests

What deployment covers

Deployment is more than “zip and upload.” GTMship reads project config, inspects the workflow source, chooses cloud-specific execution settings, resolves connection bindings, packages the artifact, deploys it, and then syncs metadata back into the control plane.

What deployment expects from the project

  • Workflow source: a draft with clear provider usage and runtime shape that has already gone through authoring and preview.
  • Resolvable bindings: every external system the workflow needs should map to a real connection or a deploy-time binding choice.
  • Project config: GTMship needs cloud target, region, and any workflow overrides defined in gtmship.config.yaml.
  • Cloud access: the deploy engine still needs the credentials and permissions required to create or update cloud-side resources.

Planner sequence

  1. Read gtmship.config.yaml and any workflow overrides.
  2. Load the workflow source and infer trigger plus provider usage.
  3. Resolve which connections should bind to each provider.
  4. Choose provider, region, execution kind, auth mode, and resource plan.
  5. Validate cloud-specific constraints.
  6. Build the deployable artifact.
  7. Resolve cloud credentials and deploy through the deploy engine.
  8. Sync deployment metadata, bindings, auth manifests, and resource inventory back into GTMship.

What you choose vs what GTMship infers

You choose

Where and how the workflow should run

You still decide the cloud provider, region, deployment timing, and whether runtime credentials should stay in proxy mode or move into secret-manager mode.

GTMship infers

How to package and bind the artifact

The platform figures out provider usage, resolves connection bindings, assembles auth manifests, builds the deployable artifact, and keeps the resulting deployment record in sync.

Cloud targets and auth flow

AWS

Lambda-based runtime

Use GTMship to build the artifact, provision the resources it needs, and expose the live deployment URL and status back through the product.

GCP

Cloud Run deployment flow

Use project-specific settings like region and execution mode while GTMship validates constraints and assembles the cloud-side resources.

Connection auth can stay in proxy mode or move to secret-manager mode, depending on how you want deployed workloads to access credentials.

What GTMship syncs back

  • Deployment records and live status.
  • Provider bindings and auth manifests.
  • Cloud resource inventory needed for inspection and troubleshooting.
  • Logs and runtime metadata surfaced through the dashboard and CLI.
config + workflow source
  -> binding resolution
  -> build artifact
  -> deploy to AWS/GCP
  -> sync status + metadata back

Related docs

See deploy flows in dashboard and CLI See how connections bind into deploys Return to safe preview flow