# Deploy a web app or service

> Deploy a web app or service: 1 companies fully do it, 6 with a limit, 12 carry the tag. Every listing in Cloud & infrastructure with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/infrastructure.deploy-app/
- Markdown: https://www.anchorterminal.com/niches/infrastructure.deploy-app/index.md (~1,250 tokens)
- Slim: https://www.anchorterminal.com/niches/infrastructure.deploy-app/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/infrastructure.deploy-app/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 6 | 12 | 32 | 11 |

## What counts as done

A live URL serving the project, the deploy id and final state read back from the platform, and any database connection strings set as environment variables, without a step the agent cannot run itself.

How agents ask for it: deploy this to Netlify; put this app on Render with a Postgres database; host this on my Cloudflare domain; set up a server for my blog

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Netlify API + MCP (Netlify, Inc.)**: With a personal access token, the REST API deploys by file digest or ZIP, deploy state is polled until ready, and environment variables are set by API, all without a browser. The hosted MCP's deploy tool still hands back a CLI command (#34, open).

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **AWS MCP Servers (Amazon Web Services, Inc.)**: Deploys go through the Serverless (SAM), ECS or AWS API servers, which run locally with configured AWS credentials and CLI; no single tool returns a live URL, deploy id and connection strings in the docs read.
- **Azure MCP Server (Microsoft Corporation)**: ARM template deployments can be created and read, App Service settings and database connections set, and a service principal in environment variables avoids a browser; no single tool returns a live URL and final state for an app deploy in the README.
- **Cloudflare CLI (cf) (Cloudflare, Inc.)**: cf deploy runs from CI with CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID and never waits for input, but the pages read don't show the deploy id, final state or URL it returns. acc-08 hands Cloudflare setup to Claude Code through the CLI.
- **Cloudflare MCP Servers (Cloudflare, Inc.)**: mcp.cloudflare.com's execute tool can call any Cloudflare API endpoint with an API token, Workers uploads included, but there is no deploy tool that returns a live URL and final state. acc-09 found it resolved most Lambda-to-Workers issues.
- **DigitalOcean MCP Server (DigitalOcean, LLC)**: create-app-from-spec deploys from a repository, apps-get-deployment-status reads the deploy, and a Bearer token needs no browser; the tool reference doesn't show the live URL or setting database connection strings as variables.
- **Railway MCP Server (Railway Corporation)**: The local server (railway mcp local) has create_service, set_variables, deploy, list_deployments and generate_domain, but it runs on CLI credentials, and the hosted server only redeploys or hands work to railway-agent. #985 (open): railway up auto-creates and deploys a new project when it detects an agent.
- **Render MCP Server (Render Services, Inc.)**: With an API key it creates web services, static sites, Postgres and Key Value, triggers deploys and reads deploy details and logs, but it can't return database connection URLs to set as variables (#7, open).

- not this job: neckbeard (David Beale (individual, GitHub account bealesh)): It scaffolds OpenTofu and pipelines; bootstrap and deployment are run by the person holding cloud credentials, and no live URL comes back.
- not this job: Terraform MCP Server (HashiCorp, Inc. (an IBM Company)): It manages Terraform workspaces and runs, not application deploys; no live URL or app deploy state comes back.

## What stops agents finishing

- hosted deploy tool returns a CLI command the client cannot run
- OAuth or browser sign-in needed before the first call
- database connection string not returned by the tool
- project claim step a person must do within a time limit

## Around it

Before: code.build, code.write-app. After: observability.verify-deploy, infrastructure.inspect-debug.

## Where this comes from

Weight 32 of 100 in Cloud & infrastructure: 11 of 32 accounts (about 31 per cent of 35 account-to-use-case links): Netlify, Render, Railway, Cloudflare and DigitalOcean

As data: https://www.anchorterminal.com/api/v1/use-cases/infrastructure.deploy-app.json, or the MCP tool get_use_case with id infrastructure.deploy-app. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
