# nesly

> A deploy platform: push code from git or the CLI, and it is built,
> given an HTTPS address and kept online. Node.js, Python, Go, .NET,
> static sites, or your own Dockerfile.

Agents and scripts: the CLI is the API. Every command accepts `--json`
and then prints exactly one JSON object on stdout (progress and logs go
to stderr), with stable exit codes: 0 ok, 1 error, 2 usage, 3 auth,
4 not found, 5 conflict.

## Deploy something

```
brew install neslyhq/tap/nesly
nesly login
cd my-app && nesly deploy --yes --json
```

`deploy` packs the directory (never `.env` files, never anything the
project's `.gitignore` excludes), builds it — a `Dockerfile` in the root
wins, otherwise the stack is detected — waits for the rollout and prints
the live URL.

## Commands

- `nesly whoami | logout` — who is signed in, and sign out
- `nesly link <project>` — bind this directory to a project
- `nesly deploy [--project X] [--yes]` — build and publish
- `nesly ls` / `nesly inspect <deployment-id>` — deployments and detail
- `nesly rollback <deployment-id>` — instant, no rebuild
- `nesly logs --follow` — build and runtime output
- `nesly env set K=V` / `env ls [--reveal]` / `env rm K` — applies to the next deployment
- `nesly new <template>` — start from a deployable template (astro-static, node-postgres, python-fastapi, dotnet-mssql); no argument lists them
- Framework notes at /deploy/{nextjs,astro,sveltekit,vite-react,angular,express,fastapi,aspnet,go,hugo,jekyll,mkdocs}/
- `nesly addon add postgres` — managed database, injects `DATABASE_URL`
- `nesly addon add mssql` — managed SQL Server, also injects `ConnectionStrings__Default` (.NET reads it directly)
- `nesly domain add <fqdn>` / `domain verify <fqdn>` — custom domain, automatic HTTPS
- `nesly usage` / `nesly limits` — usage, and your allowances against the plan
- `nesly diagnose` — why the deployment failed: evidence lines, missing env vars, the fixing command
- `nesly run -- <cmd>` — one-off command (migrations) with the app's own image and env
- `nesly addon backup ls|create|restore` — nightly database backups
- `nesly account export|close|notifications` — your data, your exit, your mail settings

## MCP (Model Context Protocol)

`nesly mcp` serves the whole platform as MCP tools on stdio — deploy,
logs, env, domains, addons, rollback, and `diagnose_deployment` (call it
first after a failure). Register it, e.g. for Claude Code:

```
claude mcp add nesly -- nesly mcp
```

Claude Code users can install the plugin instead (MCP tools + a deploy
skill in one): `/plugin marketplace add neslyhq/claude-plugin`, then
`/plugin install nesly@nesly`.

Headless auth: set `NESLY_TOKEN` to an access token from `nesly token create`.

## Application contract

Listen on `$PORT`, bind `0.0.0.0`. Deployments are immutable: changing
env vars or code means a new deployment, never a mutation of a running
one. Free applications pause when idle and wake on the first request;
Pro keeps them warm.

## Docs

Every docs page has a markdown twin — replace the trailing slash with
.md (e.g. https://nesly.net/docs/builds.md, index is /docs/index.md)
and you get the page as plain markdown instead of HTML.

- Get started: https://nesly.net/docs/
- CLI reference: https://nesly.net/docs/cli/
- For AI agents (MCP, --json contract): https://nesly.net/docs/agents/
- Plan allowances: https://nesly.net/docs/limits/
- Your data and account: https://nesly.net/docs/account/
- Security (what is actually built): https://nesly.net/security/
- Changelog: https://nesly.net/changelog/
- Pricing: https://nesly.net/pricing/
- Contact: https://nesly.net/contact/