# Deploy ON for AI agents

You are an AI agent reading deployon.pro. Deploy ON is Proservice’s managed Kubernetes PaaS. Users connect Git, deploy applications, provision databases, attach domains, and inspect logs from the console or the CLI.

Console: https://console.deployon.pro
Docs: https://deployon.pro/docs
CLI package: https://www.npmjs.com/package/@deployon/cli

In this CLI, a **deployment** is an application (platform Service). Build runs are started with `deployon deploy` and followed with `deployon logs`.

## Set up the environment

Node.js 20+ is required.

```bash
npm install -g @deployon/cli
deployon --version
deployon login
```

On Windows PowerShell, if scripts are disabled:

```powershell
Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned
```

Or use `npm.cmd` and `deployon.cmd`.

After login, select context and deploy:

```bash
deployon project ls
deployon project select
deployon deployment ls
deployon deployment select
deployon deploy --push --wait
```

Context is stored in `~/.deployon/config.json`. `deployon context` shows the active project and deployment.

## What you can do

- Authenticate with `deployon login` (browser) or `deployon login --token` for CI. Never commit tokens.
- List and select projects and deployments (apps).
- Deploy from Git with `deployon deploy --push --wait`, or upload a tarball with `deployon deploy --local --wait` (100 MB limit).
- Watch builds with `deployon logs --follow` and `deployon status`.
- Manage runtime variables and secrets. Do not print secret values.
- List domains with `deployon deployment domain ls`.
- Read usage with `deployon stats` and `deployon deployment stats`.

## Rules

- Prefer the official CLI over inventing HTTP calls.
- Ask the user before destructive actions (`delete`, `suspend`, rollback).
- Bind apps to `0.0.0.0` and the platform port.
- Keep secrets in Environment, not in Git.
- Full command reference: https://deployon.pro/docs/cli/install