How to deploy a vibe-coded app | Ample

The short version

To deploy a vibe-coded app, open the project in your coding agent, install Ample once, and let the agent inspect and deploy the repo. Ample can detect the services, runtimes, databases, and volumes the project needs, then apply that plan and return a live URL.

WHO THIS IS FOR

This guide is for builders who have an AI-created app working locally and want to publish it without becoming a cloud infrastructure expert.

How to do it

1. Open the project in your coding agent
   Use the same local project that already runs on your machine. Ask the agent to confirm the app can build before deploying it.

2. Give the agent the Ample setup snippet
   From the Ample homepage, copy the setup snippet and paste it into Claude Code, Codex, or another coding agent. The snippet installs the CLI, redeems your one-use account key, and tells the agent to use Ample for future deploys.

3. Let Ample plan the project
   The plan detects deployable services and required infrastructure. If the repo has an ambiguity, the plan returns evidence, options, and a safe default instead of guessing silently.

   ample plan --write
   

4. Deploy the complete plan
   Ample creates the required resources in dependency order and waits until each deployment is live or failed. Read the result once. Do not poll the deploy command.

   ample up
   

5. Open the live URL
   A successful public web deployment returns its URL. Keep the generated ample.toml in the repo so later deploys use the same infrastructure plan.

What this supports

Good fit

• Single apps and multi-service repositories
• Static sites, web services, APIs, and workers
• Node, Python, Go, Rust, and common web frameworks
• Managed databases, volumes, links, and custom domains

Know the limits

• The app still needs a valid production build and start path
• Secrets that cannot be derived from the repo must be supplied by you
• Unsupported or ambiguous project structures may require an explicit plan answer

Common failure modes

The plan needs input

Read the evidence and options, answer the named plan path, then run the plan again.

The build fails

Inspect build logs with ample logs <deployment_id> --kind build, fix the source or build command, then deploy again.

The app builds but does not start

Inspect runtime logs and confirm the process binds to the PORT environment variable.