Zaysa

DELIVERY · DEPLOY WITH AI

Say where it should run. Review it. Ship it.

Pick a repository and a cloud account, describe the deploy in one sentence, and Zaysa prepares the pipeline against what really exists in your account. It asks only what it cannot find, and nothing runs until you have reviewed it.

Deploy with AI on Pro
Start freeBook a demo

THE USUAL WAY

Every new service starts with a copied pipeline.

A pipeline file is copied from another repo and edited until it passes.
Cluster and service names are typed by hand, and a typo fails at deploy time.
Registry, region and permissions are looked up in three different consoles.
Nobody is sure what the pipeline will do until it runs.
What you are seeing
  1. 01Pick the repo and the cloud
  2. 02Say it in one sentence
  3. 03Picked from what really exists
  4. 04Only what it cannot find
  5. 05One review screen
  6. 06Created, committed, running
  7. 07Deployed

Example data.

How it works

Pick, describe, review

01

Pick the repo and the cloud

Choose the repository and branch, then the connected cloud account.

Repository · shop/checkout

Branch · main

Cloud account · AWS · shop-staging

Example data.

02

Describe it

Say what to deploy and where. Zaysa resolves the target, region and environment and asks only for missing details.

What do you want to deploy, and where?

put this on ECS in eu-west-2, staging

ECSeu-west-2staging

Example data.

03

Review and run

See the pipeline steps, and the actual Terraform and plan when you use Terraform, before you choose to run it.

1build image
2push to checkout (ECR)
3update service staging/checkout-svc
4wait for rollout

Example data.

Infrastructure

Three ways to get the infrastructure

Choose an existing destination, use Terraform in your repository, or let Zaysa provision what you described. Review the configuration before running anything.

Live ECS services · AWS · shop-staging

◉staging/checkout-svc
○staging/cart-svc
○staging/search-svc

Listed live from the account

Example data.

Live destinations

Every cloud, the destinations you already run

Pick from what the connected account lists now. A cluster deleted an hour ago is never offered.

Listed live from your account. VM deploys on AWS, Azure and Google Cloud need no host login or stored key.

AWS destinations

live listing
EKS clusterdestination
ECS servicedestination
Lambda functiondestination
EC2 instancedestination

Lambda container images can deploy. Zip functions are listed and refused with a reason.

Example data.

Run it with

GitHub Actions or Jenkins

Both run the same prepared pipeline. GitHub Actions gets a workflow created and pushed. One action creates the Jenkins job, commits the Jenkinsfile and starts a build. The pipeline is prepared in your CI-CD Library.

GitHub Actions

✓ workflow created

✓ pushed

Jenkins

○ job created

○ Jenkinsfile committed

○ build started

Example data.

ON THE PRO PLAN

From a sentence to a running deploy

Pick where it runs, see the real configuration, then choose when to run it.

Deploy with AIPR Cost GatesPipelines for GitHub Actions and JenkinsTerraform with plan and approval

$20 per month

See the Pro planBook a demo

Questions

Frequently asked questions

AWS: EKS, ECS, Lambda container images and EC2. Azure: AKS, Container Apps, Web App and virtual machines. Google Cloud: GKE, Cloud Run, Cloud Functions and Compute Engine VM. DigitalOcean: DOKS and App Platform. Lambda zip functions are listed but refused with a reason.

More in Delivery

PR Cost GatesCI/CD and TerraformAll features

See what you run, and what it costs.

Free plan, no card needed.

Start freeBook a demo