# Vibe code to production with Clanker Cloud

Use Clanker Cloud when an AI-built app works locally and needs a concrete, reviewed path to production infrastructure.

## Buyer query

Can Clanker Cloud inspect my repo and provider context, then propose a production deployment plan before creating anything?

## App workflow

Open Deploy or Maker mode, connect the repo and target provider profile, then ask:

```text
Take this AI-built app from local prototype to production. Inspect the repo, identify runtime needs, propose cloud resources, CI/CD, secrets, domain routing, estimated cost, and rollback plan before apply.
```

## Required context

- GitHub repo, app runtime, environment variables, target provider profile, domain or subdomain, database needs, expected traffic, and budget or region constraints.

## Example output

```text
Plan: containerize web and API services, create a managed Postgres database, configure secrets locally, add GitHub Actions deploy workflow, route app.example.com through Cloudflare, estimate baseline monthly cost, and require review before creating resources. No apply has run.
```

## Safety boundary

Repo and provider inspection are read-first. Maker mode generates a deploy plan. Creating resources, modifying DNS, or changing secrets requires an explicit reviewed apply step.

## Related

- Builder guide: https://clankercloud.ai/vibe-coding-to-production
- Local credentials: https://clankercloud.ai/security/local-credentials