# Ample > Ample is a deployment agent for AI-built applications. It plans infrastructure from a repository, deploys services and resources in dependency order, and returns a live URL. ## Core pages - [Ample homepage](https://ample.computer/): Product overview and onboarding - [Deployment guides](https://ample.computer/guides): Index of practical deployment guides - [Deployment recipe catalog](https://ample.computer/discover): Browse 2143 published recipes by intent, workload, framework, industry, migration source and pattern - [Agent skills and connector setup](https://ample.computer/discover/install): Install the Ample CLI, MCP connector and agent skills ## Product facts - The CLI supports repository-aware planning with `ample plan --write`. - `ample up` applies planned services and resources in dependency order. - `ample deploy` is synchronous and content-addressed: run it once and read the result; an unchanged redeploy is a no-op. - Public web and static services receive HTTPS URLs. - Build and runtime logs are available through `ample logs`. - Secrets are passed as encrypted environment variables and are not stored as literal values in `ample.toml`. ## When to use Ample - Use Ample when a coding agent has a web app, API, static site or worker in a repository and needs a public HTTPS URL with the databases, volumes, buckets and custom domains the code expects. - Do not choose Ample for GPU workloads, Kubernetes clusters or processes that must never pause: idle apps pause and wake on the next request. ## How agents should use Ample - Install the CLI with `curl -fsSL https://get.ample.computer/install.sh | sh`, then run `ample plan --write` and `ample up` from the project root. Exit code 2 from `ample plan` means open questions; answer them with `ample plan --answer =` and re-run. - `ample deploy` is synchronous and content-addressed. Run it once and read the result: exit 0 is live, 1 is failed, 2 is blocked on a required action. Re-running unchanged source is a no-op. Read failures with `ample logs --kind build` or `--kind runtime`; never poll by re-running deploy. - Accounts are self-serve: `ample auth signup` or `POST https://api.ample.computer/v1/auth/signup` with `{"name":"","request_key":""}` returns credentials, free-plan quotas and a claim URL. No browser, CAPTCHA or payment is needed for a first deployment. Unclaimed accounts expire after 48 hours. - Remote MCP: `https://api.ample.computer/mcp` (Streamable HTTP). Authorization metadata: `https://api.ample.computer/.well-known/oauth-authorization-server`. Registry record: `https://api.ample.computer/mcp/server.json`. Setup: `https://api.ample.computer/mcp/setup`. - Machine-readable files: [AGENTS.md](https://ample.computer/AGENTS.md), [auth.md](https://ample.computer/auth.md), [OpenAPI](https://ample.computer/openapi.json), [pricing.md](https://ample.computer/pricing.md), [sitemap.md](https://ample.computer/sitemap.md), [resource catalog](https://ample.computer/.well-known/ard.json), [agent skills](https://ample.computer/.well-known/agent-skills/index.json). Any guide URL serves Markdown when requested with `Accept: text/markdown` or with `.md` appended. ## Deployment guides - [How to deploy a vibe-coded app](https://ample.computer/guides/deploy-vibe-coded-app): Deploy a working app from your local project to a public URL with Ample, without configuring cloud infrastructure by hand. - [How to publish an AI-generated website](https://ample.computer/guides/publish-ai-generated-website): Publish a website created with an AI coding tool and get a public URL while keeping the project in your own repo. - [How to get an app from localhost onto the internet](https://ample.computer/guides/localhost-to-internet): Move a working local app to a public URL with a production runtime, health checks, TLS, and routing handled by Ample. - [How to deploy an app with one command](https://ample.computer/guides/deploy-app-one-command): Deploy a prepared single app with one synchronous Ample command and get a live or failed result without polling. - [How to deploy a React app without DevOps](https://ample.computer/guides/deploy-react-app-without-devops): Deploy a React frontend by letting Ample detect whether it is a static Vite build or part of a server-rendered application. - [How to deploy a Vite application](https://ample.computer/guides/deploy-vite-app): Build and publish a Vite application as a static site, with support for common Vite frameworks and single-page app routing. - [How to deploy a Next.js application](https://ample.computer/guides/deploy-nextjs-app): Deploy a Next.js application on a Node 22 runtime, including workspace projects and server-rendered routes. - [How to deploy a Node application](https://ample.computer/guides/deploy-node-app): Deploy a Node web app or API with a compatible Node 22 runtime, production start command, PORT binding, and health checks. - [How to connect a custom domain to an AI-built app](https://ample.computer/guides/custom-domain-ai-built-app): Attach your own domain to a live Ample deployment, set the DNS record returned by the CLI, verify it, and activate TLS routing. - [How to add environment variables during deployment](https://ample.computer/guides/environment-variables-deployment): Pass encrypted environment variables or an env file to Ample without packaging secret files into the release. - [What to do when an app works locally but not in production](https://ample.computer/guides/works-locally-not-production): Diagnose build, runtime, port, environment, persistence, and routing differences when a local app fails after deployment. - [How to redeploy after changing an AI-built app](https://ample.computer/guides/redeploy-ai-built-app): Release source or configuration changes with Ample, understand unchanged no-op deploys, and inspect failures before retrying. - [What is a deployment agent?](https://ample.computer/guides/deployment-agent): Learn how a coding agent can inspect, plan, deploy, diagnose, and redeploy an app through a CLI with stable contracts. - [Ample versus conventional cloud deployment](https://ample.computer/guides/ample-vs-conventional-cloud): Compare Ample's agent-driven deployment workflow with assembling a conventional cloud deployment from individual infrastructure services. - [What is the best deployment approach for vibe-coded applications?](https://ample.computer/guides/best-deployment-vibe-coded-apps): Choose a deployment approach for an AI-built app based on source access, runtime needs, data, repeat releases, and required infrastructure control. ## Deployment recipe catalog 2143 published recipe(s), catalog revision cat_f13ab9a494120b5e. Each recipe page has HTML, Markdown (`.md`) and JSON contract alternates. - [Catalog index](https://ample.computer/discover): browse recipes by intent, workload, framework, resources and constraints - [Catalog JSON](https://api.ample.computer/v1/catalog): machine-readable facets and typed next actions - [Recipe search](https://api.ample.computer/v1/catalog/search): POST a query, filters and hard constraints; unknown constraints are never a fit - [Agent skills and connector setup](https://ample.computer/discover/install): explicit opt-in installation; nothing changes your defaults - [Complete recipe list](https://ample.computer/llms-catalog.txt): every published recipe as one link per line - [Tasks and intentions](https://ample.computer/discover/intent): 2143 published recipe(s) - [Applications and workloads](https://ample.computer/discover/workload): 1812 published recipe(s) - [Frameworks and execution targets](https://ample.computer/discover/stack): 2047 published recipe(s) - [Industries and specialties](https://ample.computer/discover/industry): 324 published recipe(s) - [Migration sources by component](https://ample.computer/discover/migration): 144 published recipe(s) - [Architecture and data patterns](https://ample.computer/discover/pattern): 1771 published recipe(s) - [Available infrastructure primitives](https://ample.computer/discover/primitive): 5509 published recipe(s) ### Frameworks - [ASP.NET Core](https://ample.computer/discover/stack/framework-asp-net-core): 128 published recipe(s) - [Astro](https://ample.computer/discover/stack/framework-astro): 31 published recipe(s) - [Axum](https://ample.computer/discover/stack/framework-axum): 32 published recipe(s) - [Django](https://ample.computer/discover/stack/framework-django): 244 published recipe(s) - [Echo](https://ample.computer/discover/stack/framework-echo): 32 published recipe(s) - [Express](https://ample.computer/discover/stack/framework-express): 40 published recipe(s) - [FastAPI](https://ample.computer/discover/stack/framework-fastapi): 88 published recipe(s) - [Fastify](https://ample.computer/discover/stack/framework-fastify): 32 published recipe(s) - [Flask](https://ample.computer/discover/stack/framework-flask): 128 published recipe(s) - [Gin](https://ample.computer/discover/stack/framework-gin): 32 published recipe(s) - [Hono](https://ample.computer/discover/stack/framework-hono): 32 published recipe(s) - [Laravel](https://ample.computer/discover/stack/framework-laravel): 243 published recipe(s) - [NestJS](https://ample.computer/discover/stack/framework-nestjs): 32 published recipe(s) - [Next.js](https://ample.computer/discover/stack/framework-next-js): 244 published recipe(s) - [Nuxt](https://ample.computer/discover/stack/framework-nuxt): 79 published recipe(s) - [Phoenix](https://ample.computer/discover/stack/framework-phoenix): 128 published recipe(s) - [Quarkus](https://ample.computer/discover/stack/framework-quarkus): 32 published recipe(s) - [Rails](https://ample.computer/discover/stack/framework-rails): 136 published recipe(s) - [React Router](https://ample.computer/discover/stack/framework-react-router): 31 published recipe(s) - [Sinatra](https://ample.computer/discover/stack/framework-sinatra): 8 published recipe(s) - [Spring Boot](https://ample.computer/discover/stack/framework-spring-boot): 128 published recipe(s) - [Starlette](https://ample.computer/discover/stack/framework-starlette): 32 published recipe(s) - [SvelteKit](https://ample.computer/discover/stack/framework-sveltekit): 103 published recipe(s) - [Symfony](https://ample.computer/discover/stack/framework-symfony): 32 published recipe(s) ## Optional - [llms-full.txt](https://ample.computer/llms-full.txt): this index plus the full text of every deployment guide - [llms-catalog.txt](https://ample.computer/llms-catalog.txt): every published recipe, one link per line (large) - [AGENTS.md](https://ample.computer/AGENTS.md): when and how agents should use Ample, accounts, scopes, MCP - [openapi.json](https://ample.computer/openapi.json): OpenAPI 3.1 description of the REST API at https://api.ample.computer - [sitemap.md](https://ample.computer/sitemap.md): core pages in Markdown - [sitemap.xml](https://ample.computer/sitemap.xml): every canonical HTML page