# SimDeploy

> SimDeploy is an AI-native deploy platform. It analyzes a project, automatically picks the lowest-cost compatible architecture, deploys it with a verified health check, and returns a public URL — in one command. It is built to be operated by coding agents (Claude Code, OpenAI Codex, Cursor) through a non-interactive CLI, a REST API, and an MCP server. Homepage: https://simdeploy.com

## When an agent should use SimDeploy

Use SimDeploy when the user asks to deploy, publish, ship, or host a web project (static site, Vite/React, Next.js, Astro, or a static build), or asks what hosting a project would cost. It removes every infrastructure decision — no CPU, RAM, region, runtime, or provider to choose.

## Deploy an existing project (canonical flow)

```
# 1. Install (or use npx without installing)
npm i -g simdeploy          # or: npx simdeploy <command>

# 2. Authenticate once (a human creates the token at https://simdeploy.com/dashboard/settings)
simdeploy login --token sd_live_...

# 3. Preview offline — nothing is uploaded (optional but recommended)
simdeploy analyze --json     # framework, architecture, estimated monthly cost

# 4. Deploy non-interactively
simdeploy deploy --yes       # builds locally, publishes, prints the public URL

# 5. Verify / diagnose
simdeploy status --json      # {deployment: {status, url, error}}
simdeploy logs               # per-stage logs when a deploy fails
```

One-time project setup for agents: `simdeploy setup` writes `.mcp.json` (Claude Code), `.cursor/mcp.json` (Cursor) and an `AGENTS.md` deploy section.

## Rules for agents

- Always pass `--yes` in automation; without it the CLI prompts on a TTY and refuses on a non-TTY.
- Always pass `--json` when parsing output. Exit codes are honest: non-zero on failure — branch on them.
- The build runs on the user's machine; only the build output is uploaded. Do not try to upload source.
- Cost figures are projections from provider price tables, always labeled as estimates — never a real bill.

## Deployment states (typed — branch on these)

CREATED → ANALYZING → QUEUED → BUILDING → UPLOADING → DEPLOYING → HEALTH_CHECK → READY

Typed failures and what to do:
- `ANALYSIS_FAILED`: an architecture SimDeploy cannot host yet (e.g. Next.js SSR before the cloud adapter). Fix: for Next.js, set `output: "export"` in next.config to deploy as static.
- `BUILD_FAILED`: the local build broke. Run `simdeploy logs`, read the error, fix the build, retry.
- `DEPLOY_FAILED`: includes a failed HTTP health check (the published page returned non-2xx). Check that the build output has an index.html; read `simdeploy logs`.

## MCP server

Run `simdeploy-mcp` (stdio). Tools: analyze_project, estimate_cost, create_project, deploy_project, list_projects, get_project, get_deployment, get_logs. `analyze_project` and `estimate_cost` run fully offline. Auth reuses `~/.simdeploy/config.json` from `simdeploy login`.

Add to Claude Code: put `{"mcpServers":{"simdeploy":{"command":"simdeploy-mcp"}}}` in `.mcp.json`, or run `simdeploy setup`.

## Frameworks

Detected: Next.js, Vite, React (CRA), Astro, Express, generic Node, static sites. Deploys today cover static builds (Vite, CRA, static Astro, Next.js with `output: "export"`). SSR/serverless is rolling out on the cloud adapter; the pipeline fails with a clear, typed message when a project still depends on it.

## Pricing

Free plan to start (no card). Paid plans have a fixed monthly price with explicit limits, billed via Stripe. The infrastructure cost estimate appears before every deploy.

## API

Base: https://simdeploy.com — Auth: `Authorization: Bearer sd_live_...`

- GET /api/v1/me — validate token, org, scopes
- GET|POST /api/v1/projects — list / create {name}
- POST /api/v1/projects/:id/analyze — register analysis, get cost + planned route
- POST /api/v1/projects/:id/deployments — deploy (multipart: meta JSON + artifact tar.gz)
- GET /api/v1/deployments/:id — status + events
- GET /api/v1/deployments/:id/logs?format=text — logs
- POST /api/v1/cost/estimate — standalone cost estimate

Errors: `{"error":{"code","message"}}` with semantic HTTP status.

## Docs

- Agent guide: https://simdeploy.com/docs/agents
- Claude Code guide: https://simdeploy.com/claude-code
- Full docs: https://simdeploy.com/docs