# Let.com app hosting

> Let.com runs edge sites built from a source folder (Next.js, Astro, SvelteKit, Vite, static) and web services and workers from container images. Coding agents deploy with the letcom CLI (`npx @let.com/cli`, no browser needed: sign up with an emailed code or a personal token) or the Let.com hosting MCP server (OAuth, streamable HTTP), with project-scoped permissions, a spend limit and a size ceiling.

Agents start here: [Agent quickstart](https://api.staging.let.com/docs/apps/agents.md) — install, sign up or sign in without a browser, `letcom deploy --json`, env vars, logs, domains, rollback, with the matching MCP tools.

MCP endpoint: https://mcp.staging.let.com/apps. Without an account: https://mcp.staging.let.com/apps/anonymous (previews that expire unless claimed). OpenAPI: https://api.staging.let.com/openapi.json (the `/v1/apps` operations).

## Docs

- [Agent quickstart: empty repo to live URL](https://api.staging.let.com/docs/apps/agents.md): Start here (for coding agents): install, sign up or sign in without a browser, deploy, env vars, logs, domains, rollback — exact commands and the matching MCP tools.
- [Hosting MCP server reference](https://api.staging.let.com/docs/apps/mcp.md): Endpoint, authorization, protocol versions and every tool.
- [letcom CLI](https://api.staging.let.com/docs/apps/cli.md): Sign up or sign in without a browser (emailed code, personal token, device flow), deploy a folder or an image, status, logs, env, rollback, stdio MCP.
- [Errors](https://api.staging.let.com/docs/apps/errors.md): Stable error codes and what to do about each.
- [Anonymous deploys (no account)](https://api.staging.let.com/docs/apps/anonymous.md): Put a static site on a preview URL without an account; claim it to keep it.
- [Logs and metrics](https://api.staging.let.com/docs/apps/logs.md): Runtime logs (search, levels, live tail), metrics per service, retention by plan, and how tenant isolation works.
- [Log drains](https://api.staging.let.com/docs/apps/log-drains.md): Send a project’s logs to your own HTTPS endpoint, a syslog server over TLS, Datadog, Axiom or Better Stack; signed, retried, redacted.
- [Alerts](https://api.staging.let.com/docs/apps/alerts.md): Per-project alert rules (failed deploys, crash loops, OOM, error rate, p95 latency, storage, spending and AI limits, workflow/cron failures, domains) sent by email, signed webhook, Slack or Discord.
- [Tracing (OpenTelemetry)](https://api.staging.let.com/docs/apps/tracing.md): Export traces to any OTLP/HTTP endpoint: OTEL_* variables for containers, an edge span for every edge request.
- [Deploy to Let.com button](https://api.staging.let.com/docs/apps/deploy-button.md): A README button that deploys a public GitHub repository to the reader’s Let.com account.
- [Image optimization](https://api.staging.let.com/docs/apps/images.md): Resize and convert images at the edge with /_create/image; next/image works unmodified; loaders for Astro, SvelteKit and Nuxt.
- [Web Analytics and Speed Insights](https://api.staging.let.com/docs/apps/analytics.md): Privacy-first page analytics and Core Web Vitals for edge frontends: opt in per project, no cookies, no IP addresses stored.
- [Protected previews and share links](https://api.staging.let.com/docs/apps/protection.md): Who can open previews, deployment addresses and production: Let.com sign-in, a password, or share links; plus a bypass header for CI.
- [Preview toolbar and comments](https://api.staging.let.com/docs/apps/comments.md): Your team comments on protected previews: pinned to a page and element, with screenshots, replies, resolve and email digests.
- [Firewall, rate limits, bot protection and static egress IPs](https://api.staging.let.com/docs/apps/firewall.md): Allow, deny or challenge requests by IP, country, ASN, path, method, hostname or header; rate limits per client; bot scores; a dedicated outbound IP for containers.
- [Private services and databases for edge frontends](https://api.staging.let.com/docs/apps/private-networking.md): Make a container web service private to its project (only its edge frontends, with a per-deployment token, and its own services reach it), and give edge frontends a Hyperdrive binding to a managed database — nothing exposed to the internet.
- [Import a Docker Compose file](https://api.staging.let.com/docs/apps/compose.md): Turn compose.yaml into Let.com services, variables, volumes and a managed Postgres or Valkey — preview first, then apply exactly that plan.
- [Moving to Let.com from Vercel](https://api.staging.let.com/docs/apps/moving-from-vercel.md): What of a Next.js app runs at the edge on Let.com (and the conformance results), what moves to a container, and how a Vercel project’s settings, build settings, variables of every environment, vercel.json routing, domains (with their DNS records) and storage come across — one project or all of them.
- [Next.js conformance on Let.com](https://api.staging.let.com/docs/apps/nextjs-conformance.md): Every Next.js feature Let.com’s conformance suite probes at the edge (App Router, ISR, middleware, proxy.ts, edge and Node.js runtimes, server actions, next/image, PPR, use cache, …), the Next.js and OpenNext versions tested, and pass/fail from the latest run.
- [Let.com Studio: build an app by chatting](https://api.staging.let.com/docs/apps/studio.md): Describe an app; Let.com Studio writes a real Next.js app in an isolated workspace, shows a live preview, keeps every change as a version and deploys it to Let.com app hosting — with the cost of every message shown and hard limits.
- [Sandboxes: run untrusted code in isolation](https://api.staging.let.com/docs/apps/sandbox.md): Short-lived, isolated machines for code an AI agent wrote: run commands, read and write files, expose a port behind a signed URL, snapshot and restore — by MCP, CLI, SDK or API.
- [Scaling, autoscaling and sleep-on-idle](https://api.staging.let.com/docs/apps/scaling.md): Fixed replicas or a CPU autoscaler (Pro/Team); web services that sleep when idle and wake on the next request; what each plan allows.
- [Reviews, holds and appeals](https://api.staging.let.com/docs/apps/abuse.md): What happens when Let.com’s automated checks flag a project for its Acceptable Use Policy: warnings, the three kinds of hold, what keeps working, and how a person appeals.
- [Let.com Blob (file storage)](https://api.staging.let.com/docs/apps/blob.md): Store uploads, images and other files in a project: put/list/del/head/copy with @let/blob, public URLs or signed private ones, browser uploads without exposing the token.
- [Plans, usage and spending limits](https://api.staging.let.com/docs/apps/billing.md): Free, Pro and Team; what is metered; the spending limit that is on by default; and how usage is invoiced.
- [Registered domains](https://api.staging.let.com/docs/apps/domains.md): Domain names the account owns through Let.com: ordering, renewal, nameservers, lock, privacy, transfers, and what agents can read.
- [Persistent volumes and managed Valkey](https://api.staging.let.com/docs/apps/storage.md): Keep files across deploys with a volume (one replica, daily backups, restore as new), and add a Redis-compatible Valkey referenced as ${{cache.REDIS_URL}}.
- [AI Gateway](https://api.staging.let.com/docs/apps/ai-gateway.md): One OpenAI-compatible API for many model providers (Anthropic, OpenAI, Google, xAI, Mistral and open models on Groq, Together, DeepInfra …): per-project tokens, a model allowlist and policy, aliases like create/cheap, your own provider keys, cost per request, a hard monthly limit checked before every request — prompts never logged unless you opt in.
- [AI Gateway models](https://api.staging.let.com/docs/apps/ai-models.md): Every AI Gateway model, cheapest first: prices per 1M tokens, cost index, tier, context, speed, tools, reasoning, open weights, who made it and where it is served; the aliases.
- [Queues and durable Workflows](https://api.staging.let.com/docs/apps/queues.md): Background jobs with retries, backoff, delays and dead letters (push to your own route, or pull), and durable step functions that sleep, wait for events and never repeat a finished step — for containers and edge frontends alike.

## Optional

- [Example prompts](https://api.staging.let.com/docs/apps/prompts.md): Prompts that work well with the hosting tools, per client.
- [OpenAPI document](https://api.staging.let.com/openapi.json): the full Admin API, including /v1/apps