StateSet Deploy

One-click deployment service for commerce handlers, agents, and iCommerce apps on managed Kubernetes.

StateSet Deploy builds and hosts commerce handlers and iCommerce applications on managed Kubernetes infrastructure. Connect your GitHub repository and deploy with a single click.

Features

• One-click deploy — Push to GitHub, Deploy builds and ships automatically.
• Docker builds — Builds container images from your repo’s Dockerfile.
• Managed Kubernetes — Runs on production-grade K8s with autoscaling and health checks.
• HTTPS by default — TLS certificates provisioned automatically.
• Custom domains — Point your own domain at a deployment.
• Persistent storage — Attach volumes for databases, file uploads, or caches.
• Environment secrets — Inject API keys and credentials securely.
• Deployment logs — Stream build and runtime logs in the console.

Supported Deployment Types

Type	Description	Example
ACP Handler	Agentic Commerce Protocol handler for conversational checkout	Deploy ACP Handler
ChatGPT App	ChatGPT plugin powered by StateSet Response	Deploy ChatGPT App
iCommerce App	Full iCommerce application with agent sandbox	iCommerce Quickstart
Custom Service	Any Docker container with an HTTP endpoint	—

How It Works

1. Connect — Link your GitHub repository in the StateSet Console.
2. Configure — Set environment variables, resource limits, and domain.
3. Deploy — StateSet builds a Docker image, pushes it to the registry, and creates a Kubernetes deployment.
4. Monitor — View build logs, runtime metrics, and health status in the console.

Quickstart

Deploy from the Console

1. Go to Dashboard > Deployments > New Deployment.
2. Select your GitHub repository.
3. Configure environment variables (e.g., STATESET_API_KEY).
4. Click Deploy.

Deploy via CLI

curl -X POST https://deploy.stateset.cloud.stateset.app/deploy \
  -H "Content-Type: application/json" \
  -d '{
    "repo": "https://github.com/your-org/your-app",
    "branch": "main",
    "slug": "your-org",
    "github_token": "'"$GITHUB_TOKEN"'",
    "user_id": "your-user-id",
    "env_vars": { "STATESET_API_KEY": "'"$STATESET_API_KEY"'" }
  }'

@stateset/cli has no deploy subcommand; deployments are created with POST /deploy on the Deploy service. The app is served at {app-name}.{slug}.cloud.stateset.app.

Configure the build

A stateset.yaml in the repository root pins how the image is built and how the platform decides the service is healthy:

name: my-commerce-handler
description: ACP handler for conversational checkout

build:
  dockerfile: Dockerfile
  context: .

runtime:
  port: 3030
  health_check: /health
  readiness_check: /ready

runtime.port must match the port your container actually listens on, and the health and readiness paths must answer before the first request arrives. A deployment whose readiness check never returns 200 is rolled back as failed even though the build succeeded — which shows up in the console as a build that worked and a service that is not there.

Architecture

GitHub Push → Build (Docker) → Registry → Kubernetes Deployment
                                              │
                                              ├── HTTPS Ingress
                                              ├── Autoscaling
                                              ├── Health Checks
                                              └── Persistent Storage

Next steps

Deploy an ACP handler

A worked deployment of a checkout handler.

Deploy a ChatGPT app

A worked deployment of a widget and MCP server.

Cloud API

Driving deployments, secrets and logs from the API.

iCommerce quickstart

The application this most often ships.