Platform Ops

These commands connect you to the kis.ai platform and operate the products, services, and infrastructure running on it. Authentication (login) comes first; the rest assume you’re logged in.

What it is. Authenticates you with the kis.ai platform and stores credentials under a named context.

Why it exists. The ops commands below act on real platform resources, so they need an authenticated identity. Contexts let one machine hold several logins (e.g. work vs. personal) without re-authenticating each time.

When to reach for it. Once before using info, services, or deployproduct, and again when switching identities.

kis login -l [email protected]                  # classic password login
kis login -l [email protected] -a magiclink     # email magic-link login
kis login -l [email protected] -k work          # store under the "work" context

Flag	Meaning
`-l, --loginid`	Your login id (email)
`-a, --auth`	`classic` (default) or `magiclink`
`-k, --context`	Named context to store credentials under (default `default`)

See Tenancy & contexts for how a context differs from a tenant.

kis services

What it is. Start, stop, restart, and list services. Aliased as kis svc.

When to reach for it. Operating the services that make up your product.

kis services list             # or: kis svc list
kis services start -n api
kis services stop -n api
kis services restart -n api

Most subcommands take -n/--name to target a specific service.

kis info

What it is. Inspects products, services, and infrastructure.

When to reach for it. Seeing what you have access to and how it’s deployed.

kis info products      # products you can access
kis info services      # services and their status
kis info infra         # infrastructure information

kis git

What it is. Runs the platform “meta” tool in git mode, git operations across the repositories that make up a product.

Why it exists. A product often spans multiple repos; these subcommands let you stage, commit, and push across them as a unit rather than repo-by-repo.

When to reach for it. Multi-repo product work where ordinary per-repo git would be tedious.

kis git status
kis git stage                 # stage untracked changes
kis git commit -m "message"
kis git push
kis git pull
kis git refs                  # show references

kis dependency

What it is. Manages a product’s dependencies: add, remove, list.

When to reach for it. Declaring or auditing what your product depends on.

kis dependency list           # show resolved dependencies
kis dependency add <dep>      # add one if not already present
kis dependency remove <dep>   # remove one if present

kis deployproduct

What it is. Deploys a product application using the deploy workflow.

When to reach for it. Shipping a product/app to its environment.

kis deployproduct -p myproduct -a myapp -d ./deploy

Flag	Meaning
`-p, --product`	Product name
`-a, --app`	App name
`-d, --deploy`	Deploy path

kis version

What it is. Prints the version of the CLI binary and every installed plugin.

Why it exists. Because kis is plugin-composed, the core and each plugin version independently, this is how you confirm they’re aligned and what to cite in a support request.

kis version