# Kanject CLI

The Kanject CLI coordinates three release jobs around normal .NET and cloud tools: deploy services, publish packages, and distribute desktop applications. Each path starts with a local proof and ends with an evidence-bearing production action.

> **New here? Learn by shipping:** Bean & Bark is the fastest way in: [ship the Orders API](https://www.kanject.com/docs/cli-bean-bark/), [release the Pricing SDK](https://www.kanject.com/docs/cli-bean-bark-packages/), then [ship Roastery Desk](https://www.kanject.com/docs/cli-bean-bark-desktop/) across three operating systems. The same fictional company makes the boundaries between deploy, packages, and distribution visible.

The CLI does not replace `dotnet`, AWS tools, CloudFormation, or your CI provider. It coordinates them around a manifest, stage files, generated MSBuild wiring, lockfiles, and deployment ledgers so the loop becomes repeatable. Run bare `kanject` for a project-aware landing screen; `kanject --help` renders the complete tree.

```bash
kanject <root-command>
kanject <provider> <provider-command>
```

- **[Deploy services](https://www.kanject.com/docs/deployment/)** — `new` / `init` → `test` → `aws deploy` → deployment ledger, rollback, previews, and pipeline automation.
- **[Publish packages](https://www.kanject.com/docs/packages/)** — `packages plan` / `verify` → version audit → candidate feed smoke → approved, journaled publication.
- **[Distribute desktop apps](https://www.kanject.com/docs/distribute/)** — Archive/native artifact proof → edition × RID routes → candidate downloads → byte-identical promotion.

## Command shape

Root commands are provider-agnostic and work against the project tree. Provider-bound commands live under a provider key; today the production path is `kanject aws ...`.

- `kanject new`, `init`, `doctor`, `update`, `install provider` — create, check, and extend the CLI
- `kanject add`, `configure distribution`, `env`, `sync`, `test`, `migrate` — daily project work
- `kanject aws …` and `kanject github …` — provider operations for deploy, previews, pipelines, and distribution

> **Best next page:** If you are deploying Lambda, use the [Lambda quick start](https://www.kanject.com/docs/quick-start/). For a library repo, start at [Publish .NET packages](https://www.kanject.com/docs/packages/). For a desktop app, start at [Distribute desktop applications](https://www.kanject.com/docs/distribute/).

---
_Source: https://www.kanject.com/docs/cli/ · Kanject Docs_